Website chatbots for small business: what they cost and what goes wrong

A website chatbot is a typing receptionist

It is the little box in the corner of your site that answers typed questions. The jobs it does well are narrow: your hours, your service area, whether you carry a part, how to book, what to bring to the appointment, where to send a photo of the broken thing. It keeps working while you sleep, and it does not get tired of the same question.

Statistics Canada asks businesses about this every quarter. In the second quarter of 2026, 19.2% of businesses in Canada said they had used AI to produce goods or deliver services in the 12 months before the survey ¹. Among the businesses using AI, 28.2% used virtual agents or chat bots, behind data analytics at 36.6% and text analytics at 34.5% ².

Small does not mean left out. Among businesses with 1 to 4 employees, 19.9% reported using AI ³. So this is a normal thing for a shop your size to be looking at. That does not make it the right call for every shop.

What the entry plans cost

Prices here come from each vendor's own pricing page, and none of those pages names a currency. Treat them as US dollars, then add GST and whatever your card issuer charges on the exchange. Most of the cheap numbers you see advertised are annual billing rates, so paying month to month costs more.

Tidio's Starter plan is $24.17 a month at the annual rate. It comes with 100 billable conversations and 50 Lyro AI Agent conversations, which the page marks as one-off rather than monthly ⁴. Chatbase's Hobby plan is $32 a month billed yearly, with 700 message credits a month and top-ups at $40 per 1000 credits ⁵. Crisp's Mini plan is $45 a month per workspace, with enough included AI credit for around 90 automated conversations ⁶.

The bigger platforms work differently. Zendesk includes AI agents in its Suite plans and bills them per automated resolution, on top of $55 per agent a month paid yearly for the human side of the desk ⁷. So the monthly number you see advertised is the minimum, not your final bill.

Know how your chatbot plan is metered

The headline price tells you less than the unit the vendor counts. There are three units in common use, and each one suits a different kind of customer.

Per conversation suits a site with steady, short questions. Tidio counts a Lyro conversation once the AI replies at least once, no matter how long the chat runs after that ⁴. Fifty one-off conversations run out fast on a busy site, so check whether your included AI chats renew each month or not.

Per message credit suits short exchanges and punishes long ones. Chatbase deducts credits as messages go back and forth and tops up at $40 per 1000 credits when you run low ⁵. Crisp works on a similar idea, with a credit balance that covers around 90 automated conversations on the entry plan ⁶.

Per result sounds fairest, and often is, as long as you read the definition. Zendesk says paying per automated resolution means you pay only for requests the AI actually resolved without passing them to a person ⁷. Ask any vendor who prices this way what counts as resolved, because a customer who gives up and closes the window can still look like a customer who got the answer.

It will sound certain even when it is wrong

This is the part vendors skim past. These tools do not know when they are guessing, and they do not pause to say so.

The Tow Center at Columbia tested eight AI search tools against news articles. Together, the tools gave incorrect answers to more than 60 percent of the queries ⁸. Those were news questions, not questions about your price list, so do not read that as your error rate. Read it as proof that sounding sure and being right are two different things.

So keep the bot on boring, checkable ground: hours, service area, booking links, what to bring, how to send a photo. Keep quotes, warranty terms, refunds, credit and anything touching safety off its list, and have it offer to get a person instead. Feed it only pages you truly keep current, because an old price on your site becomes an old price repeated to every visitor.

What your chatbot says, you said

A customer asked Air Canada's website chatbot about bereavement fares and was told the wrong thing. He bought tickets at full price, then asked for the difference back. Air Canada argued the chatbot was a separate thing, responsible for its own answers. The British Columbia Civil Resolution Tribunal did not accept that. It said it should be obvious to Air Canada that it is responsible for all the information on its website ⁹, and that it makes no difference whether the information comes from a static page or a chatbot.

That was a tribunal in another province, so no court has to follow it. But the reasoning is hard to argue with, and no small business should expect to get a kinder one. If your bot promises a price you cannot honour or a policy you do not have, you own the result.

The practical version is a written list. Decide which questions the bot may answer, put the answers in writing on your own pages, and tell it to hand everything else to a person with your name and number. A plain handoff costs you nothing. A confident wrong answer can cost you a customer and a refund.

Be open about your chatbot and privacy

Chat transcripts fill up with names, phone numbers, addresses, job details and sometimes money or health information. That is personal information, and in Alberta it is covered by law.

Alberta's Personal Information Protection Act applies to private businesses. The provincial privacy commissioner states it plainly: private sector organizations must have your consent to collect, use or disclose your personal information ¹¹. Some situations are authorized without consent, but a chat widget collecting customer details is not the place to gamble on that.

The federal privacy commissioner's principles for generative AI say organizations must tell people what personal information is collected, how, when and why it is collected, used or disclosed, at any stage of the system's life ¹⁰. The same guidance says outputs that could significantly affect someone should be clearly marked as coming from a generative AI tool. In practice: call the widget an assistant, not a staff member with a first name, and say at the top of the chat that answers come from software.

Then ask the vendor two questions before you pay. Where are the transcripts stored, and how long are they kept? Add one sentence to your privacy notice saying the chat is recorded, why, and who sees it.

When it is worth putting one on your site

It is worth it when the same few questions arrive every day, when your site already gets visitors who type instead of phoning, and when the answers live in writing on pages you keep current. Under those conditions an entry plan is cheaper than the evenings you spend answering the same email.

It is not worth it when your site gets little traffic, when every enquiry needs a price that depends on a site visit, or when your real problem is the phone ringing while your hands are full. A chatbot does not fix a phone problem.

If you go ahead, start on the smallest paid plan, limit it to your own pages, and read every transcript for the first week. Ready-made tools cover most small businesses, and the list above is a reasonable place to start. Custom work only earns its cost when the chatbot has to read or change something inside your own booking, inventory or job system, which a basic off-the-shelf widget cannot reach.