Cost per ticket is the fully loaded cost of handling one support ticket. The IT support cost per ticket calculator divides the total cost of running your help desk by the number of tickets it handles, so you can see what each request really costs — and what would make it cheaper.

Most teams know their headcount and their ticket count, but not the cost that connects them. A desk that handles 2,000 tickets a month on a $40,000 monthly budget spends $20 per ticket, whether anyone has done the math or not. Doing the math is what lets you improve it.

How cost per ticket is calculated

The formula is simple: total support cost divided by the number of tickets resolved in the same period. The work is in getting the total cost right.

Total cost has three parts. Labor is the biggest: agent wages plus benefits, usually 25 to 35% on top of salary, plus a share of team-lead and management time. Tools are next: the help desk platform, phone and chat software, remote access, and monitoring. Overhead is the rest: training, office space, and the share of IT infrastructure the desk uses.

The ticket count should be resolved tickets, not received ones. A backlog of unanswered tickets makes the cost look lower than it is, because the work has not been done yet. Count what was actually finished in the period.

Worked example

A five-agent desk costs $38,000 a month in total. Salaries and benefits are $30,000, the help desk and phone tools are $4,500, and training, management time, and overhead add $3,500.

The desk resolves 1,900 tickets that month. Cost per ticket is $38,000 divided by 1,900, or $20 per ticket.

Now suppose the team publishes ten knowledge articles that deflect 200 simple password-reset tickets to self-service. Tickets fall to 1,700, but the cost stays $38,000, so cost per ticket rises to $22.35. That looks worse — but the desk now has spare capacity for harder tickets, and the cost per resolved issue, counting the self-service ones, has actually fallen. Always read cost per ticket alongside deflection.

How to use the result

Use cost per ticket to compare options honestly. An outsourcer quoting $15 per ticket looks cheap against your $20, until you check what is included: their price may exclude the tools, the management, or the complex tickets that stay with you. Compare like with like.

Use it to justify automation. If a chatbot resolves 300 tickets a month at $3 each, and your desk resolves them at $20, the saving is $5,100 a month. That is the budget for building the bot, expressed as a number a finance team understands.

Track the trend, not the absolute value. A desk whose cost per ticket falls 10% over a year while satisfaction holds steady is improving. A desk whose cost falls because agents are rushing and reopen rates are climbing is not. Pair this number with first-contact resolution and reopened tickets before drawing conclusions.

Note: Split cost per ticket by channel if you can. Phone tickets usually cost two to three times more than email, and chat sits in between. The blended average hides the fact that moving a ticket from phone to self-service saves far more than moving it from email.

Cost per ticket and staffing

Cost per ticket and headcount are two views of the same budget. If the staffing math says you need another agent, this calculator says what that agent does to the cost per ticket. Run the help desk staffing calculator first to get the headcount right, then use this one to price it.

Frequently asked questions

What is cost per ticket?

It is the total cost of running your support desk divided by the number of tickets handled in the same period. It is the standard way to compare the efficiency of a help desk over time or against outsourcing.

What costs should I include?

Agent wages and benefits, the help desk software, phones and chat tools, training, and a share of management and office overhead. The biggest mistake is counting wages only and forgetting the tools.

What is a typical cost per ticket?

It varies widely by channel and complexity. Industry benchmarks often put a phone ticket at $20 to $30 and an email ticket lower, but your own trend matters more than any benchmark.

Does a lower cost per ticket mean a better desk?

Not on its own. A desk can cut cost per ticket by rushing tickets and creating repeat contacts. Track it alongside first-contact resolution and customer satisfaction.

How do I reduce cost per ticket without cutting service?

Deflect simple tickets to self-service, fix the root causes that generate repeat tickets, and improve knowledge articles so agents resolve faster. All three cut tickets or handle time without touching quality.