TicketPro
TicketPro focuses on tickets, SLA, evidence, and support accountability; SupportHub adds CX platform depth, Customer 360, live chat, APIs, and tenancy.
Laravel
CX Platform
Live Chat
SupportHub
Support desk operations, AIBot live chat, Customer 360, SaaS tenancy, and governed CX automation in one Laravel platform.
SupportHub chat automation scoped to the SupportHub CX package
Native tickets, SLA operations, support teams, and requester workflows
Customer 360, feedback, community, status, success, and analytics context
Product at a glance
What SupportHub does
SupportHub helps teams run tickets, live chat, Customer 360, CX analytics, AIBot handoff, tenant workspaces, and support automation.
SupportHub is the customerpro-style customer platform: it keeps the ticket desk foundation but expands it into live chat, Customer 360, AIBot handoff, feedback, status, customer success, analytics, tenant workspaces, permission isolation, automation, REST, GraphQL, and developer surfaces. It is for teams that need customer context and CX operations around support, not only a ticket queue.
Best for
Teams that need support tickets plus live chat, customer context, analytics, tenant workspaces, and governed automation.
Main outcome
Tickets and live chat in one CX workspace
Starts from
USD 229
Why this product is different
SupportHub is different because it expands the support desk into a customer/CX platform with live chat, Customer 360, AIBot handoff, analytics, tenant workspaces, and APIs.
TicketPro is the focused ticket desk. SupportHub keeps that foundation and adds broader customer context, live chat conversion, feedback, success, status, CX analytics, SaaS tenancy, REST, GraphQL, automation, and platform operations.
OvionDesk
OvionDesk is the AI support desk; SupportHub is the broader customer platform where AI is one capability among CX, analytics, tenancy, and APIs.
Generic helpdesk suites
SupportHub combines ticket foundation, Customer 360, SaaS productization, REST/GraphQL, and automation in a Laravel product.
10 standout features
The 10 strongest reasons to choose SupportHub
Choose a feature to see why it matters, what to inspect in the demo, and how it supports the buying decision.
Tickets
Ticket intake, queues, replies, SLA state, assignments, approvals, case files, and reports remain the foundation.
Why it matters
This matters because tickets is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect Ticket intake, Requester portal, Support reports. Confirm the screens show real setup, records, status, and operating context instead of a static placeholder.
Buying signal
This is a strong buying signal when your team needs tickets handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Proof to inspect
- Ticket intake
- Requester portal
- Support reports
Live chat
Live conversations can become native support tickets and feed customer context.
Why it matters
This matters because live chat is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect Live chat conversion, Workspace tokens, Scoped APIs. Confirm the screens show real setup, records, status, and operating context instead of a static placeholder.
Buying signal
This is a strong buying signal when your team needs live chat handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Proof to inspect
- Live chat conversion
- Workspace tokens
- Scoped APIs
Customer 360
Customer and organization context, health, feedback, success signals, and history sit around the support record.
Why it matters
This matters because customer 360 is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect Customer 360, Customer health, Executive analytics. Confirm the screens show real setup, records, status, and operating context instead of a static placeholder.
Buying signal
This is a strong buying signal when your team needs customer 360 handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Proof to inspect
- Customer 360
- Customer health
- Executive analytics
AIBot handoff
AIBot-assisted conversations can hand off into human support and native ticket workflows.
Why it matters
This matters because aibot handoff is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect Tenant workspaces, REST and GraphQL, Webhooks. Confirm the screens show real setup, records, status, and operating context instead of a static placeholder.
Buying signal
This is a strong buying signal when your team needs aibot handoff handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Proof to inspect
- Tenant workspaces
- REST and GraphQL
- Webhooks
Knowledge workflows
Knowledge content, resolved-ticket summaries, and human-reviewed publishing support support operations.
Why it matters
This matters because knowledge workflows is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect the setup screen, the working records, the permission path, and the report or history view connected to this feature.
Buying signal
This is a strong buying signal when your team needs knowledge workflows handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
CX analytics
Analytics, executive views, customer health, status, feedback, and success data help leaders see beyond ticket counts.
Why it matters
This matters because cx analytics is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect the setup screen, the working records, the permission path, and the report or history view connected to this feature.
Buying signal
This is a strong buying signal when your team needs cx analytics handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Tenant workspaces
Workspaces, branding, domains, limits, and module entitlements support SaaS-style customer operations.
Why it matters
This matters because tenant workspaces is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect the setup screen, the working records, the permission path, and the report or history view connected to this feature.
Buying signal
This is a strong buying signal when your team needs tenant workspaces handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Permissions and isolation
Roles, scopes, API actors, and tenant isolation keep platform data controlled.
Why it matters
This matters because permissions and isolation is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect the setup screen, the working records, the permission path, and the report or history view connected to this feature.
Buying signal
This is a strong buying signal when your team needs permissions and isolation handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
REST and GraphQL
Developer surfaces let external systems read and write customer platform data.
Why it matters
This matters because rest and graphql is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect the setup screen, the working records, the permission path, and the report or history view connected to this feature.
Buying signal
This is a strong buying signal when your team needs rest and graphql handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
Automation
Rules, playbooks, webhooks, report schedules, and operations checks reduce manual support work.
Why it matters
This matters because automation is part of the working SupportHub workflow, not just a label on a sales page. Buyers can see how it connects to ownership, records, follow-up, permissions, and reporting inside the same product.
What to inspect in the demo
In the demo, inspect the setup screen, the working records, the permission path, and the report or history view connected to this feature.
Buying signal
This is a strong buying signal when your team needs automation handled in the same Laravel workspace as the rest of SupportHub, with less manual reconciliation after the demo.
How teams use it
From setup to daily operation
A simple operating path so buyers can understand what happens after installation.
-
01
Configure tenant workspaces, branding, domains, users, roles, and permission scopes.
-
02
Set up channels, chat widgets, AIBot handoff rules, knowledge, and automation.
-
03
Triage live conversations and convert important chats into native tickets.
-
04
Review Customer 360, organization context, feedback, status, health, and success signals.
-
05
Use analytics, REST, GraphQL, API keys, OAuth actors, webhooks, and reports for productized support operations.
Proof and fit
Check fit, proof, model, and buying confidence
Use these compact checks before moving to the live demo, docs, or pricing tab.
Who should consider SupportHub
Best for
- Support teams that need customer context beyond tickets
- SaaS platforms with tenant workspaces and customer operations
- Teams that need live chat, analytics, REST, GraphQL, and AIBot handoff
Not just for
- Not only a ticket queue
- Not only live chat
- Not only a knowledge base
- Platform
- Laravel customer/CX support platform
- Source reference
- supporthub local app and SupportHub docs
- Main modules
- Tickets, live chat, Customer 360, AIBot handoff, analytics, tenancy, APIs
- Operational depth
- Permissions, isolation, tenant branding, REST, GraphQL, webhooks, automation, CX reporting
Practical use cases
Customer support plus CX context
Resolve tickets while seeing customer, organization, feedback, success, and health context.
Tenant-based support platform
Use workspace isolation, branding, domains, entitlements, API keys, and permissions.
Live chat to ticket operation
Run widget chat, AIBot handoff, agent inbox, native ticket conversion, and CX reporting.
Where the explanation comes from
Dashboard workspace docs
Documents the support workspace foundation and operational screens.
Open docs
API reference docs
Covers API surfaces used by the customer platform and integrations.
Open docs
Automation and playbooks docs
Explains automation, playbooks, and process control around customer operations.
Open docsAIBot, AI Copilot, Customer 360 summaries, and governed CX assistance
SupportHub can explain AI as a governed platform capability: AIBot handoff, copilot drafts, knowledge search, customer summaries, sentiment, priority, SLA prediction, report summaries, and executive views with human approval guardrails.
- AI Copilot suggestions are drafts and do not close cases automatically.
- AI knowledge search is restricted to approved sources and resolved-ticket summaries.
- AI trust/reporting records action, status, confidence, source references, user, and guardrail signals.
Ownership, tenancy, and operations
SupportHub is a Laravel customer/CX SaaS platform with tenant workspaces, branding, custom domains, usage limits, module entitlements, permissions, REST, GraphQL, API keys, OAuth actors, webhooks, automation, and reports.
- Tenant workspaces separate customer operations and branding.
- Module entitlements, usage limits, custom domains, permissions, and API scopes support productized plans.
- REST, GraphQL, webhooks, reports, Demo Hub, and operations checks support platform ownership.
Buyer questions answered
Common buyer questions
Quick answers for fit, users, workflow, and the buying decision after the main proof sections.
What does SupportHub do?
SupportHub combines ticket intake, live chat, Customer 360, AIBot handoff, support workflows, feedback, status, customer success context, CX analytics, tenant workspaces, automation, REST, GraphQL, and scoped APIs.
What is SupportHub for?
It is for teams that need a customer platform around support: tickets plus live conversations, customer context, analytics, tenant isolation, automation, and developer access.
Who can use SupportHub?
Support teams, customer success teams, SaaS companies, product teams, agencies, tenant-based platforms, and support operations leaders can use SupportHub.
How do teams use SupportHub?
Teams configure workspaces, channels, chat widgets, knowledge, handoff rules, permissions, APIs, and automation; triage conversations; resolve tickets; review Customer 360; and monitor CX analytics.
When is SupportHub a good fit?
Use it when live chat, Customer 360, AIBot handoff, customer health, analytics, tenant workspaces, REST, GraphQL, and APIs matter alongside tickets.
Project details
A complete implementation brief for SupportHub
A documentation-guided view of the real workflow, evaluation checks, launch options, and buyer evidence behind this project.
91% buyer evidence ready
Open product docs
The project in context
SupportHub in a real buyer workflow
SupportHub expands the TicketPro-style support desk base into a broader CX platform with native tickets, AIBot live chat, Customer 360, feedback, status, AI governance, SaaS tenancy, analytics, REST, and GraphQL.
- Built for
- Teams that need ticket operations plus live chat, Customer 360, AI guardrails, SaaS tenancy, analytics, and developer APIs in one SupportHub package
- The operating gap
- Buyers need to understand how SupportHub behaves before checkout.
- After launch
- Use the demo, docs, screenshots, and version history to decide whether it fits the launch plan.
Evaluation route
View all screens
What to inspect in the product
-
01
Screenshot 1
Open this product screen and confirm the workflow, layout, and data state match your use case.
- Screenshot 1
-
02
Screenshot 2
Open this product screen and confirm the workflow, layout, and data state match your use case.
- Screenshot 2
-
03
Screenshot 3
Open this product screen and confirm the workflow, layout, and data state match your use case.
- Screenshot 3
-
04
Screenshot 4
Open this product screen and confirm the workflow, layout, and data state match your use case.
- Screenshot 4
Who it helps
Practical project scenarios
Before: Tickets, chats, customer history, organization context, and analytics are split across tools.
With SupportHub: Use SupportHub to receive live chat, convert chats into native tickets, view Customer 360 context, and track support health in one workspace.
Result: The team can run support as a CX operation instead of a queue-only helpdesk.
Before: Workspace membership, package limits, tenant branding, and chat access need product-grade isolation.
With SupportHub: Review tenant workspaces, package entitlement, AIBot access, role permissions, installer settings, custom domains, and scoped APIs.
Result: SupportHub can be sold and operated as a tenant-aware support platform with safer access boundaries.
Before: Support data needs APIs, webhooks, GraphQL, analytics, and governed automation instead of manual exports.
With SupportHub: Use REST/GraphQL, webhooks, scoped API keys, analytics, and AI approval controls around tickets, chats, customers, and workflows.
Result: The buyer gets integration depth without turning AI or chat access into a cross-app security risk.
In the real world
How the workflow changes the day
The buyer has a workflow need but does not want to purchase only from a feature list.
They review the story, screenshots, demo roles, docs, changelog, support terms, and comparison rows.
The buying decision becomes a documented test drive instead of a guess.When this project is the right choice
SupportHub fits teams that need the TicketPro support-desk base plus AIBot live chat, CX Inbox, Customer 360, tenant workspaces, AI governance, analytics, REST, and GraphQL in one Laravel-owned CX platform.
- SupportHub keeps the TicketPro-style ticket base and expands it with live chat, CX Inbox, Customer 360, tenant isolation, analytics, and developer APIs.
- SupportHub includes scoped chat automation for CX workflows; OvionDesk is the separate self-hosted AI support desk product.
- Chat-to-ticket conversion keeps requester, organization, conversation, and timeline context in SupportHub.
- Tenant-safe isolation rules distinguish platform super admin, SaaS workspace users, and organization users before exposing chat data.
Four checks that prevent a bad purchase
-
Choose SupportHub only when CX depth is needed
Use TicketPro for a focused support desk. Use SupportHub when live chat, AIBot, Customer 360, tenant workspaces, analytics, and APIs matter.
-
Confirm AIBot entitlement scope
AIBot should be enabled through SupportHub package limits and should not be wired into ecommerce, CRM, TicketPro, or other apps.
-
Review tenant and organization isolation
Confirm chat access resolves through workspace membership, native ticket links, requester email, and organization permissions without oldest-workspace fallback.
-
Inspect APIs and analytics needs
Review REST, GraphQL, webhooks, analytics, queue, scheduler, mail, and provider requirements before checkout.
Pause and ask first if…
- Only need a classic ticket desk — TicketPro is the cleaner first option when live chat, Customer 360, tenant packaging, APIs, analytics, or AI governance are not required.
- Need a dedicated AI support desk — Use OvionDesk when the main need is self-hosted AI support with knowledge QA, citations, confidence, handoff, inbox, tickets, CRM, billing, channels, and connectors.
- Tenant isolation cannot be reviewed — Pause if workspace, organization, requester, and permission boundaries cannot be checked before production use.
Launch path
Choose how you will get live
Self-install from SupportHub docs
Open docs
Use the docs, requirements, installer screens, AIBot package notes, tenant setup, and post-install checks.
Installation service
Plan setup
Ask Ovion to scope hosting setup, AIBot entitlement, queue/mail checks, tenant isolation, API keys, and launch handoff.
Compare with TicketPro
Compare both
Open a side-by-side comparison before buying if the team is unsure whether it needs classic helpdesk or full CX platform depth.
Buyer evidence
What the project makes visible
Install readiness
PHP 8.2+, Composer 2.x, Laravel 12 compatible hosting
Support scope
6 months included
Update confidence
Version 1.0.0 / Updated 2026-07-05
A thorough evaluation records
- Chat automation scope reviewed
- Chat-to-ticket path inspected
- Customer 360 reviewed
- Tenant isolation checked
- TicketPro comparison captured
Project reference
Compare this product
The details to compare side by side
- Primary workflow
- Full CX/support platformTickets, live chat, CX Inbox, Customer 360, tenant workspaces, analytics, AI governance, REST, and GraphQL.
- Difference from TicketPro
- Ticket desk plus CX layerTicketPro focuses on helpdesk tickets. SupportHub keeps that base and adds live chat, AIBot, Customer 360, SaaS tenancy, analytics, and developer surfaces.
- Chat automation scope
- SupportHub CX packageSupportHub includes scoped chat automation for its CX workflows. OvionDesk is the separate self-hosted AI support desk product.
- Chat ownership
- Tenant-safe isolationSuper admins can see all workspaces; SaaS users see their workspace; organization users see owned chats only when permissions allow it.
- Developer surface
- REST and GraphQLAPIs cover tickets, chats, conversations, customers, analytics, workflows, SaaS controls, and webhooks.
- Commercial model
- Premium one-time Laravel product licenseSupportHub starts at USD 229 for customer/CX platform depth, tenant customer workflows, analytics, and developer surfaces.
Gallery
SupportHub screens and product views
Review the key screens, then open any preview at full size.
21 previews
Open Demo
Featured
SupportHub product preview
SupportHub expands the TicketPro-style support desk base into a broader CX platform with native tickets, AIBot live chat, Customer 360, feedback, status, AI governance, SaaS tenancy, analytics, REST, and GraphQL.
Screenshot 2
SupportHub screenshot 1
Product screen used for marketplace evaluation.
Screenshot 3
SupportHub screenshot 2
Product screen used for marketplace evaluation.
Screenshot 4
SupportHub screenshot 3
Product screen used for marketplace evaluation.
Screenshot 5
SupportHub screenshot 4
Product screen used for marketplace evaluation.
Screenshot 6
SupportHub screenshot 5
Product screen used for marketplace evaluation.
Screenshot 7
SupportHub screenshot 6
Product screen used for marketplace evaluation.
Screenshot 8
SupportHub screenshot 7
Product screen used for marketplace evaluation.
Screenshot 9
SupportHub screenshot 8
Product screen used for marketplace evaluation.
Screenshot 10
SupportHub screenshot 9
Product screen used for marketplace evaluation.
Screenshot 11
SupportHub screenshot 10
Product screen used for marketplace evaluation.
Screenshot 12
SupportHub screenshot 11
Product screen used for marketplace evaluation.
Screenshot 13
SupportHub screenshot 12
Product screen used for marketplace evaluation.
Screenshot 14
SupportHub screenshot 13
Product screen used for marketplace evaluation.
Screenshot 15
SupportHub screenshot 14
Product screen used for marketplace evaluation.
Screenshot 16
SupportHub screenshot 15
Product screen used for marketplace evaluation.
Screenshot 17
SupportHub screenshot 16
Product screen used for marketplace evaluation.
Screenshot 18
SupportHub screenshot 17
Product screen used for marketplace evaluation.
Screenshot 19
SupportHub screenshot 18
Product screen used for marketplace evaluation.
Screenshot 20
SupportHub screenshot 19
Product screen used for marketplace evaluation.
Screenshot 21
SupportHub screenshot 20
Product screen used for marketplace evaluation.
Pricing
Pick the right SupportHub license
SupportHub is priced as a full CX platform because it adds live chat, Customer 360, AIBot handoff, knowledge workflows, CX analytics, tenant workspaces, permissions, REST, GraphQL, and automation around the support desk foundation.
Priced as a full solution
- Ticket desk plus CX platform depth
- Live chat, Customer 360, AIBot handoff, analytics, and knowledge workflows are included
- Tenant workspaces, permissions, REST, GraphQL, webhooks, and automation support SaaS operations
- Broader customer platform value justifies pricing above a focused helpdesk
License tier
Single App License
1 live app / 3 staging/dev apps
One SaaS, product, or support team needing customer platform depth.
Covers one live SupportHub deployment with tickets, live chat, Customer 360, AIBot handoff, analytics, tenancy, APIs, and automation. USD 229 Recommended Business 2 Apps License 2 live apps / 6 staging/dev appsTwo CX workspaces, two brands, or a client handoff with separate production use.
Adds a second live CX platform deployment for multi-brand support, client delivery, or staged customer operations. USD 399 License tier Agency Unlimited License Unlimited live apps / Unlimited staging/dev appsAgencies and platform operators deploying customer/CX systems repeatedly.
Designed for repeated CX platform launches where tenant workspaces, Customer 360, live chat, APIs, analytics, and automation repeat. USD 799Product workflow
Core workflows in SupportHub
Review the main operating areas a buyer should understand before opening the demo or choosing a license.
Support Desk Foundation
SupportHub keeps the ticket queue, requesters, SLAs, case files, support teams, reports, and support operations base.
- Ticket intake and queue management
- Requester portal and public support
- SLA, assignment, approvals, and case files
- Reports, invoices, operations checks, and support teams
AIBot Live Chat
The bundled AIBot package is scoped to SupportHub and converts live chat into native SupportHub tickets.
- SupportHub route prefixes
- Live chat to native ticket conversion
- Workspace tokens and scoped APIs
- Package positioning included in product metadata
Customer 360 And CX
Customer 360 joins ticket, conversation, feedback, organization, status, success, and analytics context for broader CX work.
- Customer and organization intelligence
- Feedback, community, status, and success modules
- Customer health and next-best action context
- Advanced analytics and executive views
AI Governance
AI capability matrix, guardrails, audit-only controls, summaries, suggestions, and Demo Hub coaching stay governed by permission.
- AI capability matrix and source-bound guardrails
- Ticket, chat, Customer 360, and demo assist workflows
- Human approval defaults for risky actions
- Usage, audit, and provider settings
SaaS And Developer Platform
Tenant branding, custom domains, usage limits, module entitlements, REST, GraphQL, and webhooks support productization.
- Tenant setup, subscriptions, branding, and domains
- REST and GraphQL developer surfaces
- Scoped API keys, OAuth actors, and webhooks
- Phase 15-25 platform module coverage
Isolation And Permissions
Chat access is centrally scoped: platform super admin sees all, SaaS users see their workspaces, and organization users see owned chats by permission.
- No oldest-workspace fallback for non-super users
- Organization ownership through tickets or requester matching
- 403/404 handling for out-of-scope reads and mutations
- Shared scope for inbox, reports, APIs, GraphQL, and Customer 360
Demo access
Try the live SupportHub demo
Open the hosted demo, use shared credentials when provided, and review the documentation for setup details.
Demo Login
admin@ovion.tech
Demo@12345
Buyer trust
Compatibility, review, and support checks
Digital purchases are reviewed case by case when the product is not as described or cannot be accessed.
6 months of setup and product support are included with this license.
Manual code review and compatibility checks are tracked before products are promoted.
Changelog
Version history
Initial SupportHub marketplace release with CX platform positioning, AIBot paid bundle, chat isolation, installer hardening, docs, screenshots, and cPanel split archives.
Verified reviews
No published reviews yet
Verified buyer reviews will appear here after moderation.
Log in with a buyer account to leave a verified purchase review.
Product Q&A
Pre-sale answers from the operator
No published Q&A yet. Ask a product-specific question below.
