helpdash/inbox · #HD-423 · Multi-tenant helpdesk platform replied · 05 May 2026

01 Overview

One platform. Many client brands. Zero data leaks.

Helpdash gives SaaS teams, agencies, and MSPs a single workspace to run helpdesk operations across every customer brand — with embeddable widgets, white-label custom domains, and strict per-tenant data isolation baked into the database layer.

Start a free 14-day trial

● 14-day trial · no card · cancel via one ticket

acme.helpdash.io · queue 3 open · click to expand

customer · Sarah M. · 2m ago

I added a new screenshot to this thread but the agent already closed the ticket.

incident priority · urgent SLA · 02:14:31

● live · auto-refresh every 30s

⏱ 30-second tour

From idea to live in three steps.

no setup call · no demo gate · no card

01 /onboarding

Pick a slug

Type a name, get a workspace. We provision the database row, the JWT scope, and your subdomain in one shot.

workspace ready in 12s
02 /branding

Make it yours

Logo, accent colour, custom domain (auto-TLS via DNS verify), and copy in any of 4 languages — all without a redeploy.

fully white-label
03 /launch

Pick your surface

Embed the widget on your site, share the customer portal link, or do both. Tickets land in the same queue either way.

live · accepting tickets

+ Built for

Three teams. One platform. No compromise.

3 personas · pick yours

01 · saas see how →

SaaS support teams

One platform, one agent layer, every customer on their own brand. Your support stays one team while every tenant gets a white-label home.

02 · agency see how →

Agency client desks

Each client gets their own subdomain, brand, and ticket queue. Run the operation from one control plane with cross-tenant visibility.

03 · msp see how →

MSP ticket queues

API-driven ticket ingestion from monitoring tools, SLA tracking by service tier, automation rules per client. Scales past 10k/month.

02 Capabilities

Everything support teams need to run multi-brand operations

08 modules · all tiers

module · building FT-101

Multi-tenant by design

Single database, shared schema, tenant_id global scopes. A query physically cannot leak between tenants — verified by the test suite on every PR.

Subdomain ● live

● acme.helpdash.io

Agent app + admin

tenant_id = 17 · isolated

Custom ● live

● support.acme.com

Customer portal

tenant_id = 17 · isolated

Widget ● live

● widgets.helpdash.io

In-product chat

tenant_id = 17 · isolated

module · globe FT-102

White-label custom domains

Map support.yourbrand.com to a tenant. DNS TXT verification, automatic Let's Encrypt issuance via Caddy, hot-path resolver on every request.

tenant/custom-domain ● 2 of 3 verified

host support.acme.com

Step 01

DNS TXT proof

_helpdash=ok-a8f2…

verified

Step 02

CNAME points to us

→ edge.helpdash.io

verified

Step 03

TLS issuing

Let's Encrypt · Caddy

pending

module · code FT-103

Embeddable widget

One script tag, fully customisable: branding, colours, container type (popup / modal / drawer), position, fields. Surfaces tickets and live chat.

embed/widget · live preview ● editing

controls

accent

container

Need help?

How can we help today?

module · ticket FT-104

Industry-standard tickets

Type / status / priority / channel enums, watchers, tags, due dates, SLA clock with pause logic, status transition gating, full history.

workflow_editor · ticket_status_graph 5 states · 4 transitions

open in_progress waiting_customer resolved closed

sla paused while in waiting_customer

required fields · per project 3 projects use this

module · message-circle FT-105

Real-time chat

WebSocket-powered chat between agents and customers via Laravel Reverb. Typing indicators, read receipts, file uploads, message pinning.

acme.helpdash.io · chat / #room-204 reverb · live

Erik · agent · 14:32

Hi Sarah — I see your refund issue. Pulling the invoice now.

Sarah · customer · 14:33

Thanks. Reference #INV-8821. The amount is wrong by $40.

EL Erik is typing

module · star FT-106

CSAT + Knowledge Base

Signed CSAT survey link on ticket resolve. Per-tenant KB articles with revisions, views, and feedback capture. Both surfaced through the widget.

acme.helpdash.io · knowledge base 42 articles · 18.2k views (30d)

password reset 3 hits · logged

How to reset your account password account 4,128 views · 92% helpful
Configure SSO with Okta in five minutes sso 1,872 views · 88% helpful
Refund policy for prorated subscriptions billing 996 views · 76% helpful
Webhook delivery failures — debug checklist developer 612 views · 81% helpful

module · plug FT-107

Jira sync (Cloud + DC)

Strategy-pattern sync with Jira Cloud or Jira Data Center. Configure from Settings, no code. LDAP directory binding also supported.

integrations · jira ● synced 14:32

strategy JiraDataCenterStrategy tenant: aurorabank

last run · 14:32:08 3 issues mirrored

HD-1042 → SUP-2099 linked
HD-1041 → SUP-2098 linked
HD-1039 → SUP-2097 queued

module · mail FT-108

Magic-link customer portal

Customers log in by clicking a signed link in their email — no password, no friction. Submit tickets, follow status, leave CSAT feedback from one place.

inbox · email_pipeline ●3 steps

Step 01 · inbound

customer@acme.io

invoice question

2m ago

Step 02 · parse

customersubjectattachments · 1thread-id

Step 03 · ticket

HD-2114 open medium created from email

03 Conversations

Teams that consolidated their support stack on Helpdash

4 replies · thread · #cust-stories

●featured story

“We host the helpdesk under support.northwind.co.uk via the custom-domain feature — customers never see a third-party brand. The SLA pause logic alone saved my team hours of explaining clock issues to managers.”

Sarah Mitchell

Head of Customer Operations @ Northwind Logistics · GB

PH

Dr. James Chen · Director of Patient Services @ Pinnacle Health · US

Each clinic runs as its own tenant with its own roles, its own widget, its own custom domain — but I see everything from the Platform Admin panel. The audit log is exactly what our compliance team asked for.

12 healthcare
AB

Erik Lindqvist · VP of Customer Success @ Aurora Bank · NO

LDAP authentication, per-tenant role isolation via Spatie permissions, and the Jira Data Center sync strategy meant our security review took an afternoon, not a quarter.

15 fintech
GR

Maria Rodriguez · Support Team Lead @ Globex Retail · US

We replaced an email queue, a chat tool, and a separate CSAT survey vendor with helpdash. The embeddable widget surfaces tickets, chat, and KB from one script tag.

18 retail

start a workspace · 2 minutes

Spin up a workspace and a custom-domain widget in one afternoon.

14 days free. No credit card. Cancel from the dashboard with one click.

Start free trial

14-day trial
No card required
Cancel anytime
4 languages

One platform. Many client brands. Zero data leaks.

From idea to live in three steps.

Pick a slug

Make it yours

Pick your surface

Three teams. One platform. No compromise.

SaaS support teams

Agency client desks

MSP ticket queues

Everything support teams need to run multi-brand operations

Multi-tenant by design

White-label custom domains

Embeddable widget

Industry-standard tickets

Real-time chat

CSAT + Knowledge Base

Jira sync (Cloud + DC)

Magic-link customer portal

Teams that consolidated their support stack on Helpdash

Spin up a workspace and a custom-domain widget in one afternoon.

Talk to sales

Thanks — we'll be in touch.