Blog · AI agents and workflows
Why agents miss answers that are sitting in your documents, the five files every business agent needs, the writing rules that make each entry findable, and a test to prove it works.
By Dijae Dadula · November 16, 2026 · 9 min read

A customer asks a shop's AI agent how much delivery to Cavite costs. The answer is in the knowledge base, on page six of a long document, in a table under the heading “Rates”. The agent replies that it is not sure and offers to connect a person. The owner opens the document, sees the fee right there, and wonders why the agent “can't read”.
An AI-ready knowledge base is a set of short, single-topic entries that each make sense on their own, so the agent can find the right one and quote it accurately.
Short answer: the agent never reads your whole document. It searches small pieces of it, and a piece that does not say what it is about is hard to find and easy to misread.
Most AI agents answer with retrieval-augmented generation (RAG): before replying, the system searches your files and passes the best-matching passages to the model. To make that search work, documents are split into chunks. OpenAI's file search, for example, splits files into chunks of 800 tokens with a 400-token overlap by default. A long document becomes dozens of separate pieces.
The problem is what a piece loses when it is cut out. Anthropic's research on retrieval gives the classic example: a chunk that says “The company's revenue grew by 3% over the previous quarter” does not say which company or which quarter. The same happens with business documents. A table row that says “₱150 · 2 to 3 days” means nothing once it is separated from the heading that said “Delivery to Cavite”.
Anthropic measured how much this matters. Adding a short line of context to each chunk before storing it cut failed retrievals by 35%, and by 49% when combined with keyword search, on its test sets. You do not need to build that system yourself. You get much of the same effect by writing entries that carry their own context from the start.
Short answer: five, each with one job: business facts, products or services, policies, FAQs, and handoff rules.
A common mistake is uploading everything: brochures, old price lists, chat exports, the website copied page by page. More documents do not make a smarter agent. They make more places for two versions of the same fact to disagree. Start with five files and put each fact in exactly one of them, the “one fact, one home” rule from grounding an AI agent in your business knowledge.
| File | What goes in it | Changes how often |
|---|---|---|
| Business facts | Name, locations, hours, contact channels, service areas, payment methods | Rarely |
| Products or services | One entry per item: what it is, who it is for, price, options, what is not included | With every price or menu change |
| Policies | Delivery, returns, refunds, cancellations, warranties, booking rules, each as its own entry | When the policy changes |
| FAQs | The real questions customers ask, in their words, with full-sentence answers | Monthly, from new questions in chat |
| Handoff rules | What the agent must not answer, and who takes over | When the team changes |
The last file connects to your agent's instructions. How to write those is in AI agent instructions for any business.
The more documents you upload, the more the agent knows.
Every extra document is another chance for an outdated or conflicting version to be retrieved. A small, clean set beats a large, messy one.
Short answer: one topic per entry, the subject named in the first sentence, full sentences instead of yes or no, and exact numbers with a date.
Intercom's guidance for its Fin AI agent lines up closely with what the retrieval research shows. Its help centre asks for single-topic sections, full sentences instead of bare “yes” or “no” answers, precise numbers and limits, numbered lists for steps, and written text alongside every image. Put together, that gives eight rules:
Write every entry so it still makes sense if it is the only thing the agent reads.
Short answer: a short title phrased like the customer's question, a one-sentence answer, the details and conditions, and a footer with the date and owner.
Copy these two templates and replace the brackets. Keep each entry short; if it runs past a few paragraphs, it is probably two topics.
ENTRY: [Customer question, e.g. How much is delivery to Cavite?]
ANSWER: [One full sentence that names the subject, e.g. Delivery to
Cavite costs PHP 150 and takes 2 to 3 working days.]
DETAILS:
- Applies to: [who or which orders]
- Conditions: [minimum order, cut-off time, exceptions]
- Not included: [what this does not cover]
IF UNSURE: [what the agent should do, e.g. hand off to the team]
UPDATED: [date] | OWNER: [name or role]POLICY: [Name, e.g. Refunds for online orders]
SUMMARY: [One sentence a customer could act on.]
STEPS:
1. [First thing the customer does]
2. [What happens next, with the time it takes]
3. [How they get the refund or replacement]
LIMITS: [time window, condition of item, exclusions, exact numbers]
THE AGENT MAY: [explain the policy, share the link, collect details]
THE AGENT MAY NOT: [approve exceptions, promise refunds] -> hand off
UPDATED: [date] | OWNER: [name or role] | SOURCE: [link to the public policy page]The “may not” line matters as much as the facts. A refund rule the agent invents is a promise your business may have to keep, as covered in the Air Canada chatbot ruling.
Short answer: give every entry an owner and a review date, retire expired content on the day it expires, and add new entries from the questions the agent could not answer.
Three habits keep it honest. First, put an end date on every promo the day you add it, and delete it on that date. Second, treat a price change as a knowledge base change: the same person who updates the price list updates the entry. Third, read the conversations your agent handed off. Each one is either a missing entry, an unclear entry, or a question the agent should never answer. The weekly side of this is in AI agent monitoring after launch.
How you will know it works (acceptance criteria for the 20-question test):
The table below lists the checks to run after loading the files, and what a pass looks like.
| Check | Pass when |
|---|---|
| Accuracy | At least 18 of 20 answers match their entry on every number, date and condition |
| No invention | Zero answers contain a price, fee or policy that is not in the knowledge base |
| Uncovered questions | Questions with no entry are handed off, not guessed |
| Freshness | Every entry has a date from the last 90 days or a confirmed review |
| Retest | The 20 questions are rerun after every price, policy or agent change |
An honest limitation: a well-written knowledge base raises the odds of a correct answer, but it does not guarantee one. How well retrieval works also depends on the platform's search, the model and your agent's instructions, which you may not control. That is why the test set and a human handoff stay in place even after the agent passes.
It is the set of documents an AI agent searches before answering, such as business facts, product and service details, policies and FAQs. The agent quotes from it instead of relying on what the model learned in training.
Many small, single-topic entries usually work better. Systems split documents into chunks before searching, so an entry that names its own subject and stands alone is easier to find and harder to misread.
You can, but website pages mix several topics, repeat facts and often hold prices in images. Use them as raw material, then rewrite the facts into short entries with one home each.
Update it the same day a price, promo or policy changes, and review it once a month using the questions the agent handed off or answered wrongly.
Get your agent's knowledge right
Want a knowledge base and AI agent set up so customers get accurate answers from day one? Book a free AI Automation Blueprint call.
Prefer to learn it step by step? Join the free weekly newsletter.
Join the free newsletter on AI agents, automation and turning your skills into income. Prefer video? Watch the walkthroughs on YouTube.
Want a system like this built for your business? Book a free AI Automation Blueprint call, or see the done-for-you services at my consultancy, IRD Digital Marketing Services.
DIJAE DADULA
Dijae Dadula · AI automation and systems specialist · Cavite, Philippines · Founder of IRD Digital Marketing Services
Home · Blog · Book a call · Newsletter · YouTube · Threads · Transparency
Some links on this site are affiliate links. If you buy through them, I may earn a commission at no extra cost to you.
© 2026 Dijae Dadula. All rights reserved.