What Is Support Cost Per Ticket?
Support Cost Per Ticket reveals the true unit economics of your support operation — and where efficiency gains will have the greatest impact.
Key Takeaways
- Cost per ticket = total support cost ÷ total tickets resolved in the period.
- Staff costs typically represent 70–80% of total support cost.
- Reducing cost per ticket requires either lower costs or higher throughput — or both.
- Cost per ticket should be tracked alongside CSAT to avoid optimising for speed at the expense of quality.
Calculating cost per ticket
Support Cost Per Ticket is calculated by dividing total support department costs in a period by the number of tickets resolved in that period. Total costs include: agent salaries and employer overheads, team manager and quality assurance costs, software licences (helpdesk platform, telephony, workforce management tools), training costs, and a share of office or infrastructure costs. If your team costs £40,000 per month all-in and resolves 5,000 tickets, your cost per ticket is £8. Tracking this monthly reveals whether your support operation is becoming more or less efficient over time.
What drives cost per ticket
The dominant cost driver is agent time — specifically, average handle time multiplied by the fully-loaded cost of an agent hour. Tickets that require long calls, multiple back-and-forth emails, or specialist escalation cost significantly more than simple queries resolved with a canned response. The second major driver is ticket volume: if volume rises faster than agent productivity, cost per ticket increases. Conversely, deflecting low-complexity tickets through self-service reduces average ticket complexity and can reduce cost per ticket even if it does not reduce headcount.
Benchmarking and targets
Cost per ticket varies significantly by channel and industry. Industry estimates suggest phone support costs £10–£25 per contact, email £5–£15, chat £3–£8, and self-service under £1. These are rough benchmarks — your actual costs depend on agent seniority, location, tooling, and issue complexity. Rather than chasing an industry benchmark, focus on your own trend: if cost per ticket is falling while CSAT holds or improves, your efficiency programme is working.
Avoiding cost-quality trade-offs
Cost per ticket is a dangerous metric to optimise in isolation. Pushing agents to resolve tickets faster reduces cost per ticket but often worsens FCR and CSAT, generating repeat contacts that actually increase total cost. The most sustainable cost reductions come from eliminating avoidable contacts (product improvements, better onboarding), increasing self-service deflection, and improving FCR — all of which reduce cost without degrading quality. Always track cost per ticket alongside CSAT and FCR.