How to Set Up an AI Chatbot to Answer Customer Questions on Your Website
By Automate Basics
Loading guide…
By Automate Basics
Gather your FAQs and help docs into one clean document, feed them to an AI chatbot tool so it answers only from your content, set a fallback that hands off to a human when it is unsure, then add the chat widget to your website. Test it with your 20 most common real questions before you go live. The grounding step is what stops it inventing answers.
A support chatbot is only useful if it answers from your business, not the open internet. The whole job is this: take your real help content, give it to an AI tool as its only source of truth, and put a chat bubble on your site. Do that and customers get correct answers at 2am about your shipping, your refunds, your hours. Skip the grounding step and the bot will cheerfully invent a returns policy you do not have. So the order is: gather content, ground the bot, set a human fallback, test, launch.
Before you touch any tool, collect what the bot will learn from. Open one document and dump in everything a customer asks you:
Write answers in plain language and keep them current. This document is the bot's brain. A messy or outdated doc makes a messy, outdated bot, so spend most of your time here, not in settings.
This is the step that separates a trustworthy bot from a liar. In your chatbot tool, upload that document (or point it at your website) as the knowledge source, then find the setting that says answer only from these sources. Tools like Tidio / Chatbase and Intercom Fin are built around exactly this: you give them your docs, they answer from them and stay quiet outside them. If you would rather just answer questions yourself for now, paste your doc into ChatGPT or Claude and ask away, no widget needed.
A bot that guesses loses customers. A bot that says "let me get a person" keeps them. Find the handoff setting and tell it, in plain English: if you are not confident or the customer asks for a human, stop answering and collect their email or open live chat. One short instruction does it: "If unsure, reply that you will pass this to the team and ask for their email." This single setting is the difference between a chatbot people trust and one they learn to ignore. Treat it as required, not optional.
Do not launch on hope. Before the widget goes live, ask the bot the 20 questions you actually get most, in the messy way customers phrase them. Try "do u ship to canada," "wheres my order," "can I get a refund after 30 days." Watch for three failures: a wrong answer, a made-up policy, or a confident reply where it should have handed off. Fix those by improving your source doc, not by arguing with the bot. When the common questions come back right, you are ready.
Now put it where customers are. Most tools give you a small snippet of code to paste into your site once, or a one-click app for your platform. On Shopify, Wix, Squarespace, or WordPress, install the app or plugin and the chat bubble appears on every page automatically, no code touched. Place it bottom-right where people expect it. Load your homepage, open the chat, and ask one real question to confirm it answers live. That is your bot, on your site, working.
A chatbot is not "set and forget." Once a week, read the conversations it had. You are looking for two things: questions it got wrong, and questions it could not answer at all. Each one is a gap in your source doc. Add the missing answer, and the bot gets smarter the next day. This loop, read the logs and patch the doc, is how a decent bot becomes a great one over a month. Your customers are telling you exactly what to fix, for free.
Open a blank document and write out the five questions customers ask you most, with your real answers underneath. That is enough to start. Drop it into a chatbot tool as the knowledge source, turn on answer-only-from-sources, add the "hand off to a human if unsure" instruction, and ask it those five questions. Seeing it answer correctly from your own words, then admit it when it does not know, is the moment you know this is safe to put on your site.
Before you touch a chatbot tool, open a doc and write down the ten questions customers actually ask you — pull them from your sent mail and order them by frequency. That list is the whole project; the widget is an afternoon.
That’s the whole lesson. Try it on a real task while it is fresh, then come back for the next one.
Pick any chatbot tool that lets you upload your docs as the knowledge source and set a human fallback. The principles matter more than the brand: ground it in your content, add a fallback, and test with real questions.
The same corner of the library, one job further on.