Support tools & workflow · SupportRoadmap Docs
Knowledge bases in software support
A knowledge base is structured documentation for repeating questions—internal runbooks for agents, public help articles for customers, or both. In software support it shortens investigations and reduces contradictory answers, but only if articles stay accurate as the product changes.
By Tom Ulman · Published · Last reviewed
Two audiences, one idea
Software support teams usually maintain (or rely on) two documentation layers: customer-facing help centre articles and internal runbooks. Both reduce repeat investigation. Neither replaces a roadmap for learning skills; they store answers for repeating product situations.
How agents use a KB day to day
- Search before reinventing a reply for a known configuration issue.
- Link a public article when the customer can self-serve safely.
- Update the internal note or article when the product behaviour changed.
- Escalate with a pointer to the runbook step that failed—not a blank “bug?”.
Support example
Three customers ask how to rotate an API key. Instead of three slightly different answers, you send the public article, then file an internal ticket to clarify a screenshot that is out of date. Ticket macros can point at the same article so the queue stays consistent (ticketing systems).
Quality over volume
A short accurate article beats a long outdated wiki. If you are unsure whether guidance is still true, verify in a test account before sending it to customers.
Common mistakes
- Writing articles that restate marketing copy instead of steps and caveats.
- Keeping “shadow docs” only in personal notes so the team cannot find them.
- Linking internal-only URLs to customers.
Related concepts
Primary sources
Prefer an ordered path? Open the related roadmap skill and work through it with the curated resources.
Learn this in order