Feature 01 / 06
Unified inbox
Email, web widget, live chat, portal, and API merge into a single triage view with SLA timers, assignment, and macros.
Multi-tenant helpdesk
Customer support that scales with your tenants
Helpdash gives SaaS teams, agencies, and MSPs one workspace to run helpdesk operations across every customer brand — tickets, live chat, and a knowledge base, with white-label custom domains and strict per-tenant data isolation.
ACME · Tickets
All open · 27 1.2k
Open
27
Pending
9
Breach
2
CSAT 7d
94%
- SC −02:14
SSO loops on Safari 17.4
- AB 00:42
Webhook retries returning 500
- P 01:17
Add a second custom domain
- JK 03:55
Macro shortcut conflicts
- DA 06:12
Configure SLA by ticket priority
30-second tour
How a Helpdash workspace runs support
01
Capture
Email, web widget, live chat, portal, or API — every request becomes a tracked ticket in one inbox.
02
Triage
Auto-route with workload-aware rules, paste a canned reply in one keystroke, and watch the SLA clock pause while you wait on the customer.
03
Resolve
Reply, link a KB article, hand off to a teammate, then send a signed CSAT survey on resolution — automatically.
Multi-tenant, by design
One Helpdash, every customer’s brand
Spin up a fresh workspace in minutes — own subdomain, own logo, own palette, own locale. Data stays scoped at the row level, agents stay scoped at the team level, and your end customers never see Helpdash branding.
- Row-level tenant isolation enforced at every query
- Workspace-scoped roles with fine-grained permissions
- Custom domain + branded outbound email
- Per-workspace locale, timezone, and business hours
https://support.acme.io
A
ACME Support
27
3
live
https://help.rivo.app
R
Rivo Support
14
1
live
Capability pillars
Everything a modern support team actually uses
Helpdash ships the full workflow — not just a ticket table. Every pillar below maps to a production-ready module you can turn on per workspace.
Feature 02 / 06
Sub-second live chat
WebSocket-powered conversations with typing indicators, agent presence, file uploads, and a 100% Helpdash-branded widget.
Feature 03 / 06
Knowledge base
Multi-locale articles with version history, public/private visibility, and CSAT signals fed straight from your tickets.
Feature 04 / 06
Automation rules
If/then routing on intake, status transitions, time-based escalations, and webhook triggers — built without code.
Feature 05 / 06
CSAT & SLA reporting
Signed survey links on resolution, breach alerts, response/resolution dashboards exported to CSV or webhook.
Feature 06 / 06
White-label everywhere
Custom domain, logo, palette, and email From-address per workspace. End customers never see Helpdash branding.
Live chat that doesn’t feel like email
Sub-second exchanges with the same context as the ticket
A WebSocket-backed widget that opens in popup, modal, or drawer mode. Every conversation lands as a ticket the moment a customer leaves — so nothing falls between channels.
- Typing indicators · read receipts · presence
- File uploads with scoped storage
- Agent macros and KB snippets in-thread
- In-widget CSAT the moment a chat wraps
ACME Support
Online · replies in ~2 min
A
Hey 👋 — how can we help today?
Widget snippet won't load on Safari.
A
A
Add widgets.helpdash.io to your CSP. Docs link incoming. 👇
Honest comparison
Helpdash vs. Zendesk vs. Freshdesk
Six things that matter to teams running support across multiple brands. We’d rather show the gap than hide behind a star rating.
Six multi-brand features
Helpdash wins on 6 of 6
Zendesk
0 / 6
Helpdash
0 / 6
Freshdesk
0 / 6
- 01 Multi-tenant + white-label native
- 02 Bidirectional Jira sync (Cloud + Data Center)
- 03 Custom domain + branded email
- 04 Embeddable widget · popup / modal / drawer
- 05 Multi-language out of the box
- 06 Sub-second WebSocket chat latency
Customers
Built for teams running support across many brands
“Run a separate branded desk per client from one login — pricing is per workspace, and you add agents up to the plan cap without a per-seat charge.”
Agency owner
“White-label clients each get their own subdomain, palette, and locale, so end customers never see Helpdash branding.”
MSP founder
“SLA timers pause the moment you're waiting on the customer, so first-response numbers reflect real work, not handover time.”
Support lead
Plans
One price per workspace — pick the capability you need
Each plan is a full, isolated workspace billed per month. Run one, or run one per customer brand — they never share data.
Starter
$29 / workspace / mo
Core ticketing for a small team getting its support organised.
Start 14-day trial- Up to 5 agents · 3 projects
- Email-to-ticket + embeddable web widget
- 500 tickets / month · 10 MB attachments
- Roles & permissions · activity log
- In-app notifications
Pro
$89 / workspace / mo
Live chat, automation, SLAs and a knowledge base for growing support teams.
Start 14-day trial- Up to 25 agents · 25 projects
- Everything in Starter, plus:
- Live chat · knowledge base · customer portal
- SLAs · automation · CSAT · canned replies
- Reports · API keys · Jira · LDAP · Telegram
- 10,000 tickets & 2,000 chats / month
Enterprise
$249 / workspace / mo
Unlimited scale, white-label branding and compliance for large organisations.
Talk to sales- Unlimited agents, tickets & chats
- White-label branding · custom email templates
- Full billing suite · 200 MB attachments
- Dedicated account manager · 24/7 support
- 99.9% uptime SLA · on-premise option
- 30-day evaluation
FAQ
Frequently asked questions
What does multi-tenant actually mean for my data?
Each workspace is enforced as a tenant scope at the database query layer — row-level isolation enforced by a workspace key and a global query boundary. Agents, tickets, articles, and uploads from one workspace are simply unreachable from another, including via the API.
Do you charge per agent?
No — you pay one price per workspace, per month, not a fee per seat. Each plan includes an agent allowance (up to 5 on Starter, up to 25 on Pro, unlimited on Enterprise), so you add agents up to your tier's cap without a per-seat charge.
Can I use my own domain?
Yes. On Pro and Enterprise you point a CNAME to Helpdash and serve the portal and email From-address from your own domain — we issue and rotate the certificate. Starter workspaces run on a yourname.helpdash.io subdomain.
Which channels do you support out of the box?
Email-to-ticket, an embeddable web widget (popup, modal, or drawer), live chat over WebSocket, a customer portal, REST + webhooks, and an inbound API for custom intake (call-center, SMS gateways, etc.).
Is there a Jira integration?
Yes — bidirectional sync with both Jira Cloud and Jira Data Center. Open a Jira issue from a ticket, mirror status, and post comments back. LDAP, Google SSO, and webhooks ship in the same release.
Where is the data hosted?
Helpdash is EU-hosted, and every workspace's data is isolated per tenant at the row level. For regulated deployments — dedicated single-tenant, on-prem, or a customer-supplied VPC on Enterprise — talk to us about residency requirements.
Stand up your first workspace in under five minutes
Start with a 14-day trial — no credit card, cancel any time.