A branded support portal on your own domain. Customers sign in with a magic link, file requests with attachments and threads, and read a public knowledge base — and every request lands in your team’s Inbox with the account already attached.
Your end customers live in email threads and shared inboxes. They can’t see where a request stands, so they ask — and every ‘any update?’ arrives as one more ticket for a team already at capacity.
Worse, the answer often already exists — written down somewhere your customers were never given a way to reach.
Per-tenant branding — logo, theme, and copy — served on a custom domain like support.hooli.com, a Quantesic /t/{slug} address, or embedded straight into your product. Customers never feel handed off to someone else’s tool.
Customers sign in with a one-time magic link, verified against the email domains you allow for each account. No shared passwords, no seat sprawl, and no one reaching an account they shouldn’t.
Customers file and track requests with full threads and file attachments, and can always see where each one stands. The ‘any update?’ question answers itself.
Publish articles anyone can read without an account. When the answer already exists, customers find it before they ever open a request.
Show the response targets you commit to, by priority. Expectations are set in the open — and you configure them, per account and plan, not us.
A portal ticket is never a silo. It arrives in your team’s Omnichannel Inbox with the account, history, and priority already attached — ready to triage.
The portal is the customer-facing edge of the same account spine your team already works.
Customers can see where every request stands and read the answers that already exist. The status-check load your team quietly carries goes away.
From the first help article to the final reply, customers stay in your world — never bounced into a tool that looks like it belongs to someone else.
Because it lands in the Inbox with the account attached, the first ten minutes of triage are done before your team reads line one.
A 30-minute walkthrough of the platform, with the person who built it.