Knowledge Base Article From Ticket
Published KB article with metadata, screenshots, and category. Article linked from prior tickets. View and deflection metrics tracked at 60 days.
Before you start
- KB platform with editorial workflow
- Voice and style guide for KB
- Ticket-pattern detection — the issue has occurred 3+ times
- Cluster of similar resolved tickets
- The actual fix or workaround that resolved them
- KB taxonomy for placement
The steps
- Identify a recurring issue from ticket data — Pull tickets matching the same issue pattern in the last 90 days. Threshold: 3+ tickets with similar root cause. If only 1-2 tickets, not yet KB-worthy — too narrow.
- Extract the actual resolution — From the resolved tickets, document the steps that actually fixed the issue. Include any pre-conditions or environment factors. Avoid 'we restarted it' — capture the why.
- Draft article using standard structure — Structure: Title (search-friendly question form, e.g., 'Why is my export failing?'), short summary (1-2 sentences), step-by-step solution, when to contact support, related articles. Match the voice guide — no marketing-speak in support content.
- Add screenshots and code blocks — For UI-related issues, include screenshots with annotations. For technical issues, format code/commands as code blocks. Visuals reduce ticket volume more than walls of text.
- Add metadata for searchability — Tag with: category, related product area, error codes mentioned, alternate phrasings of the question. KB articles are only useful if they're findable.
- Send for editorial review — Route to the KB editor or senior support agent for review. Editor checks: accuracy, clarity, voice, screenshot quality. Don't publish without review — bad articles erode trust in the KB.
- Publish and link from prior tickets — Publish the article. Link the new article in the resolved tickets that triggered its creation — closes the loop and proves the KB is actively maintained. Track article views and ticket-deflection rate over the next 60 days.
If it goes wrong
Article gets few views despite being relevant
Search audit — is the article discoverable for the natural questions customers ask? Rephrase title and add alternate phrasing tags.
Article becomes outdated quickly when the product changes
Link KB articles to product feature flags. When a feature changes, all linked articles flag for review automatically.
Articles drift from voice guide over time
Quarterly voice audit. Reform articles that drift. Don't accept 'we'll fix it later' — voice consistency compounds.
All OpenLabor playbooks