Self-service
What is self-service and why doesn't a customer choose it?
Self-service is letting the customer arrange themselves what would otherwise be a conversation. It only works when it takes less effort than firing off an email.
In short
Self-service is the set of facilities letting a customer find an answer or carry out an action without an agent: a help centre, an order status page, a returns portal or an account where they change their details. It differs from automation in that the customer acts; with automation your system does the work.
Why customers skip your help centre
The choice a customer makes isn't between searching and emailing. It's between an unknown amount of searching with an uncertain outcome, and typing three lines after which someone else figures it out. In that comparison emailing often wins, even when the answer is on your site.
Self-service only wins when the path is shorter. In practice that means: the answer sits on the page the customer is already on, not behind a search box on another page. A shipping question belongs with the product and with the order, not in an article you have to find.
Which self-service actually gets used
There's a clear pattern in what customers will do themselves. Actions with an immediate result get used; reading texts to assemble an answer doesn't.
- Checking order status
- Works well, provided the page says more than the tracking link. A status translated into an expected day answers the question; a carrier code doesn't.
- Registering a return
- The strongest form of self-service there is. The customer wants to do this themselves, because it's faster than waiting for your answer.
- Changing details or address
- Gets used as long as it takes a few clicks. Put a confirmation email with a link in between and a share drops off and emails anyway.
- Reading articles
- Only for questions the customer judges complex themselves, like warranty or a technical setting. For short factual questions, contacting you wins.
Where self-service starts working against you
A help centre you must walk through before seeing a contact button raises effort instead of lowering it. Customers find your email address anyway, but with more irritation and an opening line to match.
The second way it fails is staleness. An article with a return period that no longer applies is more harmful than no article: the customer acts on it and comes back with a screenshot. So put a review date on every article containing an amount, a period or an opening time.
Self-service or automation?
| Self-service | Automation | |
|---|---|---|
| Who acts | The customer | Your system |
| The customer notices | That they did it themselves | Only the result |
| Works well for | Actions with an immediate result | Questions and repetitive work |
| Fails at | A path with more than a few steps | Exceptions and judgements |
Choose self-service where the customer wants to do something and automation where they want to know something. Registering a return should be something the customer can do; the question of where their parcel is shouldn't need asking at all.
Where it goes wrong
Hiding the contact button
Ticket count falls and effort rises, and you only see the second in your satisfaction score and in the tone of the conversations you do get.
Writing articles from your own structure
Nobody finds a category called Logistics. Customers search with the words they'd ask the question in, and those are in your own mailbox.
No review date on articles
Anything with a period, an amount or an opening time goes stale. Without a review moment you discover it through a customer who acted on it.
Using page views as a success metric
A heavily read article can also be an article that doesn't answer the question. Look at what happens after reading, not at how often it was opened.
What to do this week
Take your five most-asked questions and look them up on your own site the way a customer would, via Google and via your own search box. Count how many clicks it takes until the answer is there. Anything above two clicks loses to sending an email, and then the article isn't the problem but where it sits.
What this looks like in a system
In Cuego the help centre comes from the same knowledge base the AI agent reads, so a changed return period is updated in one place and carries everywhere. The agent can point to the right article inside the conversation instead of sending the customer to a search box, and actions like registering a return or changing an address run as a workflow with a fixed sequence. Per article you can see how often it was used and how often contact followed anyway.
HelpRelated terms
Deflection
Deflection is the share of questions that never reached an agent. It's the easiest number to overstate and the most useful to measure honestly.
Read onKnowledge base
A knowledge base is the recorded version of what your team knows. Without an owner and a rhythm it's partly wrong within six months.
Read onWISMO
WISMO is the question of where the order is. It's rarely a location question and nearly always a certainty question, and that difference determines what you can do about it.
Read on