"What is happening with my ticket?" is a question a help centre cannot answer. A help centre covers what applies to everyone, but it knows nothing about one customer's ticket, order or invoice. A customer portal fills that gap.
Portal versus help centre
A customer portal is the logged-in part of self-service. Here the customer sees and does what concerns them: tickets, the conversation with you, orders, invoices or agreements. The help centre is the open part. The help centre answers "how do I make a return?" while the portal answers "where is my return?". They complement each other.
When it pays off
A portal pays off when customers come back and many questions concern their own details rather than how something works. Think subscriptions, B2B customers with recurring orders, ongoing services and shops with many repeat buyers. A shop that sells one item once to each customer gains little.
Three signs in your inbox say it is time:
- Many questions are status questions about a ticket, order or invoice.
- The same customer asks repeatedly because nothing shows progress.
- The team keeps resending invoices and confirmations the customer already received.
If that sounds familiar, the portal removes a whole ticket type.
What to put in it
Show what customers ask about, in the order they ask it. Start with tickets, since almost every company has them:
- Tickets with status: open and closed tickets, who has the ball, and the next step.
- The conversation: the whole history across channels.
- Orders and deliveries: status, tracking and receipt.
- Invoices and payments: downloads, payment status and due dates.
- Agreements and subscriptions: what is included and how to cancel.
- Own details: address, contact details and consents.
Tickets and conversation are the core. They must be the same tickets your team works on in its ticketing system, not a copy refreshed now and then. Orders and invoices need connections to your business system and payment provider.
Login
Login should be easy enough that customers bother, and secure enough to protect personal data. Avoiding passwords helps with both. Yet another password gets forgotten, reset and reused, and "I can't log in" becomes a new ticket type.
Two routes work well. A one-time link sent by email, which expires quickly, suits most companies: the customer has shown they own the address and there is no password to leak. A strong e-identification suits sensitive data or binding actions such as cancelling an agreement. Keep security in proportion to the data: short sessions, expiring links and a log of logins are the minimum.
What customers should not see
Hide everything internal: notes between colleagues, unsent AI drafts and raw integration data. The boundary should be technical, not a rule telling staff to be careful. Show only what the customer needs, such as the order number and status, not the full customer record. Before launch, log in as a test customer and try to find anything that should not be visible.
Measuring success
Track three things:
- Share of status questions in the inbox. It should fall over time.
- Logins per open ticket. If customers log in to follow along, they stop asking. If nobody logs in, the portal is hard to find or empty.
- Tickets created via the portal. They arrive with identity and history already attached, saving a round trip.
For the complete walkthrough, read the full customer portal guide.
