how to calculate cost per ticket for it helpdesk
Calculates fully-loaded cost per helpdesk ticket. Covers the cost components, the allocation method, and how to use the number. Use for budgeting and ROI cases. Not for chargeback politics (separate discussion).
TL;DR
Add up fully-loaded labor (salaries plus benefits plus overhead for everyone touching tickets), add tooling and facilities, and divide by tickets resolved in the period. Typical ranges are 15 to 25 dollars per ticket for staffed desks; the number's value is in trends and comparisons, not absolute precision.
The error
(Finance task; no error.)Steps
- Gather labor costs: salaries, benefits (30 to 40 percent loaded), and the share of management time spent on the desk. Expected: total labor. Include everyone who touches tickets, including tier 2/3 time.
- Add direct costs: ITSM licensing, remote support tools, KB tooling, phones. Expected: total tooling. Allocate shared tools by reasonable share.
- Add facilities overhead if the desk is onsite (space, equipment). Expected: total overhead. Keep the allocation method simple and documented.
- Divide by tickets resolved (not opened) in the same period, ideally per quarter. Expected: cost per ticket. Use resolved to avoid rewarding backlog.
- Track the trend and break it down by channel (phone costs more than chat, chat more than self-service). Expected: reported. The breakdown drives the deflection business case.
When to use
- Budgeting and staffing cases
- Automation ROI justification
When not to use
- Blaming agents (it is a system metric)
- Cross-company benchmarking without context (cost structures differ)
Compatibility
- Spreadsheet-level analysis; data from ITSM and finance
Variants
Fully-loaded vs marginal cost
Marginal cost (one more ticket) is lower; use fully-loaded for budgeting, marginal for capacity planning.
Outsourced desks
Use the contract cost per ticket, but verify what is included.
Why it happens
"You can't manage what you don't measure" applies to the helpdesk budget too. Cost per ticket turns automation and deflection from vague goodness into dollars.
Edge cases
- Do not optimize cost per ticket by degrading quality; pair it with CSAT always.
- Recompute annually; salaries and tools change the number.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_ik-A0vTAdjnOYUg-L6mN5Q
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.