Best AI chatbot builders for small business websites

A chatbot on a small business website is a promise that someone, or something, will cope with the question. Most sites are not ready for that promise. The FAQ is thin, the pricing is “contact us”, and the owner checks mail twice a day. A widget will not repair that. It will say something anyway.

This guide is about builders you embed on a marketing site or a simple web app: the visitor asks, the bot answers from your material, and a person can take over. It is not a guide to a contact centre. If the queue behind the widget is the real problem, read AI customer support tools first. If you only want the form that already works, the lead capture guide is the better project.

I have not run a bake-off with a thousand chats. The descriptions below are about product shape. Confirm features and prices on the vendor’s site. Both move.

When a chatbot is the wrong project

Skip it, for now, if any of these are true:

• You cannot list the twenty questions people actually ask.
• Nobody will read transcripts next week.
• The honest answer to most questions is “it depends, talk to us”, and you are hoping the bot will hide that.
• You want the bot to pretend it is a named person on the team.

Write the twenty questions. Put the stable ones on a page. Link that page from the contact form. Measure whether people still ask them. If they do, a bot trained on that page has something to say. If they do not, you have saved yourself a subscription. The ten tasks list includes this chore without insisting you buy a platform.

What to demand from a builder

Sources you control. Upload pages, a help centre, or a small set of files. See which source it used. If you cannot see that, you cannot fix a bad answer.

A refusal. The bot must be able to say it does not know. Test it with a nonsense question and with a question about a competitor. Both should fail closed.

A handoff with the transcript. Email, a form, or a live person in an inbox you already use. The handoff should include what the visitor already said, or you will make them type it twice and they will not.

A visible identity. Say it is automated. Say how to reach a human. On a UK site, that sits next to your privacy notice: the chat text is personal data, and if a model provider sees it, say so.

An off switch that leaves the contact form in place. The widget will break on a Friday. The form should not break with it.

A price you can simulate. Messages, resolutions, or seats. Run a pessimistic month through the current pricing page. “Unlimited” on a starter plan is a sentence to read twice.

Builders, by the job they are built for

Chatbase

Chatbase is a straightforward “point it at your content and embed a widget” product. That is the right shape for a brochure site that finally has a real FAQ. You are not buying a helpdesk. You are buying the window. Check how handoff works on the current plan, and check whether you can delete the uploaded sources when a page goes out of date. Stale sources are how a bot keeps selling last year’s offer.

Tidio

Tidio is chat widget first, with Lyro as the AI layer and a small shared inbox behind it. Pick it when you want the conversation to stay in a product that also does ordinary live chat, and when you might later sit in the inbox yourself. It overlaps with the support guide. If you already chose a helpdesk, do not add Tidio as a second queue. One queue.

Crisp

Crisp is the same family of decision: inbox and widget together, aimed at small companies. Choose between Crisp and Tidio by running the same ten questions through a trial and by pricing the plan that includes the AI replies you would turn on. I will not pretend one wins on a number I have not measured. The handoff and the invoice are the test.

Botpress

Botpress suits a team that wants more of a builder: flows, channels, and a place for someone technical to be specific. It is more tool than a cafe needs for opening hours. It is plausible when the bot is part of a product, not a bubble in the corner of a Squarespace page, and when someone will maintain the flows. Read the current hosting options before you assume the data stays where you think.

Voiceflow

Voiceflow is a design-and-build tool for conversational flows, including chat on a site. It fits teams who want to draw the conversation, review it, and only then embed it. That is healthier than “upload the site and hope”. It is extra process for a five-page business. Use it when more than one person needs to agree what the bot is allowed to say.

Landbot

Landbot leans towards structured conversations, closer to a guided form than to a free-ranging agent. For a small business that is often a virtue. A flow that asks three questions and then emails you is a lead form with better manners. Treat a fully open AI mode, if the plan offers one, with the same suspicion as any other bot: sources, refusal, handoff. The lead capture pipeline may be all you wanted.

A widget you assemble

n8n plus a chat embed is possible and usually a worse idea than it sounds, unless you already run n8n and you enjoy owning the failure. You will be building session state, a front end, logging and an abuse limit. The email assistant is a better first AI project because the mailbox already exists. Build a custom bot when a product cannot do the handoff you need, not because a tutorial made the HTTP node look easy.

A trial that takes an afternoon

Write twenty questions: ten the site answers, five it should refuse, five that should become “talk to a human”, including one about price and one about a complaint. Run them. Keep the product only if the refusals refuse, the handoff arrives in an inbox you will see, and you can tell which page an answer came from.

Then read the privacy page of the shortlisted product. The chat is personal data. If you are in the UK, your privacy notice should say a chat is in use and, in plain words, if a third-party model reads it. Link the notice from the widget, not only from the footer.

Turn the widget on for one page, not the whole site, if the tool allows. The contact page is the honest place. A bubble on every article is how you collect questions you did not staff for.

Freelancers choosing tools for their own week, rather than a widget for customers, should read AI tools for freelancers. The widget can wait until a person is tired of typing the same answer, and even then a saved reply inside the email assistant might be the smaller fix.