You've decided to add an AI assistant to your website. Now the vendor asks for your "content," and you're staring at an empty document. Where do you start? What counts as a good answer? How long should it be?
The short version: your assistant's chatbot knowledge base should be a list of real customer questions, each with a short, complete, current answer. Write the questions first, in your customers' words. Write each answer so it makes sense on its own. Then give the whole thing one owner. A knowledge base is simply the library of approved material the assistant answers from.
This post walks through a template you can fill in over an afternoon. It also makes your website better, because anything a bot can't find, a visitor can't find either.
Where do the questions come from?
Don't invent questions. Collect the ones people already ask. Good sources, roughly in order of usefulness:
- Your email inbox and contact-form submissions from the last three months
- Voicemails and notes from phone calls
- Texts and direct messages on social media
- Questions your front-desk staff answer every day
- Google reviews that mention a surprise ("I didn't know they were closed Mondays")
- The "People also ask" box on Google when you search your own service
Aim for 25 to 40 questions to start. Group near-duplicates. If five people asked "Do you do weekends?" in five different ways, that's one question, but keep the phrasings, because they show how customers actually talk.
What does a good answer look like?
A good answer for an AI assistant has four traits.
- It leads with the answer. "Yes, we're open Saturdays from 9 to 1" beats a paragraph about your commitment to flexible service.
- It stands alone. The bot may quote one answer without the ones around it. Don't write "as mentioned above" or "see the previous question."
- It names things plainly. Use the same service names as your website and invoices. If you call it a "tune-up" in one place and a "seasonal service" in another, the bot may treat them as different things.
- It states limits. Say what you don't do, where you don't go, and when the answer is "it depends."
Compare two versions of the same answer.
Before: "We offer competitive pricing and flexible options tailored to your needs. Contact us for details."
After: "A standard cleaning visit starts with a free on-site estimate. We quote a fixed price after the visit, not by phone, because the size of the space changes the work. Estimates usually take about 20 minutes."
The second one gives a visitor something to act on. It also shows the bot what to say, and what not to promise. We never quote a figure we haven't been given, and neither should your assistant.
A template you can copy
Use the same shape for every entry. Put it in a spreadsheet or a plain document.
- Question: the customer's wording
- Short answer: one or two sentences, answer first
- Details: extra facts, conditions, exceptions (optional)
- Next step: book, call, fill out a form, or "hand off to a person"
- Last checked: a date
- Owner: who updates it
The "next step" line is what turns an FAQ into a working assistant. Without it, the bot answers and the conversation ends. With it, the bot can offer to book a visit or collect contact details. See How an AI Assistant Qualifies Leads Before They Reach Your Inbox for what happens after that offer.
Which topics should every FAQ cover?
Check your list against these categories. Missing ones are usually the gaps customers hit first.
- Hours, location, and service area. Include holiday closures and how far you travel.
- Services and what's excluded. Name what you don't do, so the bot doesn't guess.
- Pricing signals. A starting point, a range, or "we quote after an estimate" is all fine. Only publish figures you actually stand behind.
- How the process works. What happens after someone books, and how long it takes.
- Policies. Cancellations, deposits, refunds, warranties, insurance.
- Who to contact for what. Billing questions, emergencies, complaints.
- What the bot should not answer. Legal, medical, or safety advice, custom quotes, and anything involving a specific customer's account.
That last item matters. Writing "if asked about X, offer to connect the customer with a person" is as important as any answer. A well-built assistant needs clear escalation rules, which we cover in What "Trained on Your Data" Means for a Chatbot.
How do you check the FAQ before launch?
Run a quick test before anyone else sees it.
- Pick 10 questions from your inbox that you did not use to write the FAQ.
- For each one, look for the entry that answers it.
- Mark it covered, partly covered, or missing.
Say you try 10 and find 6 covered, 2 partly, and 2 missing. That's an illustration, not a benchmark, but it tells you exactly which four entries to write or fix. Repeat with a fresh 10 until the "missing" column is nearly empty.
Then read every answer out loud, as if a customer asked you at the counter. If it sounds evasive or stiff, rewrite it. Remove anything out of date, and make sure two entries never contradict each other. When they do, the bot may pick either one.
How do you keep it from going stale?
A knowledge base is a living document. Three habits keep it accurate:
- Give one named person ownership, even if that person is you.
- Review it whenever prices, hours, or policies change.
- Each month, read a sample of real conversations and note any question the assistant couldn't answer. Those become next month's new entries.
Over time, the unanswered questions become a free report on what your website fails to explain.
Write the questions in your customers' words and the answers in your own, then keep one person responsible for both.
How Deca Digital helps
We build AI assistants that answer from your approved content and hand off to a person when they aren't sure. We can help you collect the questions, draft the answers, set the handoff rules, and plan how the knowledge base stays current. We're based in Celina, Texas, serve businesses across North Texas, and work remotely too. You can see more on our AI assistants page. Our dental practices and veterinary clinics pages show the kind of question list a practice ends up with.
If you'd like help turning your inbox into a working FAQ, book a free discovery call.