How much does an AI chatbot for a website cost in 2026, and when does it need a human?

What does each kind of website chatbot cost to build?

Quotes land in four bands, set less by the vendor than by what the bot may do. These are ranges vendors publish themselves: asking prices, not audited averages.

Per RaftLabs, bots built on a language model cost four to eight times more than scripted ones: prompts, retrieval and output checks all need building and testing.

Why does a VITON¹³ chatbot start so far below those ranges?

Those bands price custom software: a bespoke interface, a retrieval pipeline, integrations, weeks of a team's time. Our launch is narrower: an existing chatbot platform picked in the written scope, one channel, a knowledge base you sign off. AI drafts answers from your documents; a specialist reads each one before launch.

What does a chatbot cost to run each month?

RaftLabs puts running a chatbot at $400–$6,000 a month, with model API fees the largest, least predictable line. A small site's bill has four lines, each paid to a different provider.

How a provider charges matters as much as how much. On list prices, 1,000 conversations of Anthropic's example length use about $3.70 of Haiku tokens; 1,000 Fin outcomes cost $990. The platform fee buys an inbox, seats and reports a bare model lacks, so compare whole bills.

Chatbot, live chat or both: which costs less per conversation?

A bot is cheap only if the conversation ends well. In a Gartner survey of 3,566 customers (February–March 2026), 87% called access to a human agent essential when a company uses generative AI for service, and only 27% would try a chatbot again after a bad experience. Their complaints: the bot misread the problem, gave generic text or made a person harder to reach.

For most small sites, the third setup is the one worth buying: the question is which chats reach a person, and how fast.

Which conversations must go to a person?

Write the handoff rule before anyone builds the bot. These triggers belong in nearly every rule:

• The visitor asks for a person. Hand over the first time; making someone ask twice loses them.
• Money in dispute: refunds, cancellations, chargebacks, a complaint about an order.
• Anything legal, medical or financial, and any decision that changes what a customer pays or receives.
• No approved answer: the question falls outside the knowledge base, or the bot has already missed once.
• A bigger deal than usual: a quote above a threshold you set, a group booking, a company enquiry.
• Anger, distress or anything touching safety.

The handoff carries the transcript, the contact and the reason, so nobody makes the visitor start over; out of hours, the bot says when a person will reply. RaftLabs reckons proper escalation adds 20–30% to development time, which is why cheap quotes drop it. Ask where those hours sit in yours.

What must the bot tell visitors, and what does the law ask?

In the EU, Article 50(1) of the AI Act requires systems that interact directly with people to let them know they are dealing with AI, unless that is obvious; Article 50(5) wants the notice clear and distinguishable by the first interaction. The AI Act Service Desk dates these rules from 2 August 2026.

• Disclosure: the opening message says it is an automated assistant and how to reach a person, on every channel, wherever the visitor is.
• Personal data: link your privacy notice before the bot asks for a name or number, and agree how long transcripts are kept.
• Scope: answers come only from approved content; beyond it, the bot says so and offers a person.
• Promises: no discounts, delivery dates or refunds your policy does not state. Visitors read the bot's reply as your company's.
• Training: where possible, stop the platform training its models on your conversations.

What should a chatbot quote spell out before you sign?

Two quotes for “a chatbot” can differ tenfold because they describe different jobs. Any line a vendor will not put in writing is a cost you meet later.

• Knowledge: which documents, how many, who keeps them current.
• Channels, languages and flows, each named.
• Captured fields and where they land.
• Handoff: triggers, channel, hours, the out-of-hours message.
• Testing: how many scripted conversations, including attempts to drag the bot off topic.
• Running fees by provider, whose name the accounts are in, and where transcripts are kept and for how long.
• After launch: the fix period, the first report, what counts as new work.

When is an AI chatbot not worth buying yet?

• Few chats arrive. At a handful a week, a WhatsApp button or a contact form costs less and loses nothing.
• Your answers are not written down. Write the FAQ first; a bot cannot answer from nothing.
• Prices or stock change daily and live in someone's head, so the bot would quote stale figures.
• The questions need professional judgment. We do not build bots that give medical, legal or financial advice.
• Nobody can take the handoff. A bot that offers a person and never produces one is worse than no bot.
• You want a promise of more leads. We report what the bot did; nobody can honestly promise what it will earn.

AI-assisted or human-led: what changes for a chatbot?

Same package, same window of 5–8 working days; what differs is the specialist time spent on the conversation itself.