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
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.
30-second tour
Email, web widget, live chat, portal, or API — every request becomes a tracked ticket in one inbox.
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.
Reply, link a KB article, hand off to a teammate, then send a signed CSAT survey on resolution — automatically.
Multi-tenant, by design
ACME Support
Rivo Support
Capability pillars
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 01 / 06
Email, web widget, live chat, portal, and API merge into a single triage view with SLA timers, assignment, and macros.
Feature 02 / 06
WebSocket-powered conversations with typing indicators, agent presence, file uploads, and a 100% Helpdash-branded widget.
Feature 03 / 06
Multi-locale articles with version history, public/private visibility, and CSAT signals fed straight from your tickets.
Feature 04 / 06
If/then routing on intake, status transitions, time-based escalations, and webhook triggers — built without code.
Feature 05 / 06
Signed survey links on resolution, breach alerts, response/resolution dashboards exported to CSV or webhook.
Feature 06 / 06
Custom domain, logo, palette, and email From-address per workspace. End customers never see Helpdash branding.
Live chat that doesn’t feel like email
ACME Support
Online · replies in ~2 min
Hey 👋 — how can we help today?
Widget snippet won't load on Safari.
Add widgets.helpdash.io to your CSP. Docs link incoming. 👇
Honest comparison
Six multi-brand features
Customers
“We migrated 11 client desks from Zendesk in a weekend. Per-workspace pricing alone paid for the year.”
Mira Solak
“Our white-label clients each get their own subdomain, palette, and locale. They never know Helpdash exists.”
Jonas Klein
“The SLA pause-on-customer-reply pattern alone shaved 38 minutes off our median first response.”
Renata Faria
FAQ
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.
No. Pricing is per workspace, per month. Add as many agents as you need to a workspace — even on the Pro plan. The Enterprise plan is the only one with negotiated capacity, and it’s still workspace-based, not seat-based.
Yes. Every paid plan can point a CNAME to Helpdash and serve the portal and email From-address from your domain. We issue and rotate the certificate. Free plans use a yourname.helpdash.io subdomain.
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.).
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.
EU (Frankfurt) by default. UK and US regions are available on Pro and above; a fully isolated single-tenant deployment is available on Enterprise, including on-prem and customer-supplied VPC.
Free for solo founders and pilot teams. No credit card. Cancel any time.
We respect your privacy
Helpdash uses minimal first-party analytics to improve this site. We do not run third-party trackers or advertising pixels. Accept to allow page-view analytics, reject to opt out entirely. Read the privacy policy