A portal that remembers
Customers see their own ledger — every request, every reply, every SLA target — without a second account.
The customer portal is the other side of the same desk. When someone files a ticket through the widget, they automatically have a place to come back to — a portal that lists their past requests, the replies they got, and where each ticket stands.
What customers see
- Their own ledger. Every ticket they have opened, every reply, every status change.
- SLA targets. “Reply by 14:00 today” beats “we will get to you when we can”.
- Attachments and history. Files they sent, files we sent back, all preserved.
What they do not see
- Internal notes. Notes left between teammates stay hidden — never accidentally exposed.
- Other customers’ tickets. The portal is workspace-isolated by construction; cross-customer leakage is impossible.
- A second login flow. Customers authenticate via the same identity they used at the widget — no new account required.
Why no second account
Because asking your customer to remember a second password to read a status update is hostile. The portal accepts the same OTP / magic-link / SSO they used at the widget; the experience is “click a link in the email and you are in.”