Picture a coaching institute with a chat bubble on its website. A parent types "Is there a batch on Sunday mornings?" None of the institute's pages mention Sunday. A chatbot that falls back on general knowledge may still answer with something that sounds right, like "Yes, 8 to 11 am", and the parent plans their week around a class that does not exist. On a business website, a wrong answer given with confidence does more harm than an honest "I don't know".
You don't need to write code to fix this. The fix comes from a handful of decisions about content and testing, and you, the site owner, are the one who has to make them. Below are the steps I would take, in order.
1. Choose the pages the bot may answer from
Don't hand the bot your whole website. Go through your pages and sort them into two groups:
- Pages it may answer from: opening hours, services, fees, location and contact, admissions or booking rules, and the FAQ.
- Pages it should leave alone: old blog posts, past offers, job ads, press releases and any page you wouldn't want read back to a customer word for word.
The question to ask of each page is "would I be happy if a visitor took this as our official answer today?" If the answer is no, leave that page out. A short list of current pages beats a long list that includes last year's prices.
2. Write those pages so a reader cannot misread them
A bot that answers only from your pages is only as good as those pages. Before you switch anything on, read each chosen page as a stranger would:
- Put each fact in its own plain sentence. "We are open Monday to Saturday, 9 am to 6 pm. We are closed on Sunday." is better than a timetable image or a sentence buried in a paragraph about your history.
- Say what you don't do, too. "We do not offer home visits" lets the bot give a clear no instead of a vague maybe.
- Remove contradictions. If two pages give different fees, the bot can't know which one is current, and neither can a visitor.
- Write out numbers and phone numbers in text. Don't leave them only inside images or PDFs that are scans.
This step helps your human visitors as much as the bot.
3. Make "I don't know" an allowed answer
Whatever tool you use, check how it behaves when your pages don't cover a question. You want three things:
- It says plainly that it doesn't have that information. It doesn't guess and it doesn't fill the gap from general knowledge.
- It doesn't invent contact details, prices or names that aren't on your pages.
- When someone asks it to ignore its instructions or talk about something unrelated, it politely stays on the subject of your website.
If a tool can't show you this behaviour in a test, don't put it on a live site.
4. Test with real questions, including ones it should refuse
Write down twenty or so questions a real visitor might type, in their own words, including the short and badly spelled ones. Use a mix:
- Questions your pages clearly answer ("What time do you close on weekdays?").
- Questions your pages don't answer ("Do you have parking?" if no page mentions it).
- One or two attempts to push it off topic.
For each answer, check which page it came from. When an answer is right, you should be able to point to the sentence that supports it. When it's a refusal, make sure the refusal is honest and not a disguised guess. Keep this list and run it again whenever you change your pages.
5. Treat unanswered questions as a to-do list
Every "I don't have that information" is a visitor telling you what your website is missing. Look at those questions once a week, most frequent first. When "Do you have parking?" keeps coming up, a smarter bot won't help. One sentence on your contact page will.
6. Re-read the pages after every edit
Once you change a page, check that the bot has the new version before you trust its answers. If your tool reads pages only when you ask it to, make that part of your editing routine: edit, re-read, then run your test questions again. An old copy of your fees page is how a careful setup drifts back into wrong answers.
Adding the chat to your site
For most hosted chat tools, installing comes last and takes a few minutes. You copy one script tag from the tool's dashboard and paste it into your site's header or custom code settings, in your theme on Shopify or WordPress, in the custom code section on Webflow or Wix, or in the page template on a plain HTML site. Then open your site in a private window and ask the bubble a question from your test list.
The tool I work on
I work on TailGPT, a website AI agent built around the steps above. It answers only from the pages you tick and the documents you upload, says "I don't have that information" instead of guessing, checks every fact in an answer against the page it came from, and lists the questions your website doesn't answer, most asked first. It can still misread a badly worded page, which is why steps 2 and 4 matter whatever tool you pick. It re-reads your website when you ask it to. It isn't a helpdesk, so it won't hand a chat over to a person. It installs with one line of code on Shopify, WordPress, Webflow, Wix, plain HTML and more.
What this won't fix
Limiting a bot to your own pages makes wrong answers much rarer, but it can't make your pages correct. If a page is out of date, the bot will repeat the outdated fact. Keep the chosen pages current, read a few real conversations now and then, and treat every unanswered question as a page you still need to write.
Which question did your website turn out to be missing? Tell me in the comments.
Top comments (0)