Cost Per Ticket Calculator, With Overhead Included

Most teams quote a cost per ticket that ignores overhead. This cost per ticket calculator doesn't, which is why the number comes out higher.

Your true cost per ticket

Customer support industry averages
  • Employer overhead25% on top of salary
    Benefits, payroll tax, equipment and management time.
Total support cost per year
$527,200
Tickets per agent per month
500
Cost per ticket
$11

Every duplicate ticket in your queue costs you this number twice. Cutting duplicates is the cheapest cost-per-ticket win available, because it needs no new headcount and no new process.

Ticket Merger, based on customer support industry averages

Get back $6,240 a year

Attickets a month, about 120 are the same person asking again, costing 234 agent hours a year.

Agent time back
234 hrs/yr
Worth
$6,240/yr
Your plan
$29/mo

What this cost per ticket calculator counts

Cost per ticket = (fully loaded people cost + tooling cost) divided by tickets handled.

The mistake is using base salary. Benefits, payroll tax, equipment, software and the management time spent on the team are all part of what a ticket costs, and adding them typically moves the number by 25% to 40%.

Include your helpdesk licence, your telephony, your survey tool and anything else the support team could not work without.

What a good number looks like

It varies enormously by segment, so comparing against an industry average is close to useless. Compare against yourself instead.

Track it monthly and watch the direction. If cost per ticket is climbing while volume is flat, handle time is growing. If it falls while CSAT falls, you have cut something you needed.

Simple consumer support: often a few dollars per ticket.
B2B software support: frequently ten to thirty dollars.
Complex technical or enterprise support: can be considerably higher.

The duplicate distortion

Here is the part that trips people up. Duplicates make your cost per ticket look better, not worse, because the denominator grows.

Two tickets for one problem, both handled, means your average is dragged down by the cheap second one, while your total cost went up. So a team that fixes duplicates often sees cost per ticket rise, while total support cost falls.

Track total support cost and tickets per real problem, not just the average.

FAQ

Frequently asked questions

How do you calculate cost per ticket properly?

How to calculate cost per ticket: add fully loaded salary, overhead and tooling for everyone touching the queue, then divide by tickets handled in the same period. Payroll alone understates it by a third or more.

How does the cost per ticket calculator work?

It adds fully loaded salary, overhead and tooling for everyone who touches the queue, then divides by tickets handled in the same period. That is the real cost per ticket, not the payroll-only version.

Should I include managers in the people cost?

Include the share of their time spent on support. A support lead who spends half their week on the queue counts as half a person.

Do duplicates make cost per ticket look better or worse?

Better, misleadingly. They inflate the ticket count so the average falls while your real spend rises. It's the most common way this metric lies.

Cut the tickets, not the service

Duplicates are the only volume you can remove without a single customer noticing.

Start free trial

14-day free trial. No credit card required.