A customer support portal is built on one idea: that the customer should meet the answer before they meet the request form. The help centre answers the recurring question, the account view answers the status question, and the form at the end raises a ticket only when neither did. A customer service portal is the same thing named from the other side of the desk. The point of customer support portals for a company with a few hundred accounts is not the design but the arithmetic: the share of would-be tickets the portal answers, the cost of the tickets it removes and the cost of the portal itself. This page sets out what customer service portals hold that a shared inbox cannot, how support portals are measured, and how portal customer service is costed against an agent-handled ticket with the free business case worksheet on this site.
Answer first: the order of the portal
The customer arrives with a question. The first thing they meet is the search over the help centre, so a recurring question is answered by an article. If the question is about their own account, the signed-in view answers it: the engineer's arrival window, the invoice line, the document. Only when neither has answered does the request form appear, and it appears with the account and the article they read already attached, so the agent who picks the ticket up starts from context rather than from a blank email. A portal that puts the form first has built an inbox with a login.
What the portal holds that an inbox cannot
A record per customer: account, status, invoices, documents, cases and, for each case, its history. A record per article: how often it was read and whether a ticket followed the reading, which is how a weak article is found. A record per month: tickets raised, articles read, would-be tickets answered, and the deflection share that follows. An inbox holds messages; it cannot say which question was asked a hundred times this month, and so it cannot say which article to write next. Deflectvo Pro keeps those records per customer and per month and exports them.
Measuring support portals, and the cost against an agent
Take the tickets a month the company handles now, the share a portal will answer once its articles are written, the cost of an agent-handled ticket in loaded minutes, and the portal's monthly cost. The tickets removed times the cost per ticket is the monthly saving; the saving against the portal's cost is the payback in months. The free self-service business case worksheet on this site does that arithmetic from the figures you enter, with no vendor named and no industry deflection rate assumed; if the share answered is a guess, the worksheet shows what the payback looks like when the guess is a tenth too high. Portal customer service earns its place when that number holds up, and not before.
Questions people ask about customer support portal
What is a customer support portal?
A signed-in area where a customer meets the help centre and their own account before the request form, so a ticket is raised only when the answer was not already there. A customer service portal is the same thing named from the support desk's side.
How is a support portal measured?
By deflection: the share of would-be tickets the portal answered in a month, read from articles read against tickets raised, and by the cost of the tickets removed against the portal's own cost.
What does a customer service portal cost compared with agents?
The comparison is the tickets removed times the loaded cost of an agent-handled ticket, against the portal's monthly cost. The business case worksheet on this site works it from your own figures; this page publishes no rate.