Practice knowledge base support vocabulary: ticket deflection rates, article maintenance, solution vs. workaround articles, KB analytics, and support self-service strategy.
0 / 5 completed
1 / 5
'We deflect 40% of tickets with KB articles.' What does ticket deflection mean?
Ticket deflection is when a customer finds the answer to their question in the knowledge base before — or instead of — submitting a support ticket. A 40% deflection rate means 40% of potential tickets are avoided because customers self-served. High deflection rates reduce support costs, improve customer satisfaction (faster resolution), and free support engineers for complex issues.
2 / 5
'The KB article needs updating — the UI changed.' Why is knowledge base maintenance important?
Knowledge base articles must stay current with the product. After a UI redesign, process change, or feature update, outdated articles send customers down the wrong path — they can't find the button described, get frustrated, and open a ticket. Maintaining KB content is an ongoing responsibility, and many teams tie article review to product release processes.
3 / 5
'The article didn't help — we'll create a new one.' What process should follow a ticket that wasn't solved by an existing KB article?
When a ticket reveals a gap in the knowledge base — a common question not yet documented — the resolution should be captured as a new KB article. This is the 'shift left' principle in support: move knowledge from support engineers' heads to a self-service resource. Over time this systematically grows the KB and increases deflection rates.
4 / 5
What is the difference between a 'solution article' and a 'workaround article' in a knowledge base?
Solution articles document the correct, permanent way to resolve a problem. Workaround articles document a temporary alternative when the root cause hasn't been fixed yet — for example, 'click X instead of Y while we fix the bug in the menu'. Clearly labelling workarounds manages customer expectations and signals that a better solution is planned.
5 / 5
'The most accessed KB article this month is about password reset.' What does KB article access data tell you?
KB article access data reveals your customers' most common questions and friction points. High access on a password reset article signals the feature either isn't self-evident or generates recurring confusion. This data should feed back into product decisions — if thousands of customers need an article to reset their password, the in-app experience should be improved to make an article unnecessary.