Cost formula
API monthly = conversations/day × days × replies/conversation × cost(input+output tokens); Escalations = conversations × (1 − resolution rate); Total = API monthly + escalations × human handoff $; Blended = Total ÷ monthly conversations
Calculator
AI customer support chatbot cost calculator
Enter conversations per day, replies per ticket, token sizes, and bot resolution rate to see monthly API cost, human handoff cost, and blended cost per conversation.
Support chatbot
Blended monthly support cost
$33,630.60/ month
$2.80 / conversation · GPT-4o mini · 65% bot resolution
API$30.60
Human handoffs$33,600.00
API / month$30.60
Human handoffs$33,600.00
Cost / conversation$2.80
vs all-human$62,369.40
Inputs
Chatbot volume & containment
Estimate LLM spend plus residual human cost for escalated tickets.
Workload preset
Volume
Tokens per reply
Containment & human cost
Insights
Where support spend goes
API cost is usually small next to escalations—containment rate matters most.
Conversations / month12,000
Bot replies / month60,000
Resolved by bot7,800
Escalated to human4,200
API / conversation$0.00255
Blended / conversation$2.80
Human handoff cost is your planning figure (salary + tooling + overhead), not an API price. Raising resolution rate usually saves more than switching to a cheaper model.
Models AI chatbot API spend plus optional human escalation cost for support volumes—not CRM, telephony, or seat licenses. Updated 2026-07-31. Approximate static list prices for planning only. Always verify against each provider’s official pricing page before production budgeting.
Guide
How to get value from this calculator
Estimate what an AI customer-support chatbot really costs: LLM replies, optional RAG context, bot containment rate, and residual human handoff cost. Most teams discover API spend is small next to escalations—so resolution rate and handoff cost dominate the blended cost per conversation.
Why it matters
Searchers asking “how much does an AI chatbot cost?” usually need unit economics for support, not a raw token table. This calculator turns tickets, containment, and model choice into a monthly bill and a cost-per-conversation figure finance and CX teams can share.
How to use it
- Pick a support preset (SMB, SaaS, or enterprise) or enter your own volume.
- Set conversations per day and active days per month.
- Enter average bot replies per conversation and tokens per reply.
- Add knowledge-base / RAG context tokens injected per conversation if you use retrieval.
- Choose the LLM model and optional cache or batch pricing.
- Set bot resolution rate and your fully loaded human handoff cost per escalated ticket.
- Review monthly API vs human spend, blended cost per conversation, and savings vs all-human support.
Planning tips
- Improving resolution rate by 10 points often beats switching to a slightly cheaper model.
- Cache stable system prompts and FAQs—support bots repeat the same prefix constantly.
- Measure tokens from production traces; support tickets with pasted logs inflate input fast.
- Human handoff cost should include salary, benefits, tooling, and average handle time—not wage alone.
- If RAG context is large, compare retrieval top-K sizes; context often dwarfs the user message.
- Batch pricing helps offline summarization, not live chat replies.
Frequently asked questions
How much does an AI support chatbot cost per month?
It depends on conversation volume, tokens per reply, model rates, and how often humans still take over. Enter your numbers here to get API + handoff totals rather than a single generic quote.
Is API cost or human cost usually larger?
For most support volumes, human escalations dominate. That is why containment rate is the main lever once you have a capable model.
Does this include Zendesk, Intercom, or phone costs?
No. It models LLM API spend and an optional per-ticket human handoff cost. Add CRM and telephony separately.
Are model prices official?
CentsPerToken uses approximate list prices for planning. Confirm current provider rates before production budgeting.