Start Here: What This Product Is
OvionDesk AI is a self-hosted customer support and live chat system with AI features. You install it on your own server or hosting, add the chat widget to your website, and manage customer conversations from the admin panel. Your team can reply manually, let AI reply, or use both together.
admin@ovion.techDemo@12345- Workspace slug:
support-demo-oviondesk-ai
This is not a ready-made cloud account. It is a web application that you download, upload, install, configure, and run on your own hosting or server.
scripts\build-demo-site-min-inode-zip.ps1 when you need the cPanel root/public upload pair.
CodeCanyon Marketplace Release Docs
If you are reviewing the product for marketplace upload or buyer preview, start with these pages. They use the same documentation layout as the rest of the manual and include real screenshots, layman explanations, developer notes, listing assets, and production QA checks.
A simple, screenshot-backed walkthrough for non-technical buyers and CodeCanyon reviewers.
Open Buyer Guide
Architecture rules for workspaces, canonical aibot_* tables, queues, AI,
connectors, webhooks, and production deployment.
Install notes for the branded Laravel package and WordPress plugin under
packages/oviontech/.
Canva prompts, image sizes, listing copy, tags, changelog, reviewer note, asset manifest, and no-warnings QA report instructions.
Open Listing Kit
Run the production smoke script with APP_DEBUG=false and include the generated
report in marketplace release notes.
Buyer Demo Screenshot Gallery
The same normalized screenshot set is stored in
public/assets/img/demo/screenshots/ and mirrored here for offline documentation.
Desktop captures target 1440x900; mobile captures target 390x844.
Buyer Trust Pages
Explains what is covered, what is customization, and how Envato support status is used.
Open Support NotesShows release cadence, compatibility notes, fixes, and upgrade expectations.
Open ChangelogSummarizes external accounts for AI, email, gateways, OAuth, channels, cron, queues, and HTTPS webhooks.
Open RequirementsCovers AI prompts, webhooks, customer data, mailbox access, staff roles, and audit-sensitive setup.
Open Security Notes- Your visitors see a chat button on your website.
- When they send a message, it comes into your admin dashboard.
- Your staff can reply, or AI can help answer automatically.
- You can save important chats as leads or convert them into tickets.
- You can also train the AI using your own FAQs, files, and website content.
- Businesses that want website live chat plus support management.
- Teams that want AI-assisted replies without giving up human agents.
- Agencies that want to install the same support system for multiple clients.
- Product owners who want chat, leads, help center, and automation in one app.
When You Should Use This Product
Use this product when you want customers to contact you from your website and you want those conversations handled in one central place.
- Customer support for software, services, agencies, and online stores.
- Pre-sales chat such as pricing questions, demo requests, or feature questions.
- Support teams that want a helpdesk plus live chat in the same system.
- Businesses that want to build a knowledge base and let AI answer from it.
- Companies that want to capture leads from chat instead of losing them.
- You want a hosted service where someone else manages the server for you.
- You do not want to install or maintain a Laravel application.
- You only need a tiny contact form and do not need chat, AI, tickets, or reports.
- You want built-in vendor-specific CRM sync without any custom setup.
How This Product Is Usually Used
- A chat button on your site.
- A chat box where they can ask questions, upload files, and leave contact details.
- AI replies, human replies, or a mix of both.
- A feedback form after the conversation if you enable CSAT.
- An inbox with all customer conversations.
- Conversation status, tags, notes, assignments, and priorities.
- Lead and ticket management screens.
- Reports, analytics, AI confidence, and knowledge-gap insights.
What You Do After Downloading It
If you bought or downloaded this product, the normal flow is not "open it and use it immediately." The normal flow is:
- Download the application package to your computer.
- Upload the files to your server or hosting account.
- Create the database and update your environment settings.
- Run the installer and create the first admin account.
- Log in to the dashboard and complete the settings.
- Create your first widget and copy the embed code to your website.
- Test a conversation from your website.
- Then go live.
Simple Example
Imagine you run a software company. You install this app on your server, connect the widget to your marketing site, and visitors start asking things like "What is your price?" or "How do I reset my password?" Your sales or support team sees those chats in the admin panel. AI can answer common questions, and staff can jump in when needed. If the visitor looks like a real buyer, you save the chat as a lead. If the issue needs follow-up, you convert it into a ticket.
What It Can Do
- Website chat widget
- Live agent replies
- Email inbox support
- Attachments and feedback
- AI chat replies
- Knowledge base training
- FAQ generation
- Confidence and escalation logic
- Lead capture
- Ticket conversion
- Automations and webhooks
- Reports and analytics
What Is Inside the Product
If you are technical, the application uses a shared Laravel 12 codebase with workspace-aware routing and runtime configuration. If you are not technical, just read the table below as "which area does what."
| Layer | Purpose | Main Surface |
|---|---|---|
| Platform | Workspace creation, switching, license verification, update checks, demo import. | Platform > Workspaces, Platform Ops |
| Administration | Authentication, settings, permissions, SMTP, notifications, security policies. | Settings, Auth, Roles & Permissions |
| Support Desk | Inbox, widget management, AI, leads, tickets, automations, knowledge, reports. | Chat menu in the admin sidebar |
| Public Runtime | Widget loader, chat APIs, feedback capture, hosted help center. | /widget/loader.js, /api/widget/*, /help-center/* |
Your First-Day Checklist
- Run the installer and create the first platform admin and workspace.
- Open Settings and complete general, company, branding, channels, widget, and OpenAI tabs.
- Verify SMTP before using password reset, alerts, or reply-by-email workflows.
- Create at least one department, reply template, and widget allowed domain.
- Start the database queue worker so attachments, training, and AI jobs process in background.
- Upload FAQ or document sources and confirm they reach the trained state.
- Create an API token and webhook endpoint if the workspace integrates with outside systems.
Read These Pages in This Order
If you are new, do not jump randomly through the docs. Start with these in order.
| Step | Read this page | Why first |
|---|---|---|
| 1 | Requirements | Check whether your hosting/server can run the app. |
| 2 | Installation | Set up the application files and database correctly. |
| 3 | Configuration | Finish the settings needed before real use. |
| 4 | Widgets & Inbox | Learn how the widget works and where chats appear. |
| 5 | AI & Knowledge Base | Train the AI and understand how answers are generated. |
Documentation Map
Non-Technical Buyer Note
If you are not a developer, you can still use this product, but you will usually need one of these:
- A hosting provider or server where Laravel apps can run.
- Basic server setup help from a developer or system admin.
- Access to your website so you can paste the widget embed script.
After the first installation is done, day-to-day use is much easier. Most regular work happens from the admin dashboard, not from code.
Support Model in This Build
The current build is intentionally CodeCanyon-friendly: it ships database-first defaults, OpenAI as the only AI provider, email and generic webhooks as the built-in outbound integrations, and avoids hard dependencies on vector databases or vendor-specific CRM connectors. That makes installation simpler for buyers while still exposing enough API and webhook surface for custom extensions.