Guides → Playground & Guide → Support Deflection ROI - AI Agent vs Human Cost Per Ticket

Support Deflection ROI - AI Agent vs Human Cost Per Ticket

Meet Dana Osei. VP Customer Experience, 20K tickets/month e-commerce. "The vendor deck says 60% deflection. What does that actually save us net - after the conversations our team still has to rescue?"

🔥 She's been burned by automation ROI decks before; she wants a number with the caveats priced in, not hidden.

The story

The raw math is lopsided on purpose. A full support conversation - instructions, history, knowledge-base lookups, six turns of replies - costs a few cents in tokens. A human resolution costs $5-12 fully loaded. That gap is why every vendor leads with deflection.

The honest model adds two things vendors skip. First, the human-touch share: 8-30% of 'deflected' conversations still get reviewed or rescued by a person - we price each at half a ticket. Second, the per-ticket margin: human cost minus (AI conversation cost + expected human-touch cost). If that margin is negative, no deflection rate saves you money.

Dana runs her queue: 20K tickets, 60% deflection, $6 tickets, 8% human touch. The AI all-in cost is a fraction of the avoided human cost, and the per-deflected-ticket margin is positive by dollars, not cents - the automation case holds even with pessimistic review rates.

The output she takes to finance is the net monthly savings and the cost per cleanly-resolved conversation - both computed from live token prices that move when vendor prices move.

🎮 Playground

Support Deflection ROI Playground

Here are the inputs that move the result the most. Play with the sliders and check it out. The number updates live.

What does fronting your support queue with AI cost?

Drag volume and deflection to see the monthly AI cost of the conversations it handles. The full calculator adds ticket cost + the human-touch share for net savings.

Estimated monthly cost

💡Volume and deflection set how many conversations the AI fronts; the per-conversation token cost is cents against a $5-12 human ticket — the honest variable is the human-touch share.

Ready to run the numbers?

Open the full calculator. Pick a model, enter your tokens, see per-call, daily, monthly, and annual cost.

🚀 Open the full calculator →

Top 3 right now

Verified 13 hours ago

About this calculator: Support Deflection ROI - AI Agent vs Human Cost Per Ticket

AI cost per resolved support conversation at live token prices vs the human cost deflection avoids - with the human-in-the-loop share priced in. Net savings, cost per resolved conversation, and the per-ticket break-even margin.

🎛 Inputs you control

Each input shapes the cost. Click an input on the calculator to set it. The explanations below match the live calculator field by field.

Model: The model behind the support agent. Rates are live from the daily catalog.
How to choose: Support agents rarely need frontier models — start mid-tier and only upgrade if quality demands it. The per-conversation cost updates live.
Conversations / month: Total inbound support conversations across channels.
How to choose: Use last month's ticket count from your help desk. Seasonal businesses should run peak and trough separately.
Deflection rate (%): The share of conversations the AI fully handles without a human.
How to choose: Production agents land 30-70% depending on ticket mix — order-status and FAQ queues at the top, technical troubleshooting at the bottom. Run the vendor's promise AND a cautious number.
Human cost / ticket ($): Your fully-loaded cost per human-resolved ticket: wages, overhead, tooling.
How to choose: $5-12 is typical; technical B2B runs $12-25. Take last quarter's support cost divided by resolved tickets.
Input tokens / conversation: Everything the model reads across the whole conversation: instructions, history, knowledge-base lookups, every turn.
How to choose: 4,000-9,000 is typical for a multi-turn conversation with retrieval. A week of real logs beats any default.
Output tokens / conversation: Everything the model writes back across the conversation.
How to choose: 800-1,800 typical — roughly 600-1,300 words of replies.
Human-touch share (%): The share of AI-handled conversations a person still reviews or rescues — each priced at half a ticket.
How to choose: 8-15% typical; QA-heavy or regulated teams run 15-30%. Raise it until net savings stops being comfortable — that's your affordable QA budget.
📋 Typical values & starting points Don’t know a value yet? Start with these broad, sourced ballparks — the calculator’s ▾ Typical menus pre-load the same options.

Context: 2026 CX benchmarks: AI deflection median ~41% of tickets (well-tuned 50-60%); escalation-to-human median 22%, tuned target 10-15%; human handling $6-13.50/ticket (SaaS $18-35, complex B2B $30-60).

