A restaurant owner uploads the PDF menu and the "about us" page from their website, sets the assistant live, and moves on. A week later a customer asks whether the tapas has anything without gluten, and the assistant answers with a line lifted from the about page — something about "seasonal, chef-driven small plates rooted in local tradition." It's not wrong exactly. It's also not an answer.
The assistant isn't bad at reading. The document just isn't written to answer questions. It's written to sound appealing to someone who already wants to eat there. An assistant doesn't need to sound appealing. It needs to know, in one sentence, whether the patatas bravas have dairy in them.
What a brochure actually contains
Marketing copy is built from paragraphs, not facts. A sentence like "our experienced team will find the perfect solution for your needs" carries no retrievable information at all — no price, no timeframe, no condition. It reads fine on a website because a human skims past it to the bit they actually want. An assistant has no bit to skim to. If the fact isn't stated plainly somewhere, there's nothing to retrieve, and it either guesses or says it doesn't know.
This is the part owners get backwards. They assume more content means better answers, so they upload everything — the full brochure, the press page, the founder's story. Volume isn't the problem. Shape is. A ten-page PDF with one buried sentence about deposits is worse than a single line that says: a twenty-pound deposit is required to book, refundable up to 48 hours before.
One question, one answer
The content that retrieves well looks less like a brochure and more like a staff handbook written for the person answering the phone. Each entry covers one thing a customer actually asks, in plain language, with the answer stated directly rather than implied.
- •Do you take walk-ins? Yes, but Friday and Saturday evenings are booking only.
- •Is there parking? No dedicated parking, but the council car park on Bridge Street is a two-minute walk and free after 6pm.
- •Can I bring my dog? Yes, in the outdoor seating area only.
- •Do you offer payment plans for treatment? Yes, over three or six months, arranged at the first consultation.
- •What's your cancellation policy? Full refund with 48 hours' notice, no refund inside 24 hours.
Notice none of these need a marketing voice. They need a clear question and a direct answer, ideally short enough to read in one breath. If a genuine answer runs long — say, explaining a multi-step booking process — that's fine, but it should still resolve the question rather than circle it.
Cut the marketing voice, not the information
This doesn't mean stripping personality out of the business. It means separating the two jobs a document can do. A website page persuades. A knowledge base entry informs. The same fact — "we use only free-range eggs" — can sit on the website as part of a warm paragraph about provenance, and sit in the knowledge base as its own line, answering the specific question a customer with a specific concern is going to ask.
A knowledge base written to sound good to a customer is not the same document as one written to answer a customer's question — the two jobs pull in opposite directions.
Stale content answers confidently and wrongly
The other common failure isn't tone, it's age. A clinic changes its deposit policy in March. The PDF on file still says the old figure in October. The assistant doesn't know the difference between current and outdated — it answers from whatever it's been given, with the same confidence either way. A wrong answer stated plainly does more damage than a vague one, because the customer believed it and acted on it.
The fix isn't a bigger document, it's a habit. Whenever a price, a policy or an opening time changes, that one line gets updated the same day, separately from whenever the website next gets a redesign. Businesses that treat the knowledge base as a living note — updated the moment something changes — get noticeably fewer wrong answers than those that treat it as a document written once at setup and revisited a year later.
Let the gaps tell you what to write next
The most useful source for what to add isn't imagination, it's the record of what customers actually asked and the assistant couldn't answer. That's the value of looking at conversation history rather than guessing at content in advance: the real questions arrive in the order customers actually think of them, not the order an owner assumed when writing the brochure. Somebody always asks about the thing that felt too obvious to write down — whether the fitting room is single-occupancy, whether the quote includes VAT, whether Saturday appointments cost extra. Those gaps are the actual to-do list.
AskLeya only answers from what it's been given — it doesn't invent details to fill a gap, and a thin knowledge base produces thin, hedged answers rather than confident wrong ones. That's a reasonable trade, but it puts the real work back where it belongs: not in choosing a chatbot, but in writing the plain, dated, question-shaped document underneath it.