CallWhatsApp

Planning

An AI chatbot on a business website: what to know

A chatbot can answer product questions at any hour, and it can also answer wrongly with confidence. Here is what it takes, what can go wrong and when not to bother.

Published 11 October 2026 · 3 min read

“Website with an AI chatbot”, “chatbot integration services” and “website chatbot developer” are growing searches, and the idea is attractive: a helper that answers customers’ questions at any hour. It can work. It can also embarrass a business. This note sets out what is involved so you can decide with open eyes.

For transparency: the two client sites on the Work page each have an AI product-expert assistant for specifications, grades and data sheets. They are backend features that were scoped on their own. An assistant is not part of any of my packages unless it is agreed in a written proposal, and I would tell you honestly whether you need one.

What an assistant needs behind it

  • Content to answer from. Specifications, prices, policies, data sheets, FAQs. The assistant is only as good as the facts it is given, and someone has to keep them current.
  • A backend. It runs on a server that talks to an AI service and your content. See frontend, backend and what your site needs.
  • A running cost. AI services usually charge for use, and hosting costs money. Both continue after launch, and usage can rise.
  • Rules. What it may answer, what it must refuse, when it hands over to a person, and what it says when it does not know.
  • Testing. Before launch, a long list of real customer questions, including awkward ones.
  • Monitoring and fixes. Someone reads what it said, corrects it and updates it when your business changes.

How it goes wrong

  • A confident wrong answer. It may state a wrong specification, price or policy as fact. For technical or health products this can cause real harm.
  • Out-of-date information. A price changed and the assistant did not.
  • Promising what you do not offer, such as a discount, delivery date or guarantee.
  • Handling private information carelessly. Customers may type their details into it. You are responsible for where those go.
  • Looking helpful while blocking a real person. A visitor who needs a call gets a loop.

When it is worth considering

  • You have a large range of products or documents that customers query constantly.
  • Your staff answer the same questions repeatedly and the answers are written down.
  • You can afford the running cost and a person to supervise it.
  • A wrong answer will not cause serious harm, or a person checks it.

When a simpler route serves better

For most small businesses, the cheaper route works better:

  1. A clear FAQ on the pages where questions arise.
  2. Specifications and data sheets published plainly, so the answer is on the page.
  3. A WhatsApp link on every page, answered by a person. See WhatsApp on a website.
  4. A short quote-request flow for catalogue sites; see how a quote request should work.

Do these first. If customers still wait too long, you will know what an assistant needs to answer, because you will have written it down.

Questions to ask anyone who offers one

  1. Which AI service does it use, and what happens to customer text?
  2. What is the monthly cost at my expected volume?
  3. How does it hand over to a person, and when?
  4. What does it say when it does not know?
  5. Who reads its answers, and how do mistakes get corrected?
  6. What happens to it if I stop paying, or you stop supporting it?
  7. What is in the written scope, and what is not?

If you are weighing an assistant for a product-heavy site and want an honest view, message or call Harman with what you sell and the questions customers ask most.

Where this leads

CallWhatsApp