For IT Support Technician / Help Desk Analysts ·
What you'll accomplish
By the end of this guide, you'll have a repeatable system for turning your resolved tickets into KB articles, keeping documentation current, and building the kind of searchable knowledge base that actually reduces ticket volume — instead of the dusty wiki that nobody reads. You'll do your first KB article in 15 minutes.
What you'll need
Go to claude.ai. Click "Start for free." Sign up with your personal email. You'll get the conversation interface immediately — no configuration needed.
What you should see: A chat window ready for your first message.
The most effective time to write a KB article is immediately after closing a non-trivial ticket — the solution is fresh in your memory. Build this habit:
Over time, this becomes automatic.
In Claude, paste this:
Convert these ticket resolution notes into a professional IT knowledge base article.
Issue: [brief description]
Resolution notes: [paste your notes — rough is fine]
Format the article with these sections:
- Problem Description (what symptoms the user sees)
- Affected Environments (OS versions, applications, conditions)
- Step-by-Step Resolution (numbered, specific commands/paths included)
- Verification Steps (how to confirm the fix worked)
- Common Variations (related issues with same resolution)
- Related Issues / See Also
Keep steps specific and complete enough for a new analyst to follow independently.
What you should see: A complete, structured article with all sections filled in. Review for accuracy and add any details only you know (specific registry paths, version numbers, configuration details).
Read the article before publishing. Check:
Add screenshots or screen recording references where needed (describe them as "[screenshot: showing the error dialog at step 3]" if you can't include them).
For KB articles that users have been following incorrectly (you can tell because they open tickets after reading them), use Claude to update them:
Identify your top 5 most common ticket types. Write KB articles for all 5 in one focused session:
Each takes 10-15 min. In 90 minutes you've built a KB that prevents hundreds of future tickets.
Standard KB article from ticket notes:
Convert these ticket resolution notes into an IT KB article. Issue: [description]. Notes: [paste notes]. Include: Problem Description, Affected Environments, Step-by-Step Resolution, Verification, Common Variations.
Update an outdated KB article:
Update this KB article to reflect current procedures. What's changed: [what changed]. Keep the format and structure, update the steps. Current article: [paste old article].
Create a troubleshooting decision tree:
Create a troubleshooting decision tree for [common issue type] at the IT help desk. Format as numbered Yes/No decision points. Start from user-reported symptoms and branch to specific diagnoses and fixes.
Write a user-facing how-to guide:
Write a step-by-step user guide for [task] in [software]. Audience: non-technical office users. Use simple language, numbered steps, and describe what the user should see at each step. No jargon.