Customer Experience
Write a customer support knowledge base people can actually use
Turn scattered answers into a searchable, owned and maintainable source of guidance for customer conversations.
IGS Editorial · 4 min read · Updated 17 November 2026

A knowledge base is useful when it helps someone make the correct next decision. A large library of documents can still leave an agent guessing if titles are vague, policies conflict or exceptions are buried. Start with the moments where people hesitate during real conversations, then write guidance for those moments.
Treat the library as part of an operating process. Someone needs to propose updates, someone needs authority to approve them, and readers need a way to flag uncertainty. Without these roles, an initially accurate collection slowly becomes a source of contradictory answers.
Begin with the question, not the department
Customers rarely describe a problem using your internal team names. Organise articles around recognisable questions such as “Where is my order?” or “How can I change my appointment?” Add the terms customers and agents actually use to titles and search keywords. Keep administrative ownership in metadata rather than using it as the main navigation structure.
Review recent enquiries and group them by the decision required. Two questions that sound similar may need separate guidance if the answer changes by product, geography or purchase date. Conversely, several phrases may point to the same underlying rule and should lead to one authoritative article.
Give each article a decision path
Open with the situation the guidance covers. State what the agent must verify, what information can be shared, and what actions are permitted. Put important exceptions next to the relevant step. An instruction to “follow policy” is not useful unless it links to a specific, current policy and explains how it applies.
For example, an address-change article might distinguish an unprocessed order from one already dispatched. The first route may allow an update; the second may require a logistics enquiry. The article should also identify who handles a case that falls outside both routes.
Make ownership visible
Every article needs an owner, approval date and review trigger. A calendar review is helpful, but changes to pricing, products or systems should also trigger a content check. Archive superseded versions in a way that preserves history without leaving them prominent in search results.
Do not measure freshness only by whether a review date changed. Ask the reviewer to test the instructions against a representative case. A link may still work while the underlying screen, permission or customer message has changed.
Use feedback as a maintenance queue
Let readers report missing steps, unclear wording and cases that do not fit. Capture the article, the point of confusion and the consequence. Avoid collecting unnecessary customer details in feedback comments. Assign a content owner to resolve each report and tell the reporter when the guidance changes.
Repeated questions can indicate a navigation problem rather than missing content. Before writing another article, check whether the existing answer can be found using the terms people use. Duplicate answers create future maintenance work and can drift apart.
Test usefulness in context
Ask a colleague unfamiliar with the article to handle a sample case using only the documented guidance. Notice where they stop, infer a rule or ask for permission. Those moments reveal missing context more reliably than proofreading alone.
Track whether the library reduces avoidable uncertainty: fewer conflicting answers, clearer escalations and less rework are meaningful signals. Search activity alone cannot tell you whether an answer was correct. Review a small sample of resulting decisions and use that evidence to improve the next set of articles.
A practical editorial review
Imagine that an agent searches for an address change and finds three articles: one from fulfilment, one from sales and one from an old training pack. Each contains a different cutoff point. Creating a fourth answer would make the problem worse. The content owner should first establish the approved rule, then consolidate or redirect the competing material.
Test the revised article with a case before dispatch and a case after dispatch. Ask the reader to identify the correct route and explain the customer message. If the two routes remain difficult to distinguish, improve the decision wording rather than adding more introductory text.
Useful review questions include: can a reader recognise the situation from the title; is the source of authority clear; are exceptions located beside the relevant instruction; and is there a named route for a case the article does not cover? Record the answers as editorial actions. Review search terms again after publication to see whether the same uncertainty persists. A content change is complete when the approved answer is both accurate and findable, not merely when the document has been saved.
