---
title: "AI Chatbot Cost for Business: The Real Monthly Bill"
seoTitle: "AI Chatbot Cost for Business: The Real Monthly Bill"
description: "Compare chatbot billing units and three monthly cost scenarios, including staff time, wrong answers, and the resolution rate needed to break even."
datePublished: "2026-10-07T19:25:00Z"
dateModified: "2026-11-01T19:12:00Z"
category: "ai"
imageAlt: "A customer service worker studies a long receipt beside a chat widget at her desk."
tags: ["ai-chatbot", "chatbot-pricing", "customer-service", "ai-cost", "total-cost-of-ownership"]
faq: true
headQuery: "ai chatbot cost for business"
featuredImageFile: "/blog/art/en/chatbot-costs-more-hero.0df14bae.webp"
---
AI chatbot cost for business is more than a monthly plan or a per-resolution fee. In the three hypothetical customer-service scenarios here, the platform fee is about 21% of the monthly total, while staff handling escalated conversations account for 64% to 71%. Those shares and the savings and break-even rates that follow are our arithmetic from the stated assumptions.
The difference is the work left on your side of the bill. A platform can charge for the bot's answer while your staff still review transcripts, maintain the knowledge base and handle inquiries the bot cannot close.
Prices were read on 1 November 2026, in US dollars. Check the vendor's page before relying on them.
## Customer service chatbot pricing depends on what gets counted
Customer service chatbot pricing can charge for an outcome, a session, a conversation or message credits. Those units do not measure the same thing, so a lower sticker price does not settle which contract costs less.
| Vendor | Billing unit | Price | What counts |
|---|---|---|---|
| [Intercom Fin](https://www.intercom.com/pricing) | Outcome | $0.99 per outcome | An outcome is counted when “A customer confirms their issue is resolved”, “They don't ask for more help after Fin responds”, or “Fin completes a workflow (Procedure), including handoffs”. Charged at most once per conversation. |
| [Zendesk AI agents](https://support.zendesk.com/hc/en-us/articles/5352026794010) | Automated resolution | Dollar price unavailable from the vendor price page; on the platform in place before 18 May 2026, committed usage of 100 or more resolutions bought ahead costs less per resolution than pay-as-you-go | An issue resolved without human help and verified by an LLM. On the pre-18 May 2026 platform, monthly allotments per agent are 5 for Team, 10 for Growth and Professional, and 15 for Enterprise. Accounts remain on that platform until they move to the resolution tiers introduced on 18 May 2026. |
| [Freshworks Freddy AI Agent](https://crmsupport.freshworks.com/support/solutions/articles/50000004664-ai-agent-and-chatbot-sessions-faqs) | Session | $49 per 100 sessions | All interactions with an end user within a 24-hour window count as one session. |
| [Tidio Lyro](https://www.tidio.com/pricing/) | Conversation | The pricing calculator lists $39 per month for 50 Lyro conversations, up to $700 per month for 1,000, on monthly billing. The “Starts at $32.50/mo” headline is the annual-billing price. Prices read 1 November 2026. | A customer interaction with at least one Lyro reply counts, even if it receives multiple replies. |
| [Salesforce Agentforce](https://www.salesforce.com/agentforce/pricing/) | Conversation | $2 per conversation | The published conversation pricing charges per conversation. |
| [Chatbase](https://www.chatbase.co/pricing) | Message credit | $40 per month for 700 credits on Hobby; other plans have different allowances | Each model request consumes credits according to the selected model. Actions can trigger multiple requests. |
A **conversation** here means one customer inquiry through the widget. A **bot-closed conversation** means one the vendor bills as resolved; that billing label does not prove the answer was correct.
Intercom also lists Essential at $29 per seat per month and shows a $19 new-customer price. The platform fee can conceal the cost of model changes within its pricing; the separate [model running-cost sheet](/blog/automation-running-cost) covers that side. For a self-built support chatbot, the [AI automation cost guide](/guides/ai-automation/ai-automation-cost-for-smbs) prices the model, platform and review line by line.
## What does each billing unit cost per bot-closed conversation?
A billing unit's cost per bot-closed conversation depends on the resolution rate when the vendor also charges for attempts that reach a person. The table figures are our arithmetic: each fee is divided by the resolution rate to compare those units with a fee charged for each outcome.
| AI billing unit | At 30% resolution | At 50% resolution | At 70% resolution |
|---|---:|---:|---:|
| $0.99 per outcome | $0.99 per bot-closed conversation | $0.99 per bot-closed conversation | $0.99 per bot-closed conversation |
| $0.49 per 24-hour session | $1.63 per bot-closed conversation | $0.98 per bot-closed conversation | $0.70 per bot-closed conversation |
| $0.70 per conversation with an AI reply | $2.33 per bot-closed conversation | $1.40 per bot-closed conversation | $1.00 per bot-closed conversation |
| $2.00 per conversation | $6.67 per bot-closed conversation | $4.00 per bot-closed conversation | $2.86 per bot-closed conversation |
The table assumes one billed session or conversation per inquiry and ignores seats, minimum commitments and other operating costs. The $0.49 per session is our arithmetic from Freshworks' $49 per pack of 100 sessions divided by 100. The $0.70 per conversation is our arithmetic from Tidio's listed monthly prices divided by conversations at the 300 ($210), 500 ($350), 750 ($525) and 1,000 ($700) tiers. Actual session boundaries can make a vendor's count differ from your inquiry count.
Our arithmetic puts the crossover between $0.49 per session and $0.99 per outcome at 49.5% resolution: $0.49 divided by $0.99. Above 49.5%, the per-session price costs less per bot-closed conversation; below 49.5%, the per-outcome price costs less. At 30% resolution, a company with 1,000 conversations would pay $297 per month for the $0.99 outcomes and $490 per month for the $0.49 sessions, assuming the counts match the table.
Message credits need a different calculation because one conversation can consume a variable number of credits. Count the credits used by 20 representative test conversations, including any Actions, then divide the credit cost by the number of bot-closed conversations.
## Three chatbot cost scenarios include the work after the bot replies
The total cost of ownership of a customer-service chatbot includes the platform bill and the staff work around it. The following scenarios use the same assumptions at three inquiry volumes; they are examples, not forecasts of any vendor's performance.
**Shared assumptions:**
- Intercom Fin bills $0.99 per outcome, with Essential seats at the $29 per seat per month list price. Scenario A uses one seat, B uses two and C uses five.
- The bot closes 50% of conversations, and the other 50% escalate to a person.
- An escalated conversation takes seven staff minutes because the customer has to restate the problem after the bot fails. The same inquiry handled entirely by a person takes six minutes.
- A loaded staff hour costs $30.76. That is our arithmetic: the [BLS median wage for customer service representatives](https://www.bls.gov/news.release/ocwage.t01.htm) of $21.53 per hour divided by 0.70, the private-industry wage share of compensation in June 2026.
- A person reviews 5% of bot-closed transcripts for two minutes each. Knowledge-base upkeep takes two, four or eight hours per month, respectively.
- Setup takes 10, 20 or 40 staff hours, respectively, and its cost is spread over 12 months.
- The wrong-answer reserve assumes 0.5% of bot-closed conversations contain a statement the company must honor or fix, at an average cost of $40 per wrong answer. Both inputs are hypothetical.
At the assumed loaded rate, seven minutes costs about $3.59 per escalation and six minutes costs about $3.08 per all-human conversation. The table calculates with unrounded time costs and rounds the displayed amounts to cents.
| Monthly line | A: 300 conversations | B: 1,000 conversations | C: 5,000 conversations |
|---|---:|---:|---:|
| Fin outcomes, 50% at $0.99 each | $148.50 | $495.00 | $2,475.00 |
| Seats, at $29 each | $29.00 (1) | $58.00 (2) | $145.00 (5) |
| Escalations, 50% at 7 minutes each | $538.30 | $1,794.33 | $8,971.67 |
| Transcript QA, 5% of bot-closed at 2 minutes each | $7.69 | $25.63 | $128.17 |
| Knowledge-base upkeep | $61.52 (2 hours) | $123.04 (4 hours) | $246.08 (8 hours) |
| Setup cost spread over 12 months | $25.63 (10 hours) | $51.27 (20 hours) | $102.53 (40 hours) |
| Wrong-answer reserve | $30.00 | $100.00 | $500.00 |
| **Total per month** | **$840.64** | **$2,647.27** | **$12,568.45** |
| Cost per conversation | $2.80 | $2.65 | $2.51 |
| Cost per bot-closed conversation | $5.60 | $5.29 | $5.03 |
| Same conversations, all human at 6 minutes each | $922.80 | $3,076.00 | $15,380.00 |
:::figure{src="/blog/art/en/chatbot-costs-more-where-cost-goes.36243690.webp" alt="Chatbot costs led by escalations, with a smaller platform fee, upkeep and a leaking error line" width="1440" height="810"}
Escalations take the largest share in each scenario. The platform accounts for about a fifth, upkeep is smaller, and the wrong-answer line is small but still leaks money.
:::
At the assumed 50% resolution rate, the monthly savings against the same staff handling every conversation are $82.16, $428.73 and $2,811.55. Those figures depend heavily on the seven-minute escalation assumption: if staff must spend longer recovering the context, the savings shrink. The separate [cost sheet on hiring a person](/blog/ai-vs-part-time) addresses a different staffing decision.
The comparison also counts a fractional expected wrong-answer cost. A company cannot expect exactly 0.75 incidents in a month; the $30 monthly reserve in scenario A is an average allowance under the stated assumptions.
## A wrong chatbot answer can become the company's cost
A wrong chatbot answer can create a bill for the company that publishes it. In [Moffatt v. Air Canada](https://decisions.civilresolutionbc.ca/crt/crtd/en/525448/1/document.do), the airline's chatbot told Jake Moffatt that they could apply for a bereavement fare retroactively, while the airline's policy said otherwise.
The British Columbia Civil Resolution Tribunal issued its small-claims decision on 14 February 2024. In paragraph 27, the tribunal rejected the idea that the chatbot was responsible for its own statements and reasoned that Air Canada was responsible for information on its website, whether supplied by a static page or a chatbot. It ordered CA$650.88 in damages, CA$36.14 in pre-judgment interest and CA$125 in tribunal fees, totaling CA$812.02.
The money was small; the principle is the expensive part. The tribunal's small-claims decision does not set binding precedent for courts or other tribunals, even in British Columbia, and is at most persuasive elsewhere; it does not quantify the staff or legal time associated with the dispute.
Other reported cases show how an inaccurate answer can create costs beyond the platform bill. [Ars Technica reported](https://arstechnica.com/ai/2025/04/cursor-ai-support-bot-invents-fake-policy-and-triggers-user-uproar/) that a Cursor support bot invented a one-device subscription policy, prompting complaints and cancellation threats; a co-founder apologized and said the user received a refund.
[The Markup reported](https://themarkup.org/artificial-intelligence/2026/01/30/mamdani-to-kill-the-nyc-ai-chatbot-we-caught-telling-businesses-to-break-the-law) that New York City's MyCity chatbot had given businesses advice contrary to the law. Mayor Mamdani said the chatbot was costing the administration around half a million dollars; the reported figure did not specify a period. The [AI feature UX guide](/guides/ux/ai-feature-ux-for-smbs) covers how wrong answers and dead-end handoffs occur in the interface.
In our reading of [Intercom's published rule](https://www.intercom.com/pricing), an outcome counted when "They don't ask for more help after Fin responds" cannot distinguish a satisfied customer from someone who leaves with a wrong answer. Zendesk uses a different rule: an LLM verifies candidate resolutions before they consume the allowance. Ask each vendor how it counts an unhappy customer who goes silent.
## Free chatbot allowances can expire or stop the widget
A chatbot allowance can disappear before the end of a paid plan, so its exhaustion behavior belongs in the cost calculation. Tidio's initial 50 Lyro conversations are a one-off allowance, not a recurring monthly quota.
Freshworks says its 500 complimentary sessions are also a one-time benefit and are removed when you buy an additional session pack. Its session FAQ says that, on self-service widgets, exhausting the sessions stops the chatbot without handing the conversation to a live agent. Check the remaining allowance and the handoff behavior before treating free volume as part of a monthly budget.
## What resolution rate does a chatbot need to pay for itself?
A chatbot needs a 39%, 32% or 27% resolution rate to break even in scenarios A, B and C, respectively. Those thresholds use the assumptions above and one-percentage-point increments; below each threshold, the chatbot costs more per month than having the same staff handle all the conversations.
The threshold falls as volume rises because the assumed seats, setup and upkeep are spread across more conversations. The extra minute on each escalation moves it in the other direction: staff still handle the unresolved inquiry, and the assumed customer must repeat the problem. If your handoff preserves enough context to avoid that minute, enter your measured time in the calculation.
Iron Goo's [operations team](/services/operations) can take on escalation handling, transcript review and knowledge-base upkeep when you want a team to run those lines. Keep the numbers visible even when someone else does the work: hours and vendor charges still belong in the monthly cost.
:::formula{label="Monthly chatbot total cost of ownership"}
monthly_tco = ai_fee + seats + n * (1 - r) * escalation_minutes / 60 * hourly_cost + qa_hours * hourly_cost + knowledge_base_hours * hourly_cost + setup_hours * hourly_cost / 12 + n * r * wrong_answer_rate * wrong_answer_cost
:::
Set `n` to monthly conversations and `r` to the bot-closed share as a decimal. Enter the actual monthly AI fee under the vendor's billing rule, then compare the total with `n * human_minutes / 60 * hourly_cost` for the same inquiries handled entirely by staff.
Take ten minutes to fill the sheet with your inquiry count, loaded hourly cost and measured handling times. Measure resolution first: have a person read 20 to 50 test conversations and count how many the bot actually closed before using that rate in the calculation.