Why Knowledge Quality Matters
Your AI agents are only as good as the knowledge they have access to:Content Strategy
Document Types to Include
Document Types to Avoid
Writing for AI Retrieval
Clear Titles
The title is crucial for retrieval: Weak:Answer-First Structure
Put the answer at the beginning: Weak:Self-Contained Sections
Each section should make sense on its own: Weak:Organization
Hierarchical Structure
Organize documents logically:Naming Conventions
Use consistent naming:Tagging Strategy
Apply tags consistently:Content Quality
Quality Checklist
For each document:- Title accurately describes content
- Content answers a specific question
- Information is current and accurate
- Steps are clear and complete
- No broken links or references
- Consistent formatting throughout
Using Quality Scoring
Enable AI quality analysis:- Navigate to Knowledge → Quality
- Select documents to analyze
- Review scores and suggestions
- Address issues identified
Quality Score Interpretation
Improvement Techniques
Keyword Optimization
Include terms users actually search for: Before:Question-Answer Format
Structure documents as Q&A:Chunking for Retrieval
Break large documents into logical sections: Before: One 5,000-word document After:- Overview (500 words)
- Getting Started (800 words)
- Configuration (1,000 words)
- Advanced Usage (1,200 words)
- Troubleshooting (1,500 words)
Multi-Language Support
Translation Strategy
Translation Quality
- Use professional translation for critical content
- AI translation works for straightforward content
- Always have native speakers review
Managing Translations
Keep translations in sync:- Mark source language documents
- Track translation status
- Flag when source changes
- Re-translate updated content
Source Management
Connector Configuration
For each external source:Manual Sources
For content not in external systems:- Create dedicated manual source
- Use consistent formatting
- Include metadata (author, date)
- Review quarterly
Source Prioritization
When documents overlap, set priority:- Primary: Official documentation
- Secondary: FAQs and guides
- Tertiary: Blog posts, announcements
Maintenance Schedule
Daily
- Review sync logs for errors
- Check for failed imports
- Monitor retrieval quality
Weekly
- Review low-quality score documents
- Update documents based on support tickets
- Check for duplicate content
Monthly
- Audit document accuracy
- Review analytics for coverage gaps
- Update seasonal/time-sensitive content
Quarterly
- Full knowledge base review
- Remove outdated content
- Assess translation needs
- Evaluate source effectiveness
Common Issues
Low Retrieval Quality
Symptoms: Agent gives irrelevant answers or says “I don’t know” when information exists. Solutions:- Improve document titles
- Add more keyword variations
- Check embedding model configuration
- Enable reranker
- Review similarity thresholds
Duplicate/Conflicting Information
Symptoms: Agent provides inconsistent answers to the same question. Solutions:- Consolidate duplicate documents
- Set source priority
- Remove outdated versions
- Add canonical markers
Missing Coverage
Symptoms: Users ask questions with no matching documents. Solutions:- Review “no answer” conversations
- Analyze common escalation topics
- Create content for gaps
- Check connector include patterns
Slow Sync
Symptoms: Changes in source don’t appear in AGO. Solutions:- Check sync schedule
- Verify credentials
- Review sync logs for errors
- Consider more frequent sync
Analytics Usage
Coverage Analysis
Review which topics are covered:Top Retrieval Misses
Documents frequently searched but not found:- Export retrieval analytics
- Identify patterns in failed searches
- Create or improve matching documents
- Re-test with same queries
Document Usage
Which documents are most helpful:Content Governance
Change Management Workflow
Use Change Proposals to manage content changes systematically: Best Practices:Types of Proposals
Knowledge Gap Tracking
Use Update Requests to track missing content:- Monitor gaps: Review pending requests regularly
- Prioritize by volume: Multiple requests = critical gap
- Link to conversations: Understand user context
- Create content: Fill gaps with targeted documentation
- Close the loop: Mark resolved with notes
Quick Wins
Immediate improvements you can make:- Fix titles - Make them question-based
- Add FAQs - Top 10 support questions
- Remove duplicates - Consolidate content
- Update dates - Remove outdated info
- Enable quality analysis - Find problem areas
Related
- Knowledge Overview — Feature overview
- Knowledge Quality — Quality analysis
- Set Up Your Knowledge Base — Setup tutorial
