Helpdash is the multi-tenant, white-label helpdesk for fast-moving support teams β tickets, live chat, knowledge base, automation, and per-tenant custom domains in one workspace.
No reviews yetBe the first to leave a review for Helpdash
Maker
π
Hey Product Hunt! π
We built Helpdash because running support for multiple clients meant juggling multiple helpdesk subscriptions β or settling for one shared, unbranded inbox.
Helpdash is multi-tenant from the ground up:
β’ Each client gets their own branded portal β logo, colors, custom domain with automatic TLS
β’ Tickets, live chat with auto-assign queues, knowledge base, CSAT β one workspace
β’ Automation rules, SLA tracking, email-to-ticket
β’ 12 languages, API access
β’ Free plan to start; paid plans from $29/mo
We use it ourselves to support our own products (dogfooding!). Would love your feedback β especially from agencies and MSPs juggling multiple client support inboxes today. AMA!
Report
Custom domain support per tenant is great, but it would help to have white-label email sending too so reply notifications actually come from our clients' domains instead of a shared one.
Report
Maker
Great point, @necdetozya55828Β β and an honest one to answer: right now outbound notifications send from a shared, authenticated Helpdash domain, so that's a genuine gap in the white-label story today. (Inbound already runs on your own domain β email-to-ticket routes to each tenant's custom address β it's the outbound "From" that isn't tenant-branded yet.)
Per-tenant custom sending domains, with DKIM/SPF verification so replies truly come from support@yourclient.com, is exactly where we want to take this next. Since you clearly care about it β would you rather bring a verified domain of your own, or plug in per-workspace SMTP credentials? Feedback like this is what pushes it up the list.
Report
Adding a built-in customer satisfaction survey widget that automatically sends a short rating prompt after a ticket is marked resolved would be really useful. It would help teams track CSAT scores per tenant without needing a separate tool, and the data could live right alongside the ticket reports in the dashboard.
Report
Maker
@adilewibΒ β good news, you're describing something that's already in the box π
CSAT is built in: mark a ticket resolved and Helpdash automatically sends the customer a short 1β5 rating prompt (a signed, one-time link β no account needed on their end). Scores are tracked per tenant with agent-level and workspace-level panels, sitting right next to your ticket reports in the dashboard β exactly where you'd expect them. You can tune the send delay and cooldown per workspace, and low scores can auto-reopen the ticket with their own SLA.
We actually just added a step on top: a happy 4β5β rating can optionally invite that customer to leave a public review. Would genuinely love your take if you give it a spin on the trial.
Report
The per-tenant custom domains thing is honestly pretty slick for a white-label setup, didn't expect that built in. Wish the knowledge base editor felt a bit more modern though.
Report
Maker
Thanks @aban145998Β β appreciate that. The per-tenant domains were one of those "has to be built in, not bolted on" calls for us, so it's nice to hear it landed.
And that's a fair hit on the knowledge base editor β honestly the part of the product we're least finished with. Genuinely curious what would make it feel modern to you: slash-command blocks, live preview, cleaner media handling, markdown shortcuts? We're actively iterating on it, and specifics like this are exactly what shapes what we ship next.
Custom domain support per tenant is great, but it would help to have white-label email sending too so reply notifications actually come from our clients' domains instead of a shared one.
Great point, @necdetozya55828Β β and an honest one to answer: right now outbound notifications send from a shared, authenticated Helpdash domain, so that's a genuine gap in the white-label story today. (Inbound already runs on your own domain β email-to-ticket routes to each tenant's custom address β it's the outbound "From" that isn't tenant-branded yet.)
Per-tenant custom sending domains, with DKIM/SPF verification so replies truly come from support@yourclient.com, is exactly where we want to take this next. Since you clearly care about it β would you rather bring a verified domain of your own, or plug in per-workspace SMTP credentials? Feedback like this is what pushes it up the list.
Adding a built-in customer satisfaction survey widget that automatically sends a short rating prompt after a ticket is marked resolved would be really useful. It would help teams track CSAT scores per tenant without needing a separate tool, and the data could live right alongside the ticket reports in the dashboard.
@adilewibΒ β good news, you're describing something that's already in the box π
CSAT is built in: mark a ticket resolved and Helpdash automatically sends the customer a short 1β5 rating prompt (a signed, one-time link β no account needed on their end). Scores are tracked per tenant with agent-level and workspace-level panels, sitting right next to your ticket reports in the dashboard β exactly where you'd expect them. You can tune the send delay and cooldown per workspace, and low scores can auto-reopen the ticket with their own SLA.
We actually just added a step on top: a happy 4β5β rating can optionally invite that customer to leave a public review. Would genuinely love your take if you give it a spin on the trial.
The per-tenant custom domains thing is honestly pretty slick for a white-label setup, didn't expect that built in. Wish the knowledge base editor felt a bit more modern though.
Thanks @aban145998Β β appreciate that. The per-tenant domains were one of those "has to be built in, not bolted on" calls for us, so it's nice to hear it landed.
And that's a fair hit on the knowledge base editor β honestly the part of the product we're least finished with. Genuinely curious what would make it feel modern to you: slash-command blocks, live preview, cleaner media handling, markdown shortcuts? We're actively iterating on it, and specifics like this are exactly what shapes what we ship next.