Customer Portal
An authenticated area where customers handle their own account — the cheapest support channel a business has, when it covers the right things.
A customer portal lets people do for themselves what they would otherwise contact support about: view invoices, update payment details, manage users, download documents, track a request. Its value is measured in deflected tickets, which makes the design question empirical — what do people actually contact you about — rather than a matter of taste.
Most portals are built from what was easy to expose rather than from the support queue. That produces a portal full of read-only information and a support queue unchanged, because the top contact reasons were all actions: cancel, change the billing contact, add a seat, get a copy of last year's invoice. A portal that shows data but cannot change anything has not removed a single reason to call.
Cancellation belongs in it
Leaving cancellation out is the most common deliberate omission and the most expensive one. It converts a would-be cancellation into a support call, a bad review, or a chargeback — and in several jurisdictions it is now a regulatory problem.
In practice
A B2B vendor built a portal showing invoices and usage. Ticket volume did not move. The top three contact reasons were adding a user, changing the billing email and getting a VAT invoice — all read-only in the portal. Making those three actions self-serve cut tickets by 38% in two months.
Where teams get it wrong
- Building from what was easy to expose instead of from the support queue.
- Read-only data where the contact reasons were all actions.
- No cancellation, which pushes people to support, reviews or their bank.
- One permission level, so an admin cannot let finance see invoices without full access.
- No audit trail, so nobody can answer who changed the billing contact.
( Learn more )
Related terms
All terms- Audit LogAn immutable record of who did what and when — required by enterprise buyers and compliance frameworks, and usually built as an afterthought.
- Multi-TenancyOne application instance serving many customers with their data isolated from each other — the architecture nearly every SaaS product runs on.
- ChargebackA forced reversal of a card payment initiated by the cardholder's bank — the customer's escape hatch when the merchant's own one is worse.
- ChurnThe rate at which customers stop paying or stop using a product over a given period — the mirror image of retention.