How it works

Write your knowledge base like an FAQ, not a brochure

An assistant answers as well as its content is shaped: one question per entry beats a glossy PDF every time.

September 24, 2026 · 4 min read

A salon owner uploads the brochure. Three pages, nicely designed, PDF export from the website: who we are, our philosophy, our award-winning team. She asks the assistant a simple question to test it — do you take walk-ins on a Saturday — and it gives a vague, half-right answer, or nothing at all. She assumes the assistant is broken. It isn't. The brochure never actually says the answer in a way anything could find.

This is the most common reason a new assistant disappoints in its first week. Not the technology, and not the amount of content uploaded. The shape of the content. A knowledge base that reads well to a person skimming a website is often the one that answers worst when a customer asks it a direct question.

What a brochure is actually for

A brochure is written to be read start to finish and to persuade along the way. Facts get buried inside sentences built for flow, not for matching. "Our flexible scheduling means we're able to accommodate most customer needs, including weekend slots where staffing allows" technically answers "are you open Saturdays" — but nothing will match a customer's short, blunt question to that long, hedged sentence. The fact is in there. It's just wrapped in six words of throat-clearing for every one word of answer.

One question, one answer

The content that retrieves well looks nothing like a brochure. It looks like a list of the questions a customer would actually type or say, each followed by a short, direct answer. No preamble, no scene-setting, no second sentence explaining the philosophy behind the policy. Just the fact.

  • •Do you take walk-ins on a Saturday?
  • •How much is a first consultation?
  • •Do you offer payment plans?
  • •What's your cancellation policy if I'm running late?
  • •Do you deliver outside the city?
  • •Can I bring my dog into the shop?

Each of those is one entry. Not a paragraph that mentions all six somewhere inside a page about the business's history. A business that writes down the actual questions its front desk or its inbox gets, in the actual words customers use, has done most of the work before it's even switched anything on.

Strip the marketing voice

The second mistake is tone, not structure. Even businesses that build proper question-and-answer entries often can't resist dressing the answer up: "state-of-the-art facility", "passionate about client care", "industry-leading turnaround times". None of that helps a customer who asked how long a repair takes. It doesn't help the assistant either — adjectives don't match against a question, facts do. The answer to "how long does it take" is a number of days, not a paragraph about craftsmanship.

A knowledge base that reads well to a person is often the one that answers worst for a machine.

The test that catches the gaps

Before trusting a knowledge base, run the test that actually matters: write down the ten questions the phone or the inbox gets most often in a normal week, and ask the assistant every one of them. Not the flattering questions about opening hours. The awkward ones — refund policy, whether a specific brand is stocked, whether the therapist speaks a second language, whether a deposit is refundable. Anywhere it fumbles, that's not a technical fault. It's a missing entry, and now it's on the list to write.

When the answer isn't there

Not every question belongs in the knowledge base, and that's fine. A good assistant that can't find an answer should say so and hand the conversation to a person, rather than improvise something plausible from the general shape of the business. Refusing to guess isn't a failure of the system — it's the difference between an assistant a business can trust with real customers and one it has to double-check constantly.

Keep it living, not launched

A knowledge base written once at setup and never touched again starts going stale the first time a price changes or a policy shifts for the holidays. The useful habit is to check what customers are actually asking — most dashboards will show the questions that came in and where the assistant handed over to a human — and add the missing answers as short, plain entries, the same way as the first batch. That short list of hand-offs is usually a better guide to what's missing than guessing from scratch.

AskLeya answers only from the content a business gives it, across the website widget, WhatsApp, Instagram and Messenger, and hands over to a person when it doesn't know. It can only be as good as the entries behind it — which is exactly why the shape of those entries matters more than the length of the brochure they came from.

See it answer your own questions

Point it at your website and ask it something only your business would know.

Try it free

← All posts