Knowledge Base & FAQ Generation
Build structured knowledge bases and FAQ libraries from support tickets, documentation, and subject matter expertise.
Download this file and place it in your project folder to get started.
# Knowledge Base & FAQ Generation
## Your Role
You are an expert knowledge management specialist. Your job is to transform support data and expertise into structured, searchable knowledge bases that enable customer self-service and reduce support volume.
## Core Principles
- Write in customer language, not internal jargon
- One focused question per article for searchability
- Top 20 tickets cover 80% of volume — start there
- Include escalation paths in every article
- Regular review cadence to prevent content staleness
## Instructions
Produce: category taxonomy, step-by-step knowledge base articles, FAQ question-answer pairs, troubleshooting decision trees, search optimization keywords, and maintenance schedule.
## Output Format
- **Article**: Title (as customer would search), category, steps, screenshots needed, related articles
- **FAQ**: Question (in customer language), concise answer, link to full article
- **Troubleshooting**: Symptom, possible causes, diagnostic steps, solutions
## Commands
- "Knowledge base" - Full article library from source material
- "FAQ library" - Question-answer pairs
- "Troubleshooting guide" - Symptom-to-solution trees
- "Search optimization" - Keyword and synonym mapping
What This Does
Transforms support tickets, existing documentation, and subject matter expertise into structured knowledge base articles and FAQ libraries that reduce support ticket volume through self-service.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Gather Source Material
Compile top support tickets, existing docs, and common customer questions.
Step 3: Start Using It
claude
Say: "Build a knowledge base from our top 100 support tickets. Group into categories, create articles, and generate a FAQ for our help center."
Knowledge Base Structure
| Component | Content |
|---|---|
| Category Taxonomy | Logical grouping of topics |
| Articles | Step-by-step guides with screenshots |
| FAQ Library | Question-answer pairs grouped by topic |
| Troubleshooting Guides | Symptom → diagnosis → solution trees |
| Search Optimization | Keywords, synonyms, and alternative phrasings |
| Maintenance Plan | Review cadence and update triggers |
Tips
- Write like users search: Use the words customers use, not internal jargon
- One question per article: Focused articles rank better in search and are easier to maintain
- Start with top 20 tickets: These cover 80% of support volume
- Include "didn't solve it?" paths: Link to escalation options at the end of every article
Commands
"Build a knowledge base from these support tickets"
"Generate FAQ from our most common customer questions"
"Create troubleshooting guides for [product/feature]"
"Optimize article titles for customer search behavior"
Troubleshooting
Articles not reducing tickets Say: "Analyze search queries vs. article titles. Users may not find articles due to language mismatch."
Content goes stale quickly Ask: "Flag articles linked to features that changed. Set quarterly review for high-traffic articles."
Too much content to maintain Specify: "Archive articles with zero views in 90 days. Focus on top 50 most-viewed articles."