guide
Cost Per Ticket: What It Actually Includes (and What Everyone Leaves Out)
Most cost-per-ticket numbers are wrong by a factor of two
Cost per ticket is the number every support budget rests on, and most of the ones in circulation were produced by dividing agent salaries by ticket volume. That calculation is missing more than half the cost.
Here is what belongs in it, what almost everyone leaves out, and why the benchmark you are measuring yourself against may not be measuring the same thing.
The definition, and the five components
The metric itself is simple: total monthly operating expense of the support function divided by monthly ticket volume. The argument is entirely about what counts as operating expense.
Published service-desk methodology includes five categories, and the second is the one most internal calculations miss:
| Component | Commonly included? |
|---|---|
| Salaries and benefits for agents | Almost always |
| Salaries and benefits for indirect staff — team leads, supervisors, schedulers, dispatchers, QA, trainers, managers | Frequently omitted |
| Technology and telecom — help desk licences, telephony, headsets, seats | Sometimes |
| Facilities — office space, utilities, insurance | Rarely |
| Travel, training and office supplies | Rarely |
Support is labour-intensive, so personnel dominate — which is exactly why omitting the supervisory layer distorts things so badly. A team of ten agents with a lead, a manager and a part-time QA reviewer is carrying roughly 25% more salary than the agent line shows.
The benchmark, and what it means
The published figure most often quoted for a human-handled customer support contact is around $13.50. Two things to understand before you use it.
First, it is a blend. It averages a password reset and a three-week billing dispute, and your mix is not the mix behind that number. Second, it is fully loaded — it includes the indirect staff, tooling and facilities above. If your internal figure is $6 and you conclude you are beating the benchmark by half, check whether you counted the same five things.
Regional variation is larger than most vendor comparisons acknowledge. The same ticket handled in different markets varies by more than the difference between most software options on your shortlist, which is why offshore capacity remains a live alternative to automation rather than a superseded one.
The four costs everyone leaves out
Attrition
Support turnover runs 40-45% annually, and replacing an agent costs $10,000-20,000 once you count recruiting, onboarding and the ramp period where output is partial. At ten agents that is roughly four replacements a year — $40,000-80,000 that appears in an HR budget rather than a support one, and belongs in cost per ticket by any honest reading.
The unmeasured contact
Cost per ticket divides by tickets. Every contact that never becomes a ticket — the customer who searched, failed, and left — costs you nothing in the numerator and nothing in the denominator, so it improves the metric. This is the structural reason deflection looks free.
Rework
A re-opened ticket is usually counted as a second ticket, which lowers cost per ticket while raising cost per resolution. If you are optimising the first number you are being paid to close conversations early.
Cost per <i>resolved</i> contact is the metric worth building the budget on. It is harder to compute and it cannot be gamed the same way.
Implementation, when AI enters
AI cost per ticket almost always gets quoted as a rate — a per-resolution price or a seat licence. Neither includes the integration engineering, and anything that queries your own systems rather than answering from documentation is a development project measured in weeks. In year one that is frequently the largest line.
Calculating your own
- Take a full month. Sum all five component categories, including the supervisory layer and a fair share of facilities.
- Add a monthly share of annualised attrition cost — replacements expected this year multiplied by the replacement cost, divided by twelve.
- Divide by resolved contacts, not opened tickets. Subtract re-opens from the denominator.
- Split the result by channel and by ticket type. The blended number is for board slides; the split is what you act on.
- Recompute quarterly. It moves with headcount, mix and tooling, and a number from last year is decoration.
The split is where the work pays off. A single blended figure tells you support is expensive, which you knew. A figure per ticket type tells you which three categories are eating the budget, and those three are almost always the ones with a documentation or product fix behind them.
What it is for
Cost per ticket does not tell you whether support is good. It tells you what a decision costs — hiring, offshoring, automating, or fixing the product defect generating 8% of the queue.
Which means the only version worth computing is one you would be comfortable defending line by line. A number built from agent salaries alone will make every automation business case look better than it is, and you will find out during the renewal.
Component list read from published service-desk methodology, which is written for IT service desks and transfers cleanly to customer support. Benchmark and attrition figures are from published 2026 research and dated. The four omissions are our analysis rather than anyone's published methodology.
Frequently Asked
What is cost per ticket?
Total monthly operating expense of the support function divided by monthly ticket volume. The disagreement is entirely about what counts as operating expense — published methodology includes five categories, and most internal calculations use one.
How much does a support ticket cost?
The commonly published figure for a human-handled customer support contact is around $13.50 fully loaded. It is a blend across ticket types, and your mix is not the mix behind it.
How do you calculate cost per ticket?
Sum agent salaries, indirect staff, technology and telecom, facilities, and training and supplies for a full month. Add a monthly share of annual attrition cost. Divide by resolved contacts rather than opened tickets.
What is left out of most cost per ticket calculations?
The supervisory layer, attrition, rework, and — where AI is involved — integration engineering. The first alone can be 25% of the salary line.
Should I use cost per ticket or cost per resolution?
Cost per resolution. A re-opened ticket counts as a second ticket, which lowers cost per ticket while raising the real cost, so optimising the first pays you to close conversations early.
Why does deflection make cost per ticket look better?
Because a contact that never becomes a ticket appears in neither the numerator nor the denominator. The customer who searched, failed and left is invisible to the metric and expensive in churn.
Is $13.50 a good cost per ticket?
It is the benchmark, not a target. Compare against it only if your own figure includes the same five components — an internal number built from agent salaries alone will look artificially good.
Does cost per ticket vary by channel?
Substantially. Split by channel and ticket type; the blended figure is for board slides and the split is what you act on.
How does AI change cost per ticket?
It changes the mix rather than the unit cost — the cheap tickets leave the human queue first, so the remaining human average rises even when total cost falls. Model both numbers or the result reads as a failure.
How often should cost per ticket be recalculated?
Quarterly. It moves with headcount, ticket mix and tooling, and a figure from last year is decoration.
Tools Mentioned
Full reviews, pricing tiers and where each one breaks.
Zendesk AI Agents
The default incumbent, now consolidating the category by acquisition. Strongest if you already live in Zendesk.
Freshdesk with Freddy AI
Cheaper than Zendesk with a comparable feature list. The trade shows up in depth rather than breadth.
Assembled
Workforce management first, AI resolution second. Bought for scheduling as often as for AI.
Gorgias
The Shopify-native default, with the deepest order, return and refund actions in this category.
You Can Also Look Into
Is AI Customer Service Cheaper Than Hiring? The Break-Even Maths
Fully loaded agent costs by region, the per-ticket comparison against published AI rates, and the two costs on each side that nobody counts.
12 Customer Service Metrics That Matter (and 8 That Do Not)
Which numbers change a decision, which are vanity, and the four that get gamed the moment you put them on a wall.
How to Reduce Customer Service Costs With AI - Real Numbers for 2026
Every guide on this topic promises 30-40% savings. None of them mention that the most common AI pricing model charges you more the better the AI works.
AI Customer Service Pricing in 2026: Per-Resolution vs Per-Seat, Modelled
Published rates from fourteen vendors, the total cost modelled at three team sizes, and the per-seat alternative that ranking pages leave out because none of them sell it.
WRITTEN BY AR · UPDATED 2026-08-04
I read the fine print. Vendor pricing pages, billing definitions, terms, funding filings and acquisition notices — then I do the arithmetic nobody publishes: what a platform actually costs at your volume, what its headline metric is really counting, and who owns it now. I do not run benchmarks, and no page here pretends otherwise.