Support AI Skill
Kb Content Gap Analysis
Identify gaps in knowledge base coverage by analyzing support ticket topics, search queries, and customer questions that lack corresponding articles. Use when auditing knowledge base coverage, finding content gaps, planning article creation, improving searc...
Knowledge Base Content Gap Analysis
Identify gaps in knowledge base coverage to guide content creation and improve self-service.
Workflow
Content Gap Analysis Process
Trigger: Monthly content review; quarterly KB audit; declining search success rate:
- Search failure analysis: Extract search queries with zero results or zero clicks (last 30 days); identify top 50 failed searches; cluster by topic; prioritize by search volume.
- Ticket-to-article mapping: Analyze resolved tickets — what topics were covered vs. unsupported; identify high-volume ticket categories with low article coverage; calculate coverage ratio per category.
- Article performance review: Analyze existing articles — views, helpful votes, time on page, bounce rate; identify low-performing articles (high views, low helpful votes) indicating poor content quality; identify high-performing articles (potential expansion topics).
- Customer question mining: Extract questions from CSAT comments, NPS responses, community forum, chatbot fallback conversations; cluster by theme; identify recurring unanswered questions.
- Gap prioritization: Score each gap by — search volume (how many customers are looking), ticket volume (how many tickets on this topic), revenue impact (enterprise customers affected), urgency (compliance/security topics).
- Content creation plan: Generate article briefs for top gaps — title, target audience, key points, related articles, owner; assign to content team; set publication deadlines.
- Publishing and monitoring: Publish new articles; monitor performance (views, helpful votes, deflection impact); measure ticket volume reduction on covered topics; iterate.
- Quarterly audit: Full KB review — retire outdated articles, merge duplicates, fill remaining gaps, assess overall coverage score (target: > 85% of support topics covered).
Gap Analysis Framework
CONTENT GAP ANALYSIS — DATA SOURCES
======================================
Source 1: Search Failures (Help Center)
Data: Queries with 0 results OR 0 clicks on results
Volume: 1,200 failed searches last month
Top failed queries:
1. "how to export data to CSV" — 85 searches, 0 results → GAP
2. "API rate limit increase" — 62 searches, 0 clicks → GAP (article exists but irrelevant)
3. "connect to Salesforce" — 48 searches, 0 results → GAP
4. "two-factor authentication setup" — 41 searches, 0 clicks → LOW QUALITY (article outdated)
5. "cancel subscription" — 38 searches, 0 results → GAP
Source 2: Ticket Topic Coverage
Data: Resolved tickets mapped to KB categories
Coverage analysis:
Category Tickets Articles Coverage Score
Billing 850 12 72%
Account Management 620 18 85%
Technical Troubleshooting 1,200 25 65% ← LOWEST
API & Integrations 480 8 45% ← CRITICAL GAP
Feature Requests 350 0 0% ← BY DESIGN (not KB content)
Onboarding 280 15 80%
Security & Compliance 180 6 55% ← GAP (high urgency)
Source 3: Chatbot Fallback Conversations
Data: Questions where chatbot couldn't answer (escalated to agent)
Volume: 850 fallback conversations last month
Top fallback topics:
1. Integration setup (220 conversations) → GAP
2. Custom reporting (150 conversations) → GAP
3. Data migration (130 conversations) → GAP
4. Permission management (95 conversations) → LOW COVERAGE
5. Webhook configuration (85 conversations) → GAP
Source 4: Customer Survey Comments
Data: NPS and CSAT open-ended responses mentioning documentation
Volume: 120 comments mentioning "documentation", "guide", "how to"
Themes:
- "Wish there was a guide for X" (45 comments) → GAP
- "The documentation for Y is outdated" (30 comments) → LOW QUALITY
- "Can't find info about Z" (25 comments) → GAP
- "Video tutorial would help with A" (20 comments) → FORMAT GAP
Gap Priority Matrix:
Score = (Search Volume × 2) + (Ticket Volume × 3) + (Urgency × 2)
Priority 1 (Critical, score ≥ 20): API & Integrations, Security, Data Export
Priority 2 (High, score 10–19): Technical Troubleshooting, Custom Reporting
Priority 3 (Medium, score 5–9): Permission Management, Webhook Config
Priority 4 (Low, score < 5): Nice-to-have topics
Content Creation Plan
KB CONTENT CREATION PLAN — Q2 2025
=====================================
Article Briefs (Priority 1 — Critical):
1. "How to Export Data to CSV/Excel"
Category: Data Management
Target audience: All users (high search volume: 85/month)
Key points: Export steps, format options, filters, limitations
Related articles: Data import, bulk operations, API data access
Owner: Content Writer A
Deadline: 2025-02-15
2. "API Integration Guide — Getting Started"
Category: API & Integrations
Target audience: Developers, technical users (ticket volume: 480/month)
Key points: API authentication, rate limits, endpoints, SDKs, examples
Related articles: API reference, webhook setup, integration examples
Owner: Developer Advocate + Content Writer B
Deadline: 2025-02-28
3. "Security Best Practices and Compliance"
Category: Security & Compliance
Target audience: Admin users, compliance officers (urgency: high)
Key points: Encryption, access controls, audit logs, GDPR, SOC 2
Related articles: Two-factor auth, SSO setup, data privacy
Owner: Security Team + Content Writer A
Deadline: 2025-03-15
4. "How to Connect Salesforce to [Product]"
Category: Integrations
Target audience: Sales ops, admin users (search volume: 48/month)
Key points: Prerequisites, connection steps, field mapping, troubleshooting
Related articles: API integration, webhook setup, other CRM integrations
Owner: Integrations Team + Content Writer B
Deadline: 2025-03-01
Quality Improvement (Low-Performing Articles):
5. Update "Two-Factor Authentication Setup" (outdated — 41 searches, 0 clicks)
Issue: Screenshots from v2.0; current version is v3.5 (UI changed)
Action: Update screenshots, steps, add video tutorial
Owner: Content Writer A
Deadline: 2025-02-10
6. Rewrite "API Rate Limits" (exists but irrelevant — 62 searches, 0 clicks)
Issue: Article covers old rate limit system; new system launched 6 months ago
Action: Complete rewrite with new rate limit tiers, increase request process
Owner: Developer Advocate
Deadline: 2025-02-10
Edge Cases
- Rapidly changing product (gaps appear faster than content team can fill them):
- Detection: Gap count increasing month-over-month; coverage score declining
- Prevention: Tie content creation to product release cycle — article draft due with feature release
- Process: "Docs as code" — developers write API docs as part of feature development
- Triage: Focus on high-impact gaps (high volume, enterprise customers) first; accept temporary gaps for low-impact topics
- Metric: Time from feature release to article publication (target: < 7 days)
- Low-quality articles (article exists but doesn't help — high views, low helpful votes):
- Detection: Helpful vote ratio < 50%; high bounce rate (> 70%); average time on page < 15 seconds
- Analysis: Is content outdated, unclear, incomplete, or irrelevant to search query?
- Action: Rewrite article; update screenshots; add video; restructure for clarity; add troubleshooting section
- Prevention: Quality checklist before publishing; quarterly quality audit; SME review for technical articles
- Metric: Helpful vote ratio target > 70% for all articles
- Format gaps (text articles exist but customers want video/interactive content):
- Detection: Survey comments requesting video; high search volume for visual topics; community requests
- Analysis: Identify topics where visual/interactive format would help (setup, configuration, troubleshooting)
- Action: Create video tutorials (5–10 minutes); embed in existing articles; create interactive walkthroughs
- Balance: Not all topics need video; prioritize by search volume and complexity
- Metric: Video article helpfulness vs. text-only (A/B test); video completion rate
- Multi-language gaps (English KB covered but translations missing):
- Detection: Search volume in non-English languages; ticket volume from non-English regions
- Strategy: Translate top 50 articles first (by views); prioritize languages with highest customer volume
- Process: Professional translation for top articles; community translation for lower priority
- Quality: Native speaker review for translated articles; not just machine translation
- Metric: Non-English search success rate; non-English ticket deflection rate
- Overlapping articles (multiple articles cover same topic — confusing for customers):
- Detection: Semantic similarity analysis; customer confusion feedback; duplicate search results
- Analysis: Are articles truly duplicates or covering different angles? (e.g., "How to reset password" vs. "Account security best practices" both mention password reset)
- Action: Merge true duplicates; clarify scope of each article; add cross-references
- Prevention: Similarity check before publishing; content owner assigns clear scope per article
- Metric: Unique topic coverage; article redundancy score
Integration Points
- Help desk: Zendesk, Freshdesk, Intercom — ticket topic analysis, resolution data
- Knowledge base: Zendesk Guide, Confluence, Notion — article data, performance metrics
- Search analytics: Google Analytics, custom search logs — search queries, zero-result tracking
- Chatbot: Intercom bot, Drift, custom — fallback conversation analysis
- Survey tools: Delighted, SurveyMonkey — customer feedback on documentation
- Community: Discourse, Circle.so — customer questions, feature requests
- NLP: OpenAI, Google Cloud NL — topic clustering, semantic analysis, gap detection
- Content management: WordPress, Contentful — article management, versioning
- Analytics: Tableau, Power BI — gap analysis dashboards, coverage scoring
- Data warehouse: Snowflake, BigQuery — unified content analytics, historical trends