Benchmark · Written by a vendor, and subtracting from its own case
$1.84 vs $13.50: what a customer conversation actually costs
Gartner benchmarks the median cost per contact at $1.84 for self-service against $13.50 for agent-assisted — roughly a 7x gap. That number gets quoted constantly and understood rarely.
It holds for structured, high-volume intents. It does not hold for complaints, edge cases, or anything requiring judgement. And a business that models its whole support operation on the $1.84 figure will be disappointed at the end of the first quarter, when the conversations that came back are counted.
This page gives you the sourced benchmarks, the four costs that vendors leave out, an interactive model that includes them, and a worked example you can copy into a spreadsheet. It is published by a company that sells AI agents, which is exactly why the subtractions are here.
By Jugl12 min readInteractive cost model18 questions answered
The 60-second version
Gartner puts the median cost per contact at $1.84 for self-service and $13.50 for agent-assisted. The gap is real for structured intents — order status, hours, policy questions, resets, booking — and unreliable for complaints, where AI CSAT drops to 3.34 out of 5.
Effective cost is higher than headline cost. Zendesk benchmarks 11.3% re-contact on AI-resolved conversations against 8.7% human-resolved. At $1.50 per AI resolution and $13.50 per human contact, that turns a $1.50 resolution into roughly $3.03 of true cost. Still a large saving. Not the advertised one.
Subtract four things from any business case: maintenance at 2–4 hours a week, per-conversation channel fees, double metering in your contract, and re-contact. Vendors rarely volunteer any of them.
Then add the half nobody measures. For consumer businesses, after-hours revenue capture and in-conversation bookings frequently grow faster than the cost saving, because it is new revenue rather than reallocated staff time.
- What is cost per contact?
- At a glance
- The benchmark numbers, sourced
- Where the 7x gap is real — and where it is not
- Effective cost: the model most businesses skip
- The half of the ROI nobody measures
- Four things to subtract from your business case
- A worked model you can copy
- The questions behind the number
- Where Jugl fits on cost
- Methodology and disclosure
- FAQ — 18 questions
- People also ask
Definition
What is cost per contact?
Cost per contact is the total cost of running customer support divided by the number of contacts resolved in the same period. A complete calculation includes salaries and on-costs, software subscriptions, per-conversation channel fees such as WhatsApp charges, and a fair share of management overhead. Gartner benchmarks the median at $1.84 for self-service against $13.50 for agent-assisted — roughly a sevenfold difference. The metric is only meaningful when the denominator is resolved contacts rather than received contacts, because conversations that come back within 48 hours were never resolved and should not be counted as such. Effective cost per contact — after re-contact, maintenance and channel fees — is the figure that survives a finance review.
Definition maintained by the Jugl Editorial Team. Jugl sells an AI customer agent platform and is an interested party; benchmark figures are attributed to their original sources throughout.
The formula, written out
Effective cost per AI resolution = AI cost + (re-contact rate × human cost per contact).
Blended cost per conversation = (contained × effective AI cost) + (escalated × human cost), all divided by total conversations.
The third formula is the one to present internally, because it is the only one that describes what actually happens: some conversations are handled by software, some by people, and some by software and then by people. Anything simpler is a marketing number.
Customer service cost benchmarks at a glance
At a glance
- Self-service cost per contact
- $1.84 median (Gartner)
- Agent-assisted cost per contact
- $13.50 median (Gartner)
- Loaded agent cost
- ~$52 per hour, fully burdened (Salesforce State of Service)
- Tier-1 AI resolution
- $0.50–$2.00 (Zendesk-derived)
- Tier-1 human resolution
- $6.00–$12.00 (Zendesk-derived)
- Where the gap holds
- Order status, hours, policy, resets, booking, basic product questions
- Where it breaks
- Complaints and judgement calls — AI CSAT 3.34 vs 4.32–4.41 (Zendesk)
- The cost nobody models
- 11.3% re-contact on AI-resolved vs 8.7% human-resolved (Zendesk)
- Realistic containment
- ~41% median; 65–72% for strong deployments (Aissist.io)
- Maintenance to budget
- 2–4 hours a week — roughly $450–$900 a month at a loaded rate
- Typical payback
- Weeks, not months, at SMB scale
- Best use cases
- High-volume repetitive intents, after-hours coverage, seasonal surges
- Who should model this first
- E-commerce, hospitality, clinics, education, real estate, services
- Expected outcome
- Lower blended cost per conversation plus captured after-hours revenue
The benchmark numbers, sourced
Every figure below is attributed. Where a number is derived rather than published directly, it says so. If you are building a business case someone will hold you to, cite the source alongside the number — it is the difference between a proposal that gets approved and one that gets questioned.
| Metric | Figure | Source |
|---|---|---|
| Median cost per contact — self-service | $1.84 | Gartner |
| Median cost per contact — agent-assisted | $13.50 | Gartner |
| Loaded human agent cost | ~$52 per hour | Salesforce State of Service |
| Tier-1 AI resolution | $0.50–$2.00 | Zendesk-derived |
| Tier-1 human resolution | $6.00–$12.00 | Zendesk-derived |
| Hybrid model at 22% escalation | ~71% lower cost per resolution | Benchmark analysis |
| CSAT cost of that hybrid model | ~0.05 points | Same analysis |
| Re-contact — AI-resolved vs human-resolved | 11.3% vs 8.7% | Zendesk |
| AI CSAT — complaints vs structured queries | 3.34 vs 4.32–4.41 out of 5 | Zendesk |
| Median tier-1 automation rate | ~41% | Aissist.io |
| Strong deployments | 65–72% | Aissist.io |
| Self-service resolution vs deflection | ~14% resolution against 45%+ deflection | Gartner |
Where the 7x gap is real — and where it is not
Real: structured, repetitive, low-emotion intents
These resolve at 55–70% first-contact for AI-native platforms at under $3 per resolution. The economics are straightforwardly good, and the customer usually prefers the instant answer to the queue.
Not real: complaints, disputes and judgement
Zendesk puts AI CSAT at 3.34 out of 5 for complaint handling against 4.32–4.41 for structured queries. More than a full point, on exactly the conversations where sentiment damage is permanent and expensive. And re-contact runs 11.3% on AI-resolved conversations against 8.7% human-resolved.
That re-contact gap has a direct cost. If roughly one in nine AI-resolved conversations comes back, your effective cost per genuinely-resolved contact is higher than the headline — and the customer experience is worse than the dashboard suggests, because they had to ask twice.
- ✓Structured, repetitive intents at 55–70% first-contact resolution
- ✓After-hours and weekend coverage with no rota and no overtime
- ✓Seasonal and campaign surges absorbed without temporary hiring
- ✓Multilingual coverage without a hire per language
- ✓Instant first response on paid traffic you have already bought
- ✓Consistent answers — no variance between your best and newest agent
- ×Complaints, where CSAT falls to 3.34 out of 5 and damage is durable
- ×Anything requiring a judgement call or a policy exception
- ×Safety-critical questions — allergies, symptoms, safeguarding
- ×Negotiations, valuations and money decisions
- ×Conversations where the customer has already asked twice
- ×Anything the agent cannot verify from a real system of record
Effective cost: the model most businesses skip
Almost every ROI calculation in this category stops at the headline cost per resolution. The model below carries on for one more step, into the conversations that come back. Move the sliders to your own numbers — the outputs are illustrative estimates from your inputs, not a quote.
Effective cost per resolved conversation
Headline AI cost, plus the conversations that come back — which is where business cases die
Every inbound across WhatsApp, Instagram, web chat, email and phone — not only the ones that became tickets.
Median tier-1 automation sits near 41%. Strong deployments run 65–72%. Expect roughly half your target in month one.
Zendesk-derived tier-1 AI resolution runs $0.50–$2.00. On a flat subscription this falls as volume rises.
Zendesk benchmarks 11.3% on AI-resolved conversations against 8.7% human-resolved. Measure yours at 48 hours.
Gartner's median agent-assisted contact is $13.50. Loaded agent cost is around $52 an hour (Salesforce).
The half of the ROI nobody measures
Almost every ROI calculation in this category counts saved cost and ignores created revenue. For consumer businesses that is usually backwards.
The cost side
3,000 conversations × 6 minutes × $0.87/min = $15,600 a month of recovered capacity.
The revenue side
If 30% of 5,000 monthly conversations arrive outside working hours and 5% convert at $60: $4,500 a month that previously went to whoever replied first.
For a lot of consumer businesses the second number grows faster than the first, because it is new revenue rather than reallocated staff time. And it is invisible unless you deliberately measure it — which almost nobody does. Tag conversations that led to a purchase or a booking, and report revenue influenced alongside cost saved. The reporting change costs nothing and changes how the programme is funded. The measurement guide sets out the tagging.
This is also why cart recovery belongs in the model. Most abandonment is an unanswered question about shipping, delivery time or returns rather than price sensitivity — which means a conversation converts where a discount code merely discounts. The mechanics are in the cart recovery breakdown.
Four things to subtract from your business case
Be honest about these or your business case will not survive contact with reality. Three of the four are invisible at signature and obvious at renewal.
A worked model you can copy
A 15-person e-commerce business: 5,000 conversations a month, $60 average order value, three support staff, 60% containment.
| Line | Monthly |
|---|---|
| AI platform (flat tier) | $99 |
| Meta conversation fees | $250 |
| Maintenance — 3 hrs/week at $52 | $624 |
| Re-contact handling cost | ~$900 |
| Total cost | ~$1,873 |
| Deflection value — 3,000 × 6 min × $0.87 | $15,600 |
| After-hours revenue capture | $4,500 |
| Total value | $20,100 |
| Net position | ~$18,200 a month |
- Count a real week of conversations across every channel, not just the ticket system
- Multiply by average handling minutes and your loaded hourly rate for today's cost
- Model containment at half your target for month one, target for month six
- Add re-contact at 11% of contained conversations, priced at human cost per contact
- Add maintenance at three hours a week and channel fees at your real volume
- Add the revenue side: after-hours capture, recovered carts, bookings taken in-thread
- Present blended cost per conversation, not cost per AI resolution
The questions behind the number
Is AI customer service actually cheaper than human support?
Short answer
Yes for structured intents, by a wide margin — Gartner's $1.84 against $13.50 is real for order status, hours, policy questions, resets and booking. Factor in re-contact and maintenance and the effective gap narrows but stays substantial. For complaints it is cheaper per contact and more expensive in customer lifetime value.
Example
Why is my cost per contact higher than the published benchmark?
Short answer
Three causes cover almost every case. Containment is low because the knowledge base has gaps and nobody is reading the escalation log. Re-contact is high because conversations counted as resolved were not. Or your contract meters twice — once per ticket and again per AI resolution on the same ticket.
Example
Should deflection count as savings in the business case?
Short answer
Only if you actually reduce or redeploy the hours. Deflection produces recovered capacity, not cash. That capacity is genuinely valuable — it is how a three-person team absorbs five people's volume through a growth year — but it belongs in a capacity line rather than a savings line, and finance will check.
Does pricing shape matter more than the headline price?
Short answer
Usually, yes. Per-resolution pricing costs more every time the AI improves and every time volume spikes, so your best sales week produces your largest invoice. Per-seat pricing charges you for the headcount you are trying not to add. Flat tiers cost more at trivial volume and stop scaling with your success.
Example
Where Jugl fits on cost
Jugl publishes four flat tiers — Free, $31, $119 and $390 a month — with the AI included and nothing metered per message, per token or per resolution. The reason that matters to a cost model is structural rather than promotional: under per-resolution billing your invoice rises every time the AI gets better and every time volume spikes, which in seasonal and campaign-driven businesses means your best week is also your most expensive one. Flat tiers remove that coupling, so the model above stays true when volume moves.
What Jugl does not remove is Meta's per-conversation fee on WhatsApp, which applies regardless of vendor, or the maintenance line, which applies regardless of platform. Any comparison that leaves those out — ours included — is not a comparison worth acting on. Jugl customers typically see around 73% fewer tickets reaching a human at roughly 94% satisfaction; those figures are customer-reported and typical rather than guaranteed, which is why the model on this page asks you to enter your own.
Do not buy Jugl if your volume is genuinely tiny — under about 100 conversations a month the arithmetic does not compel it, and the permanent free tier is there precisely so you can establish that for yourself without a sales call. If you are already shopping, the buyer's guide compares the category, and the Intercom alternatives page models what per-resolution pricing costs at real volume.
Methodology and disclosure
Written by
Jugl Editorial TeamJugl Inc., Frisco, Texas — an AI customer agent platform used by 1,000+ businesses.
Reviewed by
Jugl customer operations & financeChecked against live deployment data and current vendor documentation.
Methodology & disclosure
Where the figures come from. Cost-per-contact medians are Gartner's published benchmarks. Loaded agent cost is from Salesforce's State of Service research. Tier-1 resolution cost bands, re-contact rates and CSAT-by-intent splits are Zendesk-derived. Automation-rate bands are from Aissist.io's programme analysis. Where a number is derived rather than published directly, the table says so.
Why effective cost is treated as the honest metric. Because re-contact is measurable, material and systematically excluded from vendor ROI tooling. A resolution that returns within 48 hours was not a resolution, and pricing it as one produces a business case that fails its first quarterly review — which damages the credibility of the programme more than a smaller, accurate number ever would.
Conflict of interest. This page is published by Jugl, which sells an AI customer agent platform and therefore benefits if you conclude the economics work. That is precisely why the subtractions — maintenance, channel fees, double metering, re-contact — are stated here rather than left for you to discover, and why the model defaults to conservative inputs rather than flattering ones.
How this page is maintained. Benchmarks are reviewed against current published research and revised when sources update. The page carries no year stamp because a dated benchmark misleads the moment it ages. Calculator outputs are illustrative estimates generated from your own inputs — not quotes, forecasts or guarantees.
Cost per contact: 18 questions answered
What is cost per contact in customer service?
Is the $1.84 vs $13.50 gap real?
How do I calculate the effective cost per resolved conversation?
What is the payback period on AI customer service?
Should I count deflection as savings in my business case?
What costs do vendors leave out of their ROI calculators?
What is double metering and how do I avoid it?
Why does re-contact rate matter more than containment?
How much does maintenance really cost?
Does AI reduce headcount or absorb growth?
What is the revenue side of the AI support business case?
How do WhatsApp conversation fees affect cost per contact?
What containment rate should I budget for in year one?
Is per-resolution pricing cheaper than a flat subscription?
How do I model cost per contact for a business my size?
What is the cheapest way to test the economics before committing?
Does lower cost per contact hurt customer satisfaction?
How does Jugl price against per-resolution vendors?
People also ask
The cheapest way to settle this is your own data
Every benchmark on this page describes someone else's business. Yours has a different question mix, a different channel split and a different share of conversations arriving at 11pm — and those three variables decide whether your cost per contact lands nearer $3 or nearer $13.
Point an agent at your real questions for two weeks and count what it resolves. The free tier is permanent and needs no card, so the test costs an afternoon rather than a procurement cycle. Every week you defer it, the conversations arrive anyway — they just get answered by whoever is free, or by nobody.
The conversations you are not answering still cost you. They just do not appear on any invoice.
SOC 2 Type 2 · HIPAA compliant · Meta Business Partner · NVIDIA Inception · 1000+ businesses
Keep reading
Sources: Gartner customer service research (median cost per contact for self-service and agent-assisted; self-service resolution against deflection); Salesforce State of Service (fully burdened agent cost); Zendesk customer experience benchmarks (tier-1 resolution cost bands, re-contact rates on AI-resolved and human-resolved conversations, CSAT by intent type); Aissist.io programme analysis (median and strong-deployment automation rates); Lorikeet (first-contact resolution for AI-native platforms); published benchmark analysis of hybrid escalation models; and Jugl's own published pricing and customer-reported deployment data. Figures described as derived are calculated from published bands rather than quoted directly. This page is published by Jugl, which sells an AI customer agent platform and is therefore an interested party; Jugl's outcome figures are customer-reported and typical rather than guaranteed. Calculator outputs are illustrative estimates generated from your own inputs, not quotes, forecasts or guarantees, and nothing here is financial advice. Meta, WhatsApp, Messenger, Instagram and Facebook are trademarks of Meta Platforms, Inc.; Jugl is a Meta Business Partner and this page is published by Jugl and is not endorsed by or affiliated with Meta Platforms, Inc. All other product names are trademarks of their respective owners.
Start free at Jugl · No card required · Permanent free tier