Every guide on how to add an AI chatbot to your website spends most of its length on the install. The install is one line. If that were the hard part, every site with a chat bubble would be capturing leads, and most of them are not.
What actually separates a chatbot that earns its place from one you quietly remove three months later is five decisions, none of which are technical. Here they are, in the order they matter, with the install at the end where it belongs.
1. Decide where its answers come from
This is the whole thing. A chatbot is only as good as what it has read.
There are two kinds of product sold under the same name. The first is a rule-based bot: you write the questions, you write the answers, and anything you did not anticipate gets a shrug. The second reads your actual site — your pages, your product descriptions, your prices, your FAQ — and answers from that.
The second kind is the one worth having, but it comes with a condition people skip: it will answer from whatever you point it at, including the things you forgot were still published. The 2023 pricing page nobody deleted. The service you stopped offering. An AI agent will quote all of it with total confidence.
Before you connect anything, open your own site and read it as a stranger. If two pages disagree about your price, fix that first. We wrote a longer piece on this — how to train an AI chatbot on your own content — because it is where most bad answers actually come from.
2. Decide what it is allowed to do
"Chatbot" covers four quite different jobs, and the more of them you turn on, the more careful you have to be:
| Job | What it needs from you | Risk if you get it wrong |
|---|---|---|
| Answer questions | Accurate pages | A confidently wrong answer |
| Capture leads | Somewhere for them to land | Leads collected and never seen |
| Take payment | Correct, current prices | Selling at last year's price |
| Book appointments | A real calendar with real availability | Double bookings |
Start with the first two. Answering and capturing are almost impossible to get badly wrong and they are where most of the value is anyway. Add selling and booking once you have watched a few weeks of real transcripts and you trust what it says.
3. Decide what happens when it does not know
It will not know things. The question is what it does in that moment, and there are only three honest options: say so and offer to take a message, hand over to a human, or make something up.
Every chatbot does one of these. Only two of them are acceptable, and the third is the reason people distrust the category. Before you go live, ask it something deliberately outside your business and see what comes back. If it invents an answer, that is the product telling you what it will do to a real customer at 1am.
4. Decide where the leads go
This is the most common failure and the least dramatic. The bot works, the conversations happen, the visitor leaves their email — and it sits in a dashboard nobody opens.
Pick the inbox a human actually reads. Send every captured lead there, with the full transcript attached, not just the email address. The transcript is the part that matters: it tells you what they wanted before you call them back.
5. Decide how you will know whether it worked
Agree the number before you install, because afterwards you will be tempted to count conversations, and conversations are not the point. Useful numbers:
- Leads captured per week. The only one that maps to money.
- Share of chats resolved without you. If it is near zero, the content is wrong.
- What people actually asked. Read the transcripts weekly for the first month. This is free customer research and almost everyone ignores it.
That last one tends to pay for the whole thing on its own. The questions visitors ask a bot are the questions your website failed to answer. Fix those pages and the rest of your site gets better too.
Now the install
With those settled, adding the chatbot to your website is genuinely three steps:
- Point it at your site so it can read your pages.
- Check what it learned — ask it five questions you know the answers to.
- Paste one script tag before the closing
</body>tag.
Where that tag goes depends on your platform, and the details differ enough to be worth their own pages: WordPress, Shopify, Wix, or any other site.
One technical note worth insisting on, whatever you use: the widget should load after your page does. A chat bubble that delays your content is costing you more visitors than it converts.
Three mistakes worth avoiding
Launching it everywhere at once. Put it on a few pages first. You will learn what it gets wrong at a scale where fixing it is still easy.
Writing a long welcome message. Nobody reads it. One short line that invites an actual question outperforms a paragraph about how you are here to help.
Never reading the transcripts. Install it, check the numbers, and go back to work — and six months later you still do not know that forty people asked whether you deliver on Sundays.
the short version
- The script tag is not the hard part. The content it reads is.
- Start with answering and capturing leads. Add selling and booking later.
- Test what it does when it does not know, before a customer does.
- Send leads where a human will see them, with the transcript attached.
- Read the transcripts weekly for the first month. That is where the value hides.