OvionDesk AI by Ovion Technology
Ctrl+K
v1.0.0 Changelog
Docs/Buyer Demo Guide

Buyer Demo Guide

This page is written for non-technical buyers and CodeCanyon reviewers. It explains what to click, what each screen proves, and what value the feature gives to a real support team.

Demo rule: demo users, leads, contacts, and connector customers should use @ovion.tech. Public payment gateways should stay in test mode.
Stable buyer login
Use the same account for every live demo reset
Deterministic
Email

admin@ovion.tech

Password

Demo@12345

Workspace

support-demo-oviondesk-ai

Public demo page
The public demo page gives buyers credentials, what-to-test notes, screenshots, and tour links.

1) What This Product Is In Plain English

What the customer sees
  • A public website with pricing, features, FAQ, docs, contact, and demo pages.
  • A support widget where visitors ask questions and share contact details.
  • AI answers when the knowledge base is confident enough.
  • Human support when AI is not confident or the customer needs an agent.
What the support team sees
  • A unified inbox for widget, email, and messaging channel conversations.
  • Tickets, notes, assignments, saved replies, reminders, and SLA views.
  • CRM contacts, companies, deals, and lead conversion.
  • Reports, audit logs, exports, billing, and marketplace readiness checks.

2) Recommended Buyer Demo Flow

Follow this exact flow in the live preview
  1. 1 Public demo and login
  2. 2 SaaS billing
  3. 3 AI QA and handoff
  4. 4 CRM pipeline
  5. 5 Inbox and tickets
  6. 6 Email and channels
  7. 7 Envato support
  8. 8 Addons and PWA
  9. 9 Reports and readiness

3) Public Demo And Guided Tour

Open /demo, use the credential panel, then open /chat/marketplace/tour?demo_tour=buyer&step=0. The tour card should explain each step and support Next, Back, Skip, Restart, Minimize, Resume, drag on desktop, and fixed-bottom behavior on mobile.

If a target element is missing, the tour must show a fallback card. A broken tour makes the live preview feel unfinished.

4) SaaS Billing

SaaS billing page
Billing proves that the product can run as a SaaS: plans, limits, subscriptions, invoices, coupons, and gateway test mode.
Explain to buyers
  • Plans control users, agents, widgets, API tokens, channels, storage, knowledge sources, and AI messages.
  • Invoices are printable HTML invoices, so no extra PDF package is required.
  • Manual payments stay pending until an admin approves or rejects them.
Developer notes
  • Usage counters must be workspace-scoped.
  • Renewal should reset period-based counters.
  • Limit blocking should not delete existing data.

5) AI QA, Citations, And Handoff

AI QA and handoff screen
AI is positioned as reliable support: citations, confidence, fallback reason, provider test status, and human handoff.
Buyer value
  • Citations answer "why did AI say this?"
  • Confidence answers "how sure is AI?"
  • Human handoff answers "what happens when AI is not sure?"
Developer notes
  • AI usage should count against the plan ai_messages limit.
  • Low confidence should emit ai.handoff.requested.
  • Addons must not store AI keys or run inference.

6) CRM Pipeline

CRM pipeline
CRM-lite keeps support and sales context together: contacts, companies, deals, pipeline, and lead conversion.

7) Unified Inbox And Tickets

Unified inbox
The inbox is where human agents work: replies, tickets, notes, mentions, reminders, assignments, and SLA views.
Do not demonstrate email inbox without a scheduler and queue worker. Buyers will notice if sync and replies feel fake.

8) Email And Messaging Channels

Channels page
Visible channel support is important for CodeCanyon buyer perception: IMAP/SMTP, Gmail, Outlook, WhatsApp, Telegram, Slack, Facebook, and Instagram.
What to show
  • Webhook URL.
  • Signature or secret validation status.
  • Last inbound message.
  • Last outbound reply and delivery state.
Common mistakes
  • HTTP webhook URLs instead of HTTPS.
  • Wrong Slack signing secret.
  • Wrong Telegram secret token.
  • Twilio sender mismatch.

9) Envato Support

Envato support verification
Envato verification is a strong CodeCanyon-specific feature: valid, expired, refunded, unsupported, invalid, and failed states.

10) Addons And Agent PWA

Addon package index
The addon package index proves the product has an ecosystem: WordPress, WooCommerce, Shopify, Perfex CRM, WHMCS, and Universal JS SDK.
Agent PWA
The Agent PWA gives the buyer a mobile support workflow with push-ready notification hooks.

11) Reports, Website, And Marketplace Readiness

Reports
Reports show buyer value after launch: AI usage, SLA risk, backlog, channel volume, and workspace usage.
Website CMS
Public website pages help the product look complete: pricing, features, FAQ, docs, contact, terms, privacy, demo, and changelog.
Final buyer proof should include php artisan test passing and the production smoke report with APP_DEBUG=false.
← Back: Overview Next: Developer Notes →