Business chatbot pricing: compare the full monthly cost

Three pricing models need three different counts

The total cost matters. To compare chatbot prices for your business, count the staff who will manage it, the enquiries customers send and the replies needed in each conversation. A monthly subscription alone tells you little about the final bill.

There are three broad models: pay for each billable outcome, pay for staff seats plus usage, or buy a package with a limited allowance. A seat is a staff login. Credits are the provider’s usage units, and do not necessarily represent complete customer conversations.

Our recommendation is to compare quotes for the same job. A first website chatbot might answer questions about services, delivery conditions and opening hours. Keep orders and binding promises with your team initially. The calculation below separates software costs from setup and maintenance time. For workflows beyond the website, see our companion guide to the annual cost of an AI agent.

Intercom adds usage charges to the seat price

The seat is only the starting point. According to Intercom’s pricing page, Essential costs USD 29 per seat per month when billed annually. Monthly billing costs USD 39.

For two seats and 240 billable support outcomes, our example comes to 2 × 39 + 240 × 0.99 = USD 315.60 a month, before extras and any applicable taxes. The seat price has yet to answer a customer.

Read Fin’s detailed billing rules: a resolution or a configured Procedure successfully ending in a handoff costs USD 0.99, while a qualified sales lead costs USD 9.99. Routing explicitly marked as self-serve uses the lower rate. A conversation may count as resolved when no further help is requested after the answer. There is at most one outcome charge per conversation. These are billing rules, not evidence of time saved.

With an existing helpdesk, the software used to manage customer enquiries, Fin carries no Intercom seat charge according to Intercom’s FAQ, but a minimum commitment applies. Your existing software may still have its own bill.

700 credits cover 175 conversations in our example

A package needs a usage calculation. With monthly billing, Chatbase Hobby costs USD 40 and includes 700 message credits and two staff accounts. Standard costs USD 150 for 4,000 credits and three accounts. These are capped packages, not unlimited plans.

The model documentation lists Auto at one credit per message; other models may use more credits. Assuming four AI replies per conversation, 700 credits cover 175 conversations. At 600 conversations, that assumption produces a total of 2,400 credits.

Write the expected conversation length alongside the package price. Eight replies instead of four doubles the requirement. Treat the handoff to a staff member as a separate requirement to check before choosing a plan on credits alone. The quoted provider prices exclude taxes; see the billing rules from Intercom and Chatbase.

Our monthly budget totals EUR 255

Maintenance time belongs in the budget. For a provider-independent example, we assume EUR 100 in monthly software costs, EUR 600 for initial setup and an internal hourly rate of EUR 35. These are assumptions, not a quote from Thümmler AI or either provider.

We spread setup over twelve months for the comparison. Each month also includes two hours to update answers and one hour for spot checks and corrections. That gives us this completed monthly budget:

• Software including expected usage: EUR 100
• Setup: EUR 600 ÷ 12 months = EUR 50
• Updating answers: 2 hours × EUR 35 = EUR 70
• Spot checks and corrections: 1 hour × EUR 35 = EUR 35
• Total cost for comparison: 100 + 50 + 70 + 35 = EUR 255

This example breaks even at 274 enquiries

Time saved determines the result. Assume 600 website enquiries a month. The chatbot handles 40 percent without rework, or 240 enquiries, saving four minutes each. That is 960 minutes or 16 hours, valued at EUR 35 an hour: EUR 560.

After the EUR 255 total cost, the calculated monthly benefit is EUR 305. This values time freed up; it does not automatically reduce payroll. If you cannot use those hours elsewhere, do not treat them as guaranteed cash savings.

Use this formula: minimum enquiries = total monthly cost ÷ (share handled × minutes saved ÷ 60 × hourly rate). With our assumptions: 255 ÷ (0.40 × 4 ÷ 60 × 35) = 273.21. Round up to 274 enquiries. This assumes the software budget stays fixed across the volumes compared; add any extra usage charges before applying the calculation.

At only 100 enquiries, the time saved is worth EUR 93.33. That leaves a EUR 161.67 shortfall against costs. In that case, we would start by improving the existing answers and contact form.

Six lines make supplier quotes comparable

A quote needs a defined workload. Copy these six lines into your enquiry and ask each provider to price the same monthly case. You can then see whether the advertised entry price fits your usage.

• 1. Task and volume: website support, 600 monthly conversations, an average of four AI replies, two staff accounts.
• 2. Billing unit: what counts as a chargeable conversation, outcome or message? Please include handoffs and abandoned conversations.
• 3. Base price: monthly payment, included allowance, currency and taxes shown separately.
• 4. Extra usage: price at twice the volume, automatic top-ups and a fixed spending limit.
• 5. Setup: itemise website installation, importing existing answers and handing conversations to staff.
• 6. Ongoing work: who updates content, checks mistakes and handles outages? State monthly effort and the cancellation notice period.

The test needs an answer sheet and a stop rule

A small test limits the cost. We would begin with 20 frequent, anonymised questions and write down the correct answers beforehand. Add five cases where the bot must not make a promise: an unknown price, a special discount, an uncertain delivery date, a complaint and a question with no supporting document.

For each case, record the answer, the billed usage and any rework. A correct handoff is a good result, but it does not remove all human handling time. If the bot invents a price or makes an unauthorised promise, stop the launch and correct the instructions first.

Our starting recommendation is a narrow set of functions, one named owner and a fixed monthly spending limit. Routing by postcode or enquiry type may need only a rule. Our guide to choosing between AI and conventional automation helps separate those cases before you buy.

Questions to settle before the first month

The first month needs a clear goal. Answer these three questions before ordering.

Is annual billing worth it? We would commit for longer only after a successful month-long test. A lower monthly price is little help if the answers or handoffs do not work for you. Compare the total twelve-month payment as well.

Does a small business need to write code? Not for the initial price comparison. First ask providers to show how they answer the same question set and hand it over to your team. Connections to internal systems belong on a separate line in the quote.

Which metric matters after launch? Record the minutes spent on setup, maintenance and rework against the handling time genuinely removed. Add software costs and any extra usage. Our guide to AI costs per transaction helps with the ongoing calculation.

Next step: put your monthly volume into the six quote-request lines and calculate the break-even point. If you would like help, we can discuss your website chatbot in a free first call.