What counts as customer self-service?
Self-service covers every route a customer can take without waiting for a reply. The common forms are a help centre or knowledge base, an FAQ page, guides and tooltips inside the product, a community forum where customers answer each other, account pages where people change their own settings, and automated agents such as chatbots and voice agents.
Take a customer who wants to invite a teammate. With self-service, they search your help centre, read the article and finish the task in a couple of minutes. With assisted support, they email your team, wait for a reply and then follow the steps someone sends them.
Self-service works alongside assisted support. The UK government’s Service Manual, for example, asks teams that run online services to offer assisted digital support, by phone, in person and sometimes by web chat, for people who can’t use the service on their own.
How do you measure self-service?
Start with whether people finish what they came to do. The GOV.UK Service Manual defines completion rate as the number of digital transactions users complete as a percentage of all the digital transactions they start, and the same idea works for a help article or an automated conversation.
Teams also track deflection: how many self-service visits end without a ticket or a call. A visit that ends quietly may be a solved problem or a customer who gave up, so check the figure against repeat contacts and customer feedback.
Why does self-service matter for a website voice agent?
A voice agent is a self-service channel that people talk to. It suits customers who would rather explain a problem than search for the right article, and it can take follow-up questions in the same conversation.
It shares self-service’s limits too. It can only answer what its knowledge covers, it can’t act on an account unless it’s connected to one, and someone who gets stuck needs a clear way to reach your team. Plan those routes before you switch it on.
How does Kawl Now fit into self-service?
Kawl Now adds voice self-service to a SaaS website. A visitor clicks the widget, types what they need, allows the microphone and talks to an AI agent that answers from knowledge your team has approved: FAQs and notes you write, plus selected GitHub docs for support.
It covers product questions. The agent can’t look up or change a customer’s account. When the approved knowledge doesn’t answer a question, the agent is told to say it doesn’t know and point the caller to your website’s usual contact options, or to offer a person if you’ve turned on handover.
Handover to a person is an early release. Your team verifies a UK or US phone number and turns handover on for the support or sales agent, and whoever answers hears a private briefing before the call connects. Customer routing is still being tested, so keep your usual contact options visible beside the widget.
Every conversation is saved as a text transcript, and the Insights tab in your dashboard groups the questions and issues that come up in recent calls, with quotes from the transcripts. Together they help you spot the answers your knowledge is missing.
Common questions
What are examples of customer self-service?
Common examples are a help centre or knowledge base, an FAQ page, in-product guides, a community forum, account settings customers can change themselves, and AI chatbots or voice agents. Kawl Now is a voice example: website visitors ask a product question aloud and hear an answer from knowledge the company has approved.
Does self-service replace a support team?
No. Self-service handles questions with a known answer, such as how to set something up. Account problems, bugs that need investigating and upset customers still need a person, so keep an easy route to your team beside every self-service option.