Feature 01 / 04
Solution
A portal customers actually want to open
A self-service portal on your own domain. Customers browse knowledge base articles, file new tickets, and read their own history — all in EN, AZ, RU, or TR, all under your brand, all without ever seeing Helpdash.
Outcomes
What a branded portal changes
Customers who open a Helpdash portal in their own language file 40% more self-resolving tickets — and the ones that do reach an agent come with more context.
Feature 02 / 04
Customer ticket history with status, replies, and CSAT recall
Feature 03 / 04
Knowledge base browsable without an account, search-engine indexed
Feature 04 / 04
Branded login
SSO, magic link, or password — your choice per workspace
Inside the portal
A portal you can ship without a frontend engineer
Feature 01 / 03
Custom domain
Point a CNAME, we issue the certificate. Branded outbound email follows automatically — same domain, same brand.
Feature 02 / 03
Multi-language
Detect from browser, force per-session, or let customers pick. Articles fall back gracefully to your default.
Feature 03 / 03
History & status
Customers see their tickets, replies, attachments, and SLA state. Logged-in views; no public-link guesswork.
FAQ
Frequently asked questions
Can I customise the portal layout?
Yes — themes apply per workspace (colour, logo, font). For deeper customisation, the portal exposes a templating layer with section-level overrides.
Does the portal support SSO?
Yes. SAML, OIDC, Google, and magic-link sign-in. Workspaces can require SSO for portal access while keeping the API open for service accounts.
Is the portal indexable by search engines?
Public knowledge base articles are SEO-friendly by default with structured-data markup. Private tickets and customer pages are never indexed.
Ship your portal under your domain this week
Pro plan includes the custom-domain portal and four-locale authoring. Free plan ships the portal on the helpdash.io subdomain.