Input Default Typical ballparks
ticketsPerMonth moves the needle 5,000 Small team · 1K/mo = 1,000 · Mid support org · 5K/mo = 5,000 · Large · 50K/mo = 50,000
deflectionRate moves the needle 45 Early rollout · 25% = 25 · Industry median · 41% = 41 · Well-tuned · 55% = 55
humanCostPerTicket 8 Simple/offshore · ~$6 = 6 · Typical · ~$10 = 10 · SaaS support · ~$25 = 25 · Complex B2B · ~$45 = 45
hitlReviewRate 10 Mature · 10% = 10 · Industry median · 22% = 22
tokensInPerConversation moves the needle 6,000 Chat turn · ~500 in = 500 · Typical task · ~2K in = 2,000 · RAG-heavy · ~3.5K in = 3,500 · Long-context · ~10K in = 10,000
tokensOutPerConversation 1,200 Classification / label · ~50 out = 50 · Short answer · ~300 out = 300 · Typical response · ~800 out = 800 · Long-form · ~1.5K out = 1,500
modelSlug claude-haiku-4-5

Ballparks are broad industry starting points (sourced ranges; * = rough estimate) — your result gets more accurate as you replace them with measured numbers. Try them live in the calculator; API & agent users get the same data from the MCP resource aicost://input-reference/support-deflection-roi.

Reading your result

Net savings is the headline: human cost avoided minus the AI all-in cost (tokens + priced human touches). The multiple next to it is the return on the AI spend.

Cost per resolved conversation is your unit-economics number - compare it directly to your human cost per ticket.

The saving per deflected ticket is the break-even test: if it's negative, the model/token mix is too expensive for your ticket cost at ANY deflection rate - fix that before arguing about deflection.

What "good" looks like:
  • Human cost per resolved ticket: $5-12 typical fully loaded; technical B2B support runs $12-25.
  • Production deflection rates: 30-70% depending on ticket mix; order-status/FAQ queues at the top, technical troubleshooting at the bottom.
  • Human-touch share of deflected conversations: 8-15% typical; QA-heavy or regulated teams run 15-30%.
  • Conversation size: 4,000-9,000 input tokens and 800-1,800 output tokens across a multi-turn conversation with retrieval.

What this calculator can't tell you

Honest limitations. Every model is wrong; some are useful. Where this one falls short:

For these, use: HITL Review Cost for a deeper human-oversight model. Voice Agent Stack if the channel is phone.

Most popular

Everything above is the 80% case. The last 20% is where the money is.

The gaps we just listed are real, and they are the expensive ones: your actual prompts, your switching cost, your MLOps overhead. An AICost expert spends the hour on your AI and cloud costs, not a generic playbook. You leave with a written report: the way forward, in 30 days of concrete steps.

  • An hour with the people who built the engines
  • Report the same day
  • The fee credits toward any AICost plan
  • Two slots a week
Book a Solution Session: $299 → or $99 for small business →

Not sure yet? The $39 AICost Blueprint credits toward a Session, and the Session fee credits toward any plan. You never pay twice for the same ground. See all pricing →

Ready to run your own numbers?

You have seen the shape of it. Open the calculator with your model, your tokens, your volume.

🚀 Open the full calculator →

Where to go next

Price the review layer properly →

A full human-in-the-loop cost model with reviewer wages and sampling rates.

Voice channel version →

STT + LLM + TTS cost per call for phone support.

What one agent task costs →

Multi-step agent loops with tool calls, per task.

The cost of getting it wrong →

Quality checks and the price of hallucinations in production.

Methodology

Editorial gate
8-layer defense, see aicost.ai/ai-cost-economics
Last verified
7/20/2026, 8:00:00 PM

Author: Subu Vdaygiri, Founder & CEO of CloudIntelligence.ai. 17 years Fortune 100 (Ingram Micro, Siemens). Wharton CTO program · Kellogg CPO program · 10× AWS+Azure certified.

📖 Data sources & methodology 158 text models · 9 embeddings · 37 vision · 55 audio · 8 vector DBs across 10 vendor pages · last verified 2026-07-21

Methodology

  • All prices are USD per 1 million tokens, current as of 2026-07-21.
  • Vendor-published values have no mark. Inferred/extrapolated values are marked with * and listed below.
  • Batch API discounts are 50% off standard rates across providers that offer Batch mode.
  • Prompt caching discounts vary by provider (typically 80-90% off cached input tokens).
  • Regional data-residency surcharges (Anthropic 1.1x, OpenAI 1.1x, Google regional tiers) are NOT included in base rates.
  • Long-context pricing tiers apply when input exceeds model threshold.
  • Embedding prices are input-only (no output tokens generated).

Primary sources

Last-verified date is the most recent successful daily snapshot (aicost_pricing_snapshots) or, when no snapshot exists yet, the latest successful crawler run (aicost_crawler_runs). 10 of 10 vendors are currently verified. Aggregator services (TokenCost, AI Pricing Guru, etc.) are not listed.

