When chatbots give wrong answers, the instinct is to blame the AI. But 90% of the time, the AI is doing exactly what it should—answering from the content provided.
The problem is the content.
This guide covers how to audit, structure, and maintain a knowledge base that produces accurate, helpful chatbot responses.
The Knowledge Base Audit
Step 1: List All Content Sources
Document everything the chatbot learns from:
- Marketing website (all pages)
- Help center articles
- FAQ page
- Pricing page
- Blog posts
- PDF product guides
Common finding: 100+ pieces of content, some contradicting each other.
Step 2: Grade Each Source
Evaluate every major content piece on three criteria (1-5 scale):
| Source | Accuracy | Completeness | Clarity |
|---|---|---|---|
| Pricing page | ? | ? | ? |
| Help center | ? | ? | ? |
| FAQ page | ? | ? | ? |
| Product guides | ? | ? | ? |
Anything below 3 needs immediate attention.
Step 3: Find Contradictions
Search for the same topic across sources:
Example: Return policy
- FAQ: "14-day returns"
- Help center: "30-day money-back guarantee"
- Pricing page: "Full refund within first month"
Three sources. Three different answers. The chatbot can't give consistent answers when content is inconsistent.
Example: Feature limits
- Pricing page: "5 users included"
- Marketing page: "Unlimited team members"
- Help center: "Up to 10 users on Pro"
Content Structure That Works
Rule 1: Single Source of Truth
For every topic, one page is authoritative. Other pages reference it.
Before:
- Return policy on FAQ page
- Return policy on checkout page
- Return policy in help center
- Return policy mentioned in blog posts
After:
- Single return policy page (
/policies/returns) - All other pages link to it: "See our return policy"
Configure chatbot to prioritize authoritative pages.
Rule 2: Complete Answers
Incomplete content:
Q: What's your return policy?
A: See our returns page for details.
Complete content:
Q: What's your return policy?
A: Return any unused item within 30 days of purchase
for a full refund. Items must be in original packaging.
Email returns@company.com with your order number.
Refunds process within 5-7 business days.
Exceptions:
- Sale items: 14-day return window
- Digital products: No returns after download
- Custom orders: Non-refundable
AI needs the actual information, not pointers to it.
Rule 3: Explicit Over Vague
Vague:
Shipping takes a few days depending on your location.
Explicit:
Shipping times:
- Local (within 50 miles): 1-2 business days
- Regional (within state): 2-3 business days
- National: 3-5 business days
- International: 7-14 business days
- Express option: Next business day (+$15)
Specific beats vague. Always.
Rule 4: Include Edge Cases
Main policy: "Returns accepted within 30 days."
Edge cases customers ask about:
- What if it's day 31? (Usually approved, contact us)
- What about gifts? (Gift receipt required, store credit issued)
- What if I lost the receipt? (Look up by email/order number)
- Opened software? (No returns after opening)
- Sale items? (14 days instead of 30)
Document every edge case ever answered by support. Now the bot handles them.
Rule 5: Use Customer Language
Search support tickets for how customers phrase questions:
Internal term: "Terminate service agreement" Customer term: "Cancel my subscription"
Internal term: "Payment method on file" Customer term: "My card" or "the card I used"
Rewrite content using customer language. AI will match their phrasing.
Knowledge Base Configuration
Source Priority
When sources conflict, higher priority wins:
1. Official policy pages (highest priority)
2. Help center articles
3. FAQ page
4. General website content
5. Blog posts (lowest priority)
Custom Content
For gaps in website content, add custom training:
Topic: Enterprise pricing
Content: Enterprise pricing starts at $500/month for up to
100 users. Custom plans available for larger teams.
Contact sales@company.com or book a call at [link].
This information is not on our public website by design.
Excluded URLs
Some pages confuse AI:
/blog/2022-pricing-announcement (outdated pricing)
/careers/* (not relevant to customers)
/press/* (marketing speak, not helpful)
Refresh Schedule
Automatic refresh: Weekly
Priority pages (/pricing, /features): Daily
When website updates, chatbot learns new content automatically.
Content Review Process
Weekly (15 minutes)
- Check Analytics → Failed Conversations
- Identify questions the bot couldn't answer
- Is content missing? Add it.
- Is content wrong? Fix it.
- Note patterns for monthly review
Monthly (1 hour)
- Update pricing if changed
- Add new products/features
- Remove discontinued items
- Review policy changes
- Check for outdated dates/numbers
Quarterly (2 hours)
- Full content audit (accuracy, completeness, clarity)
- Structure improvements
- Remove underperforming content
- Add frequently-requested topics
Expected Results After Audit
| Metric | Before Audit | After Audit |
|---|---|---|
| Resolution rate | 55-65% | 80-90% |
| Wrong answers | 20-25% | Under 5% |
| "I don't know" responses | 25-35% | 10-15% |
| Customer satisfaction | 3-3.5/5 | 4-4.5/5 |
| Support escalations | 35-45% | 15-20% |
Same AI technology. Dramatically better results from better content.
Common Knowledge Base Mistakes
Marketing-Speak Instead of Information
Bad:
"Our revolutionary solution transforms the way you do business with cutting-edge AI technology!"
Good:
"Our software automates invoice processing. Upload invoices as PDF or image, and the system extracts vendor, amount, date, and line items automatically. Processing takes 2-3 seconds per invoice."
Customers want information, not hype.
Assuming Prior Knowledge
Bad:
"To configure SSO, update your SAML settings in the admin portal."
Good:
"To configure Single Sign-On (SSO):
- Log into your admin account
- Go to Settings → Security → Single Sign-On
- Click "Configure SAML"
- Enter your Identity Provider's metadata URL
- Save and test the connection"
Write for beginners even if most users aren't.
Scattered Information
Same topic addressed differently across 5 pages. AI gets confused. Customer gets inconsistent answers.
Fix: Single source of truth. Other pages reference it.
Getting Started
Start free with Kya to improve chatbot accuracy:
- Export failed conversations from Analytics
- Categorize: What topics are failing?
- For each failed topic: Does content exist? Is it accurate? Is it complete?
- Fix the content (not the bot)
- Watch resolution rate climb
The bot is only as good as the content it learns from.
Give it good content, and it'll give good answers.
Chatbot accuracy isn't about AI sophistication.
It's about content quality.
When content is fixed, the bot becomes genuinely helpful.
Your chatbot isn't broken. Your knowledge base probably is.


