What an AI chatbot costs a small business, and what decides it.

The short answer

There is no single price for an AI chatbot, because vendors bill different units. Two businesses on the same tool can pay very different amounts, and the same business can pay very different amounts on two tools. What decides your bill:

• The billing unit: seats, conversations, outcomes, credits or a setup fee.
• Your volume: how many chats arrive in a month, and in your busiest month.
• What the AI settles on its own, since some tools charge for exactly that.
• The extras: channels such as WhatsApp, access for other software, removing the tool's branding.
• Your team's time to write the answers, test them and read conversations.

So before comparing prices, write down two numbers from last month: how many enquiries arrived by chat, email and your website form, and how many were questions your pages could have answered.

The ways you can pay

Small businesses meet five billing models. The pricing pages below were checked for this guide in October 2026. Vendors change prices and billing units, so look up today's terms before you sign.

• Free chat with paid extras. tawk.to offers live chat free, with paid add-ons for removing its branding and for AI Assist, which has a free tier for low volumes. Cheap, and someone still answers the chats.
• A monthly plan with a quota. Tidio sells plans with a monthly allowance of AI conversations, and Crisp charges a flat fee per workspace with AI credits included in each plan. Predictable until you pass the quota.
• Per seat plus per outcome. Intercom charges per teammate seat and bills its AI agent, Fin, per outcome. Zendesk charges per agent seat and bills its AI agent by automated resolution, with an allowance per agent.
• Credits on a larger platform. HubSpot's customer agent needs a Professional or Enterprise subscription and runs on HubSpot Credits, charged per resolved conversation.
• A custom build. A studio or developer charges for the setup, then a monthly plan or an hourly rate for hosting, changes and upkeep.

The tools themselves are compared on features in website chatbot tools compared. This guide is about what you end up paying.

Read what each tool counts

The definition of the billing unit matters more than the price per unit. These differ in ways that change the bill:

• Tidio counts a Lyro conversation once it has at least one AI reply, and it counts once however many replies follow. A visitor who gives up after the first answer still counts.
• Intercom's Fin pricing page counts an outcome when no further help is requested after Fin's last answer, or when Fin completes a procedure you set up, such as qualifying a lead or a set handover. A conversation simply passed to your team without an outcome is not charged.
• Zendesk's pricing page says requests escalated to a person do not count as automated resolutions.
• HubSpot counts a resolution when its agent helps the customer and no person takes over within a set time, and also when it qualifies a lead.

So a handover can cost nothing on one tool and count as a billable outcome on another, depending on how it happens. Ask each vendor, in writing, which of your usual conversations would be charged: a price question answered, a booking request taken, an urgent case passed to reception.

A year worked through

Take a physiotherapy clinic with two receptionists. Say its website gets 300 chats a month, rising to 400 in January. Say 180 of a normal month's chats end with the visitor's question answered, 70 with a booking request taken and 50 with a handover to reception. Here is what each model bills over the year. Put today's prices from each vendor's page into the gaps.

• Monthly plan with a quota: a plan whose AI allowance covers 400 conversations, because January sets the size, times 12 months. Every chat the AI joins counts, so all 300 or 400 do. Add live chat seats if reception answers there too.
• Per seat plus per outcome: 2 seats times 12 months, plus the outcomes. If answered questions and completed booking procedures count, that is about 250 a month, or roughly 3,000 a year, times the fee per outcome. Add any channel charges.
• Credits on a platform: the Professional subscription the agent needs, times 12, plus credits for the resolved conversations beyond those included.
• Custom build: the setup fee once, plus the monthly plan times 12. In year two, only the plan.

Then add the same line to every column: the hours your team spends writing answers, testing and reading conversations, unless someone else does that work for you.

Now change one number. A solo bookkeeper gets about 20 chats a month, most of them in January, so around 240 in the year. On a per-outcome tool or a free plan, that bill stays small. A custom setup fee is hard to justify on that volume alone, unless the chatbot does a job no tool can, such as collecting the documents each client still owes for their year-end accounts.

Work out year two as well. First-year discounts end, quotas get outgrown, and a setup fee is paid only once. The cheapest model in year one is often not the cheapest by the end of year two.

Costs that are not on the pricing page

Most surprises come from things outside the headline plan:

