Practice knowledge base support vocabulary: ticket deflection rates, article maintenance, solution vs. workaround articles, KB analytics, and support self-service strategy.
0 / 10 completed
1 / 10
'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 / 10
'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 / 10
'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 / 10
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 / 10
'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.
6 / 10
Alice: 'Hey, the support team is drowning in requests for users to reset their API keys. We should create a detailed KB article on this.' What does 'API key' typically refer to in a knowledge base context?
API keys are identifiers that authenticate applications; they're not passwords. A 'key' in this context allows an application to access a service securely. The incorrect options relate to user login or transient passwords, which are distinct security concepts. Focusing on API keys is crucial for understanding the scope of support requests.
7 / 10
Mark (in a Slack channel) writes: 'This bug is driving me insane! The database connection keeps timing out. I've tried everything!' What does Mark likely need from the knowledge base to help resolve his issue, specifically regarding troubleshooting?
Mark's message indicates a technical problem with a database connection, strongly suggesting he needs troubleshooting information. Option C is the most relevant; knowledge bases often contain solutions to common technical problems, including steps for diagnosing and resolving network issues or configuration errors. The other options address different aspects of development and don't directly relate to the immediate issue.
8 / 10
You're drafting a PR description for a fix that resolves an intermittent error when users upload large files. The description reads: 'Fixed a bug where uploads would fail intermittently. Investigating further.' What information *should* be included in the KB article related to this fix, beyond just stating the problem was resolved?
A good PR description highlights the *impact* of the change. A knowledge base article needs to provide users with practical guidance. Including steps to reproduce (if possible) and potential workarounds—even temporary ones—is essential for a helpful KB entry; this addresses the 'investigating further' aspect. The other options are irrelevant to user support.
9 / 10
Sarah: 'The new feature documentation is confusing! Users are asking for a step-by-step guide on how to integrate the SDK.' Which type of KB article would be *most* appropriate for Sarah's request?
Sarah needs a step-by-step guide to help users integrate the SDK. Option B represents a 'solution article' that directly addresses the user's request for a tutorial. The other options are less targeted and don't provide the specific guidance needed in this scenario. A solution article focuses on providing a direct path to resolution.
10 / 10
During a daily standup, David says: 'We're seeing an increase in support tickets related to users not being able to connect to the staging environment. It seems many are struggling with the configuration steps.' What is David primarily highlighting when discussing this issue within the context of knowledge base development?
David is focused on a specific problem: users struggling with configuration. This points to a need for a KB article that provides clear instructions and addresses potential pitfalls related to accessing the staging environment. The other options are tangential; documentation should focus on the user's perspective and common issues, not technical details like API keys or server performance.
This exercise, "Knowledge Base Support Vocabulary", tests your understanding of technical support vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Support exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical support topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Support exercises?
Browse the full Technical Support exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.