$5,500
Support savings / mo
110
Agent hours freed / mo
$960
Extra lead value / mo
$77,052
Estimated net annual return · $6,421/mo · 16,464% ROI
Free plan, no credit card. Live on your site in about 10 minutes.
How this chatbot cost calculator works
The model is deliberately transparent. Your support savings are the conversations the bot deflects (monthly conversations × deflection rate) multiplied by your fully-loaded cost per conversation. Agent hours freed assume roughly six minutes of human handling per deflected conversation. Extra lead value credits an always-on bot with capturing a conservative share of leads that a business-hours-only form would miss. Net return subtracts your chatbot plan cost. Nothing here uses inflated benchmarks - change any input and the math updates live. For the reasoning behind each lever, see our customer support chatbot guide and lead generation chatbot playbook.
What a chatbot actually costs in 2026
The number above only means something against real prices, and published chatbot pricing spans two orders of magnitude. At the bottom, permanent free tiers cover a live widget on a small site - ours is 600 conversations a month, Tawk.to is unlimited but has no AI, and BotPenguin allows 1,000 messages. Entry paid plans cluster between $19 and $45 a month for a workspace. Above that, per-seat platforms change the shape of the bill entirely: Intercom runs $29 to $132 per person per month and then charges roughly $0.99 for each conversation its AI resolves, so the meter grows with your ticket volume rather than your headcount.
That distinction matters more than the headline price. A five-person team resolving a thousand AI conversations a month pays a few hundred dollars in seats and close to a thousand in resolution fees - the AI is the larger half of the invoice, and it scales with success. A flat workspace price does the opposite. Which shape suits you depends on whether your volume or your headcount is growing faster, and that is worth deciding before you compare any two numbers. The free chatbot comparison lists every current free tier with its real limits, and our pricing shows where the paid steps land.
Where these estimates go wrong
Every calculator on this subject, including this one, rests on assumptions you should check rather than inherit. Four are worth stating plainly.
Deflection rate is the input people get most wrong. It is not the share of conversations the bot handles - it is the share it handles that would otherwise have reached a human. Bots frequently answer people who would have bounced instead of emailing, which is genuinely useful but is not a saving. If you have not run a holdout test, treat any figure above 40% as optimistic.
Cost per conversation has to be fully loaded. An agent's salary is usually a little over half the true cost once tooling, management, recruitment and unproductive time are counted. Using base salary alone understates savings; using an inflated blended rate overstates them.
Deflected volume rarely converts to headcount. Removing 30% of tickets does not remove 30% of a person unless the reduction crosses a whole role. In most teams the first year of savings shows up as absorbed growth and shorter queues rather than a smaller payroll - real, but not the same thing as cash.
The build cost is not zero. The plan price is the visible number; someone still has to write the answers, wire the handoff and maintain them. Budget a few days of setup and an hour a week for the first quarter. Our study of 1,247 businesses found implementation quality explained 41% of the variance in outcomes - more than platform choice, response speed or anything else measured.
Measuring the real number instead of estimating it
An estimate is for deciding whether to try. Once the bot is live, replace it with a measurement: show the widget to half your visitors on one page and hide it from the other half, then compare contacts-to-a-human across the two groups as a whole - not chatters against non-chatters, which measures intent rather than the software. Two full sales cycles is the usual minimum. The ticket deflection calculator turns the result into money, and the free plan exists so you can run that test before paying anyone - it is a plan rather than a trial, so nothing switches off mid-experiment.
Explore more calculators
Want a narrower view? Try the support ticket reduction, lead generation ROI, and customer service cost savings calculators, or browse the full calculators hub. New to the concept? Start with what is a chatbot or compare AI agents vs chatbots.
Chatbot cost calculator FAQ
How is chatbot ROI calculated?
Chatbot ROI compares what you save against what the chatbot costs. The savings come from three places: support tickets the bot resolves without an agent (deflection), leads it captures and qualifies outside business hours, and agent hours freed for higher-value work. This calculator estimates the first two from your own numbers - monthly conversations, cost per handled conversation, deflection rate, and lead value - then subtracts the plan cost to show net monthly and annual return.
What is a realistic chatbot deflection rate?
Deflection rate is the share of conversations the bot resolves with no human involvement. Teams new to automation typically start at 40-50%; teams with a well-maintained knowledge base reach 60-75%. The slider defaults to a conservative 55%. Deflection is highest for repetitive, documented questions (order status, pricing, resets) and lowest for judgment-heavy cases, which should always route to a human.
Does this calculator require an email or signup?
No. Every calculation runs entirely in your browser and nothing is sent anywhere or stored. Adjust the inputs, read the result, and screenshot it if useful. When you are ready to make the numbers real, you can start a free Conferbot account, but the calculator itself is free and ungated.
How quickly do chatbots pay for themselves?
For most SMBs the break-even point is measured in days, not months, because a single deflected agent-hour usually costs more than a month of a chatbot plan. The exact payback depends on your conversation volume and cost per contact - enter them above to see your own number rather than an industry average.
What should I include in cost per conversation?
Use your fully-loaded cost: agent hourly wage times average handle time, plus a 25-35% overhead factor for benefits, software, and management. If you are unsure, a common range for a fully-loaded human-handled support conversation is $3-$8. The calculator lets you set this directly so the output reflects your real economics, not a generic assumption.
Can I trust these numbers for a business case?
The calculator uses transparent arithmetic on inputs you control - there are no hidden multipliers or inflated benchmarks. Treat it as a directional model to build a business case, then validate against your live data after deployment. Conferbot's built-in analytics track deflection, resolution, and lead capture automatically once your bot is running.
No credit card required. 8 channels, free forever plan.