Customer Service ยท Module 21
Knowledge Base
Answer It Once, Reuse It Forever
Turn your team's best answers into short, searchable articles. Agents stop retyping the same reply, and customers can find answers on their own.
About & Business Case #
Why the same question keeps costing you time #
"I've typed the answer to 'how do I reset my password' probably two hundred times this year. New hires don't know it, so they guess, or they interrupt me to ask. We need one place with the answer written down properly, that anyone can search."
When an answer only lives in one agent's head, every repeat question costs time twice. Once to answer it, and again to explain it to whoever asks next. A written, searchable answer only has to be right once.
What you get out of it
Common questions get answered faster and more consistently. New agents learn the ropes by searching articles instead of interrupting teammates.
Implementation #
Write it, publish it, then search for it #
Every article has a Title, a short Summary (shown in search results and lists), a Category (How To, FAQ, Troubleshooting, Release Notes, Best Practices, or Other), and the full Content โ the actual answer. Content supports basic formatting and shows a live preview as you write, so you can see how it will look.
Status controls who can see it
Every article moves through a status, in this order: Draft โ In Review โ Published โ Archived. Keep an article as Draft while you're still writing it. Only mark it Published once it's ready for agents โ and customers too, if your Knowledge Base is customer-facing โ to rely on.
Search and feedback
The Knowledge Base list has a search box and a status filter, so agents can find the right article in seconds. Each article also tracks a view count and Helpful Yes/No votes. That lets you see which articles are actually getting used, and which ones need a rewrite.
1 Publish a "How do I reset my password" article #
How to Use #
Day-to-day: support agents #
Day-to-day: knowledge curators #
What to try next
Look at the Case Management, SLA & Routing trail โ a good Knowledge Base cuts down how many Cases even need to be created.