- Manish Jain
View
Share
Help desk cost per ticket is the number most IT and finance leaders use to compare support options. It is simple to quote and easy to compare. However, it is also easy to calculate in a way that hides the real cost. That happens most when tickets are escalated, reopened or sent to the wrong tier.
This guide shows how to calculate it properly and what drives the cost at each support tier. It also sets out a realistic onshore baseline. Finally, it explains when a nearshore help desk lowers the number and when it does not, based on the help desk programs our teams run for U.S. technology companies.
Why Cost Per Ticket Misleads on Its Own
A low cost per ticket can come from good operations or from cutting corners. For example, a team that closes tickets fast without fixing the cause looks cheap. Yet users open the same issue again next week. Similarly, a Tier 1 team that escalates most tickets looks efficient, but the cost simply moves to Tier 2.
So read the number alongside three others: first-contact resolution, escalation rate and reopen rate. Then, if cost per ticket falls while those three hold steady, the help desk is truly getting more efficient. Our guide to technical support KPIs covers the full set.
How to Calculate Help Desk Cost Per Ticket
The formula is simple. Divide total help desk cost for a period by the tickets resolved in that period. The hard part is counting the full cost, because most internal estimates include salaries and little else.
What Goes Into Total Cost
- Agent compensation: wages plus benefits, payroll taxes and paid time off.
- Management and quality: team leads, supervisors, quality analysts and workforce planners.
- Tools: ITSM and ticketing licenses, telephony, remote-access and knowledge base software.
- Facilities and equipment: workspace, hardware and network costs, or remote-work stipends.
- Turnover: recruiting, onboarding and training to replace agents who leave.
Also, use tickets resolved, not tickets opened, as the divisor. Count each unique ticket once, when it reaches resolved status. An escalation to another tier is not a new resolved ticket. Track reopened tickets separately, because they add handling cost without adding a new issue. Then exclude duplicates and cancelled requests under a written reporting policy.
Finally, make every cost and the ticket count cover the same period. If management or infrastructure is shared with other teams, allocate only the help desk’s share.
A Worked Example
For example, the table below models a 20-agent Tier 1 help desk in the United States. Wages use the national median for support specialists covered in the next section, and the other figures are illustrative.
| Cost item | Basis | Annual cost |
|---|---|---|
| Agent compensation, including wages and benefits | 20 agents x $61,860 median wage = $1,237,200; divided by 0.70 for benefits | $1,767,429 |
| Management and quality | Leads, supervisors, QA (illustrative) | $240,000 |
| Tools and software | Ticketing, telephony, remote access (illustrative) | $60,000 |
| Facilities and equipment | Illustrative | $160,000 |
| Recruiting, onboarding and training | Illustrative | $90,000 |
| Total annual cost | Sum of the rows above | $2,317,429 |
| Tickets resolved | 20 agents x 4,800 tickets a year | 96,000 |
| Cost per ticket | Total cost/tickets resolved | $24.14 |
Notice that agent pay is only about three-quarters of the total. That is why comparing hourly rates alone understates what an in-house help desk really costs.
The Onshore Baseline
For U.S. teams, public data gives a reliable starting point. The Bureau of Labor Statistics puts the median wage for computer user support specialists at $61,860 in May 2025. For network support specialists, it was $76,220. Those roles map roughly to Tier 1 and Tier 2 work, although the match is an approximation rather than an exact equivalent.
But wages are only part of the cost of employment. In June 2026, benefits made up 30% of total compensation for private industry workers, according to the same agency. As a result, a median-wage specialist costs an employer about $42 an hour in pay and benefits alone. That is compensation only, not the full cost of running a help desk, which also includes management, software, facilities, recruiting and training.
Why Cost Changes by Support Tier
Cost per ticket rises sharply with each tier, because tickets take longer and need more skilled staff. So the biggest savings usually come from resolving each ticket at the lowest tier that can fix it. This practice is often called shift-left. Our guide to Tier 1 to Tier 3 technical support explains how the tiers divide the work.
| Tier | Typical work | Main cost driver | Biggest lever |
|---|---|---|---|
| Tier 1 | Password resets, access requests, how-to questions | Volume and handle time | Knowledge base, scripts and self-service |
| Tier 2 | Application, device and network troubleshooting | Skilled time per ticket | Better Tier 1 triage and documented fixes |
| Tier 3 | Complex system, integration and infrastructure issues | Senior engineering time | Root-cause fixes that stop repeat tickets |
Also track cost per ticket by tier as well as in total. Otherwise, a rise in Tier 3 work can hide real gains at Tier 1.
Where Help Desk Costs Usually Leak
High cost per ticket usually has a few specific causes. So before changing the support model, find out which of these drives your number.
| Cost leak | What happens | What to monitor |
|---|---|---|
| Excess escalations | Tier 1 sends tickets to Tier 2 that it could have solved | Escalation rate |
| Repeat incidents | The same underlying issue creates many tickets | Repeat incident rate |
| Reopened tickets | The first fix does not solve the problem | Reopen rate |
| Slow diagnosis | Agents spend too long on common issues | Average resolution time |
| Knowledge gaps | Agents cannot find documented solutions | Knowledge base use |
| Poor workforce planning | Staffing does not match ticket demand | Utilization and occupancy |
Outsourcing can lower labor cost. However, unresolved process problems follow the work into any new delivery model, so fix or plan for them at the same time.
When Nearshore Support Lowers Cost Per Ticket
A nearshore help desk lowers cost per ticket mainly through lower all-in labor cost, while keeping agents on U.S. hours and in English. However, the savings only hold under the right conditions.
- Enough steady volume to staff dedicated agents for each tier, rather than a shared pool that never learns your environment.
- Full system access to your ITSM, directory and remote tools, so agents resolve tickets instead of passing them back.
- Documented processes and a knowledge base the team can follow and improve.
- The same metrics on both sides, including resolution, escalation and reopen rates, so savings are not bought with quality.
By contrast, nearshore support fits less well when volume is tiny and unpredictable. The same is true when most work needs hands-on access to on-site equipment. In those cases, a smaller onshore team or a hybrid model may cost less per resolved ticket.
How to Compare Onshore and Nearshore Costs
A fair comparison uses the same ticket volume, support hours, ticket complexity, service levels and resolution standards for both models. Then compare the fully loaded cost per resolved ticket, not hourly agent rates.
| Cost factor | What usually differs | What to check |
|---|---|---|
| Agent compensation | Usually lower nearshore | Same skills and English level for each tier |
| Management and quality | Often included in a partner rate | Supervisor ratios and QA coverage |
| Tools and software | Usually similar | Who pays for licenses and integrations |
| Transition | One-time cost to move the work | Knowledge transfer time and parallel running |
| Productivity | Depends on system access and training | Tickets resolved per agent at the same quality |
| Rework | Depends on resolution quality | Reopen and escalation rates in both models |
What It Looked Like in Practice
One example is a U.S. technology integration company with about $350 million in revenue. Our nearshore team now handles 100% of its Tier 1 to Tier 3 help desk with 82 dedicated agents. Of those, 25 work at Tier 1, 44 at Tier 2 and 13 at Tier 3. The program also covers POS, terminal and network support, dispatch and project coordination.
The client reports $1.55 million saved over 21 months, measured against the cost of a U.S. W2 talent pool. Read the full case study to see how the tiers were staffed and rolled out.
Want to know your real cost per ticket?
Share your monthly ticket volume, tier mix and current team size. Our team will model your cost per ticket today and with a nearshore help desk, side by side.
Frequently Asked Questions
How do you calculate help desk cost per ticket?
Divide the total cost of running the help desk for a period by the tickets resolved in that period. Also, total cost should include agent compensation and benefits, management, tools, facilities and turnover, not salaries alone.
Why is Tier 3 so much more expensive per ticket?
Tier 3 tickets take longer and need senior engineers, who cost more per hour. That is why resolving tickets at the lowest capable tier usually saves more than cutting hourly rates.
Should we measure cost per ticket or cost per resolution?
Measure cost per resolved ticket and track reopen rate beside it. After all, a ticket you close and then reopen has cost you twice.
Does a nearshore help desk always cost less?
Not always. Savings depend on steady volume, full system access and documented processes. With very low or unpredictable volume, or mostly on-site work, a smaller onshore or hybrid model can be cheaper.
Measure the Full Cost, Then Decide
A reliable help desk cost per ticket counts every cost and divides by tickets actually resolved. You then read it beside resolution and reopen rates. Once you have that number by tier, you can see where the money goes and which options would lower it. To see how a dedicated team would fit your environment, explore our technical support outsourcing and our work in technology outsourcing services.