Anthropic
2026-07-21
https://www.anthropic.com/pricing
Daily snapshot since Sep 2023 · 624 days captured
Anthropic Docs
2026-07-21
https://platform.claude.com/docs/en/about-claude/pricing
Daily snapshot since Sep 2023 · 624 days captured
OpenAI
2026-07-21
https://openai.com/api/pricing/
Daily snapshot since Sep 2023 · 625 days captured
Google AI
2026-07-21
https://ai.google.dev/gemini-api/docs/pricing
Daily snapshot since Dec 2023 · 600 days captured
Google Vertex
2026-07-21
https://cloud.google.com/vertex-ai/generative-ai/pricing
Daily snapshot since Dec 2023 · 600 days captured
DeepSeek
2026-07-21
https://api-docs.deepseek.com/quick_start/pricing
Daily snapshot since May 2024 · 539 days captured
xAI
2026-07-21
https://x.ai/api
Daily snapshot since Nov 2024 · 457 days captured
Mistral
2026-07-21
https://mistral.ai/pricing
Daily snapshot since Dec 2023 · 598 days captured
Cohere
2026-07-21
https://cohere.com/pricing
Daily snapshot since Sep 2023 · 624 days captured

Inferred values (marked with * in calculator tables)

Derived from industry conventions, not directly published by the vendor. Typical conventions: cached input = 10% of base (90% off), Batch API = 50% of base (50% off).

Vendor / Model Field Why it’s inferred
Anthropic — Claude Sonnet 4.6 cachedInput Derived at 10% of input rate — Anthropic publishes 90% cache-hit discount on this tier.
Anthropic — Claude Sonnet 4.5 cachedInput Derived at 10% of input rate; same 90% cache-hit convention as Sonnet 4.6.
Anthropic — Claude Sonnet 4.5 batchInput Derived at 50% of standard input — Anthropic documents uniform 50% Batch discount.
Anthropic — Claude Sonnet 4.5 batchOutput Derived at 50% of standard output — Anthropic documents uniform 50% Batch discount.
Anthropic — Claude Haiku 4.5 cachedInput Derived at 10% of input rate — Anthropic 90% cache-hit discount convention.
OpenAI — GPT-5.4 Mini cachedInput Derived at 10% of input — OpenAI documents automatic 90% discount on cache hits across GPT-5.x tier.
OpenAI — GPT-5.4 Nano cachedInput Derived at 10% of input — OpenAI 90% cache-hit convention.
OpenAI — GPT-5.4 Nano batchInput Derived at 50% of input — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Nano batchOutput Derived at 50% of output — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Pro cachedInput Derived at 10% of input — OpenAI 90% cache-hit convention.
OpenAI — GPT-5.4 Pro batchInput Derived at 50% of input — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Pro batchOutput Derived at 50% of output — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.2 cachedInput Derived at 10% of input; no residency uplift.
OpenAI — GPT-5.2 batchInput Derived at 50% of input.
OpenAI — GPT-5.2 batchOutput Derived at 50% of output.
OpenAI — GPT-5 cachedInput Derived at 10% of input.
OpenAI — GPT-5 batchInput Derived at 50% of input.
OpenAI — GPT-5 batchOutput Derived at 50% of output.
OpenAI — GPT-5.5 Pro cachedInput Derived at 10% of input — OpenAI does not publish a cached rate for *-pro models; using the family convention.
OpenAI — GPT-5.5 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5.5 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5.2 Pro cachedInput Derived at 10% of input — pro-tier convention.
OpenAI — GPT-5.2 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5.2 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5.1 batchInput Derived at 50% of input.
OpenAI — GPT-5.1 batchOutput Derived at 50% of output.
OpenAI — GPT-5 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5 Nano cachedInput Derived at 10% of input.
OpenAI — GPT-5 Nano batchInput Derived at 50% of input.
OpenAI — GPT-5 Nano batchOutput Derived at 50% of output.
Google — Gemini 3 Flash cachedInput Derived at 10% of input — Google caching discount convention ~90%.
Google — Gemini 3.1 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 3.1 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 3.1 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
Google — Gemini 2.5 Pro cachedInput Derived at 10% of input.
Google — Gemini 2.5 Flash cachedInput Derived at 10% of input.
Google — Gemini 2.5 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 2.5 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 2.5 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
Google — Gemini 2.0 Flash cachedInput Derived at 25% of input per Google 2.0 family caching rates.
Google — Gemini 2.0 Flash batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 2.0 Flash batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
Google — Gemini 2.0 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 2.0 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 2.0 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
xAI — Grok 4 (legacy) cachedInput Extrapolated at 25% of base.

Pricing is cross-verified against the LiteLLM community registry when available. Daily snapshots are kept in aicost_pricing_snapshots; every change is logged to aicost_price_changelog with old & new values for full audit trail. Read the full methodology →