One place to continue
Customers pick up any conversation — chat, email, or Discord — from a single portal, with the full thread history intact.
Customer surface
A home for your developers
A branded home where your developers pick up conversations, track issues, and get grounded answers — without leaving your product.
Cross-channel historyIssue statusWorkspace-scoped
your support · acme developersonline
The problem
Your customers have no home for support
A developer files a question over email, then has nowhere to check whether it moved. Context lives in your operators' inbox, invisible to the person who actually needs it. Without a place to see history and status, customers re-ask, re-explain, and lose confidence that anyone is on it.
Why it works
Support shouldn't dead-end in an email thread.
Status they can see
Issues and conversations show their current state, so customers know something is happening without emailing to ask.
Scoped to them
Portal access is workspace-scoped and tenant-isolated. Customers see their conversations and context — nothing from anyone else.
The portal they see
A support home your developers will use
This is the surface your customers actually live in — bright, branded, and theirs. They pick up conversations across channels, get the same grounded answers, and watch their issues move to done.
your support · acme developersonline
Webhook signature helpIn progress
Sandbox key rotationResolved
Pagination on /ordersOpen
Grounded answer, with citations
Continuity
Every conversation, in one place
The portal is the customer's side of the unified inbox. Threads that spanned chat, email, and Discord show up as continuous conversations with full history, so developers never have to reconstruct what they already told you.
- Cross-channel threads with complete history
- Grounded, cited answers, same as every channel
- Pick up where the conversation left off
one conversation · every channel
Transparency
Status, without an email to ask for it
Customers can see where their issues stand instead of pinging support for an update. Clear state on conversations and issues cuts the 'any news?' round-trips and builds trust that the work is moving.
- Visible status on conversations and issues
- Fewer status-check round-trips for your team
- Confidence that something is happening
issue status · visible to you
Boundaries
A portal that respects tenant lines
Portal access is scoped to the workspace and the customer. Tenant isolation carries through to the customer surface, so developers get their history and context — and only theirs — with the same guarantees that protect the rest of the platform.
- Workspace-scoped, tenant-isolated access
- Customer sees only their own conversations
- Same isolation guarantees as the operator side
scoped to you
How it works
Three steps, no heavy lift.
01step
Customer signs in
Developers reach a branded portal scoped to your workspace and their identity.
workspace-scoped access
02step
Pick up any thread
They continue conversations across channels with full history and grounded answers.
chat · email · discord history
03step
Track it to done
Status on conversations and issues keeps customers informed without asking.
issue · in progress → resolved
1
home for support
cross
channel history
scoped
to each customer
FAQ
Client portal questions
What can a customer do in the portal?
Continue their conversations across live chat, email, and Discord with full history, get the same grounded and cited answers, and see the status of their issues — all in one branded place.
Is the portal isolated per customer?
Yes. Access is workspace-scoped and tenant-isolated, so a customer only ever sees their own conversations, issues, and context.
Does the portal use the same AI agent?
It's the same grounded agent as every other channel — answers come from your workspace-scoped API context with citations, and low-confidence cases hand off to a human.
How is this different from the operator inbox?
The inbox is the operator's cross-channel queue; the portal is the customer's view of their own conversations and issue status. They're two sides of one conversation model.
Give developers a support home
Let customers continue conversations, track issues, and get grounded answers — all in one branded place.