Most chatbot accuracy problems are content problems in disguise. If your knowledge base is vague, scattered or written for people who already know your business, the bot will struggle, no matter how capable the underlying model is.
This guide shows how to write entries that a chatbot can actually use, with before-and-after examples you can copy.
Why chatbots struggle with typical help content
Help centers are usually written by people for people who browse. They rely on context: a page title, a menu, the article above. A chatbot does not browse. It usually receives small chunks of text pulled out of your documents and has to answer from those chunks alone.
That means a sentence like "This applies to all plans except the ones mentioned above" becomes meaningless once it is separated from "above." The bot either ignores it or guesses.
Customer: Can I cancel my annual plan and get a refund? Chatbot: Yes, you can cancel anytime and receive a full refund.
If your actual policy is "Annual plans can be refunded within 14 days of purchase," the bot has just promised something you will not deliver. Often, the real policy was in the knowledge base, but split across two paragraphs that never got retrieved together.
Principle 1: One topic per entry, with a clear title
Each entry should answer one question or describe one policy. Give it a title that matches how customers ask.
Before: "Billing information" (a long page covering payment methods, invoices, refunds, cancellations and taxes)
After: Five separate entries:
- "Which payment methods do you accept?"
- "How do I download an invoice?"
- "Can I get a refund on an annual plan?"
- "How do I cancel my subscription?"
- "Do your prices include tax?"
Question-style titles help retrieval because they look like the customer's question.
Principle 2: Make every entry stand on its own
Write each entry as if it will be read in isolation, because it will be.
Before: "As mentioned, this only applies to the Pro tier. Contact us for the others."
After: "Priority phone support is available on the Pro plan only. Customers on the Starter and Team plans can get help by email at the support address listed on the contact page, with replies within one business day."
Repeat the product name, the plan name and the key condition inside the entry. Some repetition across entries is fine and even helpful.
Principle 3: State facts, limits and negatives explicitly
Bots fill gaps. Close the gaps by saying exactly what is and is not true.
- Include numbers and units: "14 days," "up to 5 users," "orders over $50"
- Include conditions: "only for orders shipped within the US"
- Include negatives: "We do not ship to PO boxes," "We do not offer phone support on weekends"
- Include exceptions in the same entry, not a separate footnote
If customers frequently ask about something you do not offer, write an entry saying so. A one-line "We do not currently offer a free trial of the Enterprise plan" prevents a surprising amount of invention.
Principle 4: Use plain, consistent wording
Pick one name for each thing and use it everywhere. If your plans are called "Starter," "Team" and "Business," do not also call them "Basic" or "tier 2" in older articles. Inconsistent naming makes the bot treat one thing as several, or several things as one.
Avoid marketing language in support content. "Blazing-fast, worry-free delivery" gives the bot nothing to quote. "Standard delivery takes 3 to 5 business days within the mainland US" does.
Principle 5: Put the date and owner on time-sensitive entries
Prices, promotions, opening hours and shipping times change. Add a last-reviewed date and an owner to each entry that can go stale. That makes it easy to spot entries no one has looked at in a year. For a fuller process, see keeping your chatbot's knowledge up to date.
A quick template for each entry
Title: [The question as a customer would ask it]
Answer: [One or two sentence direct answer]
Details: [Conditions, limits, exceptions, numbers]
Not covered: [What this does not apply to, if relevant]
Link: [The official page for more information]
Last reviewed: [Date] by [Owner]
You do not need to rewrite everything at once. Start with the 20 questions customers ask most, then the topics where a wrong answer is expensive: refunds, pricing, contracts and safety.
Your writing checklist
- Each entry covers one topic and has a question-style title
- Each entry makes sense if read completely alone
- Numbers, conditions and exceptions are inside the entry
- Things you do not offer are stated plainly
- Product and plan names are consistent everywhere
- Time-sensitive entries have a review date and owner
- Outdated entries are deleted, not just hidden from navigation
Checking whether your rewrite worked
After rewriting, ask the bot the questions the entries are meant to answer, in a few different phrasings. If it still gets something wrong, check whether the entry is being retrieved at all, or whether another page is contradicting it.
ChatLens360 can do this checking for you: it reads your site and uploaded documents, tests your chatbot with realistic questions, and for every wrong answer shows the expected answer, the source page and suggestions for what to add or correct in your knowledge base, along with a fix prompt you can paste in. Fix it yourself, or talk to us if you would rather have the team do it. Start with a free chatbot audit.