A self-service front door for every workspace
One public URL per tenant — submit a ticket, track it by link, and browse the knowledge base, no login required.
Client portal is the public, unauthenticated surface of Service desk and Knowledge base: a support-request form, a knowledge base browser, and a token-based ticket tracker, all scoped to a single tenant's data via the workspace's slug in the URL (/portal/{tenant}). Every route behind it — submit, track, reply, list articles, read an article — only ever touches that one tenant's records.
Scoped to one workspace
The portal's tenant slug is resolved to a tenant on every request, and all reads and writes are then scoped to that tenant's data — there's no cross-tenant lookup path, even though none of these routes require a login.
Submit and track without an account
The submit form collects name, email, subject, and description. The customer is matched to an existing contact by email or a new one is created, and the response carries a one-time tracking token plus a ticket number — that token, not a password, is what lets the customer come back later at /portal/ticket/{token} to see status and the full customer-visible comment thread, and to post a reply.
Built-in abuse protection
A hidden honeypot field silently drops bot submissions, and both the submit and reply endpoints are rate-limited per tenant and per ticket respectively.
- Ticket submissions: 10 per hour, per tenant
- Ticket replies: 30 per hour, per ticket token
Knowledge base browser built in
The portal home lists every published knowledge-base article for that tenant, with its category shown inline; clicking one opens the full article at /portal/{tenant}/kb/{slug}.
- Give customers one link to submit requests instead of a shared inbox
- Deflect repeat questions with searchable, published help articles
- Let customers check on a request themselves instead of emailing to ask for status
Client portal — common questions
No. Ticket tracking works off a one-time opaque token issued at submission — there's no customer login or password.
A honeypot field on the form plus hourly rate limits on both new submissions (per tenant) and replies (per ticket token).
No — the portal thread only ever shows non-internal comments.
No. Every portal route resolves and filters by the tenant slug in the URL, so a workspace's tickets and articles are only reachable through its own portal link.