• Seats added for people who only need to read conversations now and then.
• Channels billed by use. Intercom's pricing page bills WhatsApp, text messages and phone by consumption.
• A higher plan for access by other software. Tidio lists API access on its higher plans, and many tools keep custom connections for their upper tiers.
• Removing the tool's branding from the chat window.
• Minimum commitments. Fin used with another helpdesk has a monthly minimum of outcomes.
• Yearly billing that is cheaper per month but paid upfront and hard to leave mid-year.
• The quota you pass in your busiest month, and the plan you are moved to because of it.
• Setup work for a connection to your booking software or CRM, which no plan includes.

Read the terms for each one before you compare totals.

The cost in your team's time

Every chatbot, bought or built, needs the same preparation, and someone pays for it in hours:

• Collecting thirty real questions from your inbox, forms and phone notes.
• Writing or fixing the answers your pages do not give.
• Writing the rules: what it must never say and when it hands over.
• Testing it with real and awkward questions before launch.
• Reading conversations every few days at first, then every week or two, and fixing answers at their source.
• Picking up handovers, which stays a person's job on every tool.

With an off-the-shelf tool, your team does all of this. With a custom build, the studio does most of it and your team approves the answers and tries it before launch. That difference is a real part of what a setup fee pays for, so count it when comparing.

The order of that work is in how to add an AI chatbot to your website.

What decides the price of a custom build

A custom chatbot is priced by the work, not by your volume. The main drivers are how many jobs it has, where requests have to land, how ready your information is, how many handover routes it needs, how many languages it answers in and how strict your trade's rules are. Our AI chatbots page explains each one.

Two quotes for a custom chatbot can differ for the same reasons website quotes do, so ask each one to list:

• The jobs it covers, and what it must never do.
• Every connection, and whether the vendor has checked that your software's API allows it.
• Who writes and approves the answers.
• How it is tested before launch, and whether your team tries it first.
• What the monthly fee covers: hosting, changes, reading conversations, fixing answers.
• What you keep if you stop paying, including every conversation and your answers document.

We charge a one-time setup and then a monthly plan that keeps the chatbot running and tuned. Plans run month to month and stop with 30 days' notice. The figures are on the prices page.

When the cheaper option is the right one

Spending less is often the right call, and you can set up a cheap tool yourself without paying anyone:

• You get few chats. At low volume, a per-outcome or free-tier tool costs little, and a setup fee takes a long time to earn back.
• Your questions are simple and already answered on your pages, such as hours, prices and parking.
• Handovers can go to one inbox during opening hours.
• You already pay for a helpdesk or HubSpot plan that includes an AI agent.
• You are not sure yet whether customers will use a chat at all. A free plan for a month tells you.

Sometimes the cheapest answer is no chatbot: a clear page of answers next to the booking button and a short form with an honest reply time. Chatbot, live chat or contact form helps you decide.

When paying more makes sense

A higher bill, or a setup fee, earns its keep when one of these is true:

• Your volume is high enough that per-outcome or per-conversation fees add up faster than a flat plan.
• Requests have to land in your booking software, practice software or CRM, and no off-the-shelf tool connects to it.
• Your trade needs tested limits, such as a clinic that must never comment on symptoms.
• Nobody on your team has the hours to write the answers, test them and read conversations.
• Enquiries arrive in the evening and at weekends, when a missed one goes to a competitor.

For a booking chatbot that takes requests after closing time, the comparison is with the bookings you lose today, not with the cheapest plan.

How to compare plans and quotes

Put every option through the same test:

• Run the same thirty real questions through each trial or demo, including a complaint and an urgent case.
• Ask how each of your common conversations would be billed, in writing.
• Price your busiest month, not your average one.
• Price year one and year two, including every extra you need.
• Add your team's hours to each column.
• Check the exit: notice period, data export and who owns the answers document.

The option with the lowest monthly figure is rarely the cheapest once the table is full. Keep the table: at renewal, put the year's real numbers into it and check whether the plan you are on still fits.

Check that it pays for itself

Three months after launch, compare the bill with what the chatbot did:

• Chats it answered that would otherwise have reached your phone or inbox.
• Booking requests and enquiries it took outside opening hours.
• How many of those became paying customers, from your own booking or sales records.
• Handovers that arrived complete, so nobody had to ask the customer again.

Read a sample of conversations too. A chat that ended in a handover can still have saved a phone call, and a chat the tool billed as resolved can be a visitor who gave up. If the numbers do not justify the bill, change the plan, cut the extras or switch the chatbot off. A tool nobody uses is the most expensive kind.