Bot vs Human Cost Calculator

How the human side is priced

A human-handled conversation costs more than wage × minutes, for two reasons this calculator makes explicit. First, an agent's real cost includes benefits, tools, management, and office overhead: the overhead multiplier, commonly somewhere around 1.25–1.4× base wage, though your finance team's number beats any rule of thumb. Second, occupancy: no agent handles conversations 100% of a paid shift. Training, wrap-up, meetings, and idle gaps between chats mean a typical support team spends 70–80% of paid time actively handling. At 75% occupancy, one hour of handling time costs 1.33 paid hours. Divide the loaded hourly cost by occupancy, multiply by average handle time, and you get the cost of one conversation — the number the «$3,000 per agent» pitch never shows you.

How the bot side is priced — per resolution, not per conversation

The bot's headline unit cost is usually quoted per conversation, which flatters it twice. A conversation the bot merely touched is not a conversation it resolved — and the difference is your containment rate. This calculator divides the bot's full monthly spend (platform fee plus variable AI or messaging cost) by contained conversations only, producing a cost per resolution you can put next to the human number without apologizing. The distinction matters because containment and deflection are not the same thing : a bot that makes people give up and email instead has great «per conversation» economics and terrible actual ones.

Escalations get the same honesty. When the bot fails and a human takes over, you pay the bot's variable cost, a slice of the platform fee, andthe agent's time — typically more of it than a direct conversation, because the customer re-explains from the start, often less happily. The escalation handle-time penalty input models that; even the default +20% shifts the break-even point noticeably, which is exactly why vendor math tends to omit it. How you route those failures is a design decision; see our human handoff and handoff rules entries. Whatever the design, the cost lands on both sides of the ledger.

Fixed fees and the amortization illusion

Most of a bot's cost is a fixed subscription, so its average cost per resolution falls as volume grows (painful at 500 conversations a month, trivial at 20,000) while the human cost per conversation stays flat. The volume table above shows where that crossover happens at your rates. Read it before concluding a platform is «too expensive»: the same subscription that loses money at your current volume may win comfortably at the volume you expect next year. And read it skeptically in the other direction too — falling unit cost from amortization is not evidence the bot got better, just that the denominator grew.

What this calculator deliberately is not

It is not an ROI projection. There is no ramp-up curve, setup cost, or multi-year payback here — that is the job of our chatbot ROI calculator, which models the investment decision. This tool models the steady state: given the rates you have today, is the bot-first setup cheaper this month, and by how much? Use the ROI calculator to decide whether to deploy; use this one to check whether the deployment is actually paying.

It is also not a quality argument. A cost-optimal bot can be a satisfaction disaster — containing conversations cheaply while resolving them badly. The cost verdict above deliberately points you to the quality check: run your survey numbers through the CSAT calculator and read the two results together, alongside your escalation rate and resolution rate. Our chatbot metrics guide covers how the cost and quality numbers fit into one dashboard.

Common mistakes this math exposes

1. Comparing platform fee to salary

The pitch-deck comparison («$99/month vs $36,000/year») compares a fixed fee to a payroll line, ignoring that the bot resolves only some conversations and hands the rest back with interest. The honest units are cost per human-handled conversation vs bot cost per resolution — both computed above, both in dollars per conversation actually dealt with.

2. Ignoring the escalation double-charge

At 60% containment, four in ten bot conversations cost you the bot andthe agent, with a longer handle time than if the customer had reached the agent directly. Below the break-even containment rate shown above, this double-charge fully consumes the bot's savings. If your containment is soft, fixing three failing intents usually moves the economics more than renegotiating the platform fee.

3. Trusting a containment number that measures endings, not resolutions

Platforms often report «resolved by bot» as «conversation ended without handoff» — which includes every customer who gave up. Feed that number in here and the calculator will happily overstate your savings. If containment above 85% seems too good, it usually is; the calculator flags it, and our deflection rate entry explains how to tell resolution from abandonment.

4. Forgetting that per-conversation AI costs scale linearly

The platform fee amortizes; the per-conversation AI cost does not. At high volume, a $0.15-per-conversation LLM cost quietly becomes the dominant bot expense. If your bot is AI-heavy, estimate that input properly with our LLM API cost calculator — and if you run on WhatsApp, remember Meta's per-conversation fees belong in the same input (our WhatsApp API cost calculator prices those by country).

Related Chatbotscape tools and resources

• Chatbot ROI calculator — the multi-year investment case with ramp-up and payback
• Chatbot CSAT calculator — the quality counterweight to this cost math
• Chatbot ROI guide — the full business-case methodology
• Chatbot ROI quick math — the back-of-envelope version of this calculation
• Chatbot metrics guide — cost, containment, escalation, and CSAT as one system
• Intercom review — per-resolution pricing done by a vendor, reviewed hands-on
• Tidio review — SMB-tier pricing and what the AI add-on changes
• SendPulse review — multi-channel pricing on a budget

FAQ

What is a fully-loaded cost, and why not just use the wage?

The wage is what the agent sees; the loaded cost is what you pay. Payroll taxes, benefits, software seats, management time, and office or equipment overhead typically add 25–40% on top of base wage for an in-house team. Using bare wage understates the human side and makes every bot look better than it is — the same distortion, in the other direction, as quoting the bot per conversation instead of per resolution.

Why does occupancy matter?

Because you pay for shifts, not for conversations. An agent at 75% occupancy handling 8-minute conversations costs you the other 25% of their paid time too — spread across the conversations they do handle. Skipping occupancy is the most common way in-house cost-per-contact numbers come out impossibly low.

My savings are positive but the bot's cost per resolution is higher than the human cost. How?

Volume mix. Savings compare the whole bot-first setup against the whole all-human baseline; cost per resolution prices only the contained slice. At low volume a pricey platform can lose on unit cost while the setup still wins overall because escalated and direct conversations dominate the totals — or vice versa. When the two headline numbers disagree, the break-even readout and the cost-detail table show which side of the ledger is doing the work.

Where do setup costs and ramp-up time go?

Not here — deliberately. One-time setup, integration work, and the months before containment reaches target are investment questions, modeled in our ROI calculator with a linear ramp and payback period. This page assumes you are past ramp-up and asks whether the steady state pays.

Does the calculator send my data anywhere?

No. All math runs in your browser — nothing you type is uploaded, stored, or logged. Refresh the page and the numbers are gone.

Can I embed this calculator on my site?

Yes — free. Copy the iframe snippet from the embed section above. The embed strips Chatbotscape navigation and keeps the calculator plus attribution.