The Formula
MetricNet, the service desk benchmarking firm, defines cost per ticket as the total monthly operating expense of a service desk divided by the monthly ticket volume. That is the whole formula. The work is in deciding, honestly and consistently, what goes into each half.
For an MSP this number does a specific job. Your agreements are priced per user or per device, but your cost is driven by tickets. Cost per ticket connects the two: multiply it by the tickets a client raises and you have a first estimate of what that client costs to support, which is the input the client margin calculator needs.
If you want to skip the arithmetic, the cost per ticket calculator walks through the same inputs, and there is a spreadsheet version you can keep with your monthly close. Either way, the result is only as good as the time entries and ticket counts you feed it.
What Goes in the Cost Side
HDI's guidance, written by MetricNet's Jeff Rumburg, lists the operating expenses that belong in the numerator. Translated into MSP terms, include:
- Salaries and benefits for the technicians who work tickets, including payroll taxes and any on-call pay.
- Salaries and benefits for the people who support them: dispatchers, service coordinators, team leads and the service manager.
- Technology used by the desk: your PSA, RMM, remote access, phone system, documentation platform and the laptops and headsets technicians use.
- Facilities: the share of rent, utilities and insurance that the service team occupies.
- Travel, training, certifications and office supplies for the service team.
Leave out costs that belong to the client's agreement rather than to support. Licenses you resell, such as security agents or backup storage billed per seat, are cost of goods for the agreement, not the cost of answering tickets. Putting them in inflates cost per ticket and hides whether your stack margin or your labor is the problem.
Splitting People Who Do More Than One Job
In a small MSP, somebody often works tickets part of the week and does projects or sales the rest. Allocate their cost by the share of time they spend on the desk, using the time entries in your PSA. If your time entry is unreliable, fix that first; the technician billable utilization KPI depends on the same data.
What Counts as a Ticket
The denominator is harder than it looks, because an MSP's PSA holds several kinds of record. Decide once which ones count and write it down, or the number will move for reasons that have nothing to do with the desk.
| Record Type | Count It? | Reason |
|---|---|---|
| Client-raised support request | Yes | This is the core work the agreement pays for. |
| Alert that a technician worked | Yes | It consumed technician time, even if no person at the client noticed. |
| Alert auto-closed with no human touch | No | It costs tooling, not labor, and counting it flatters the number. |
| Project task | No | Projects are quoted and billed separately and have their own margin. |
| Scheduled maintenance or patch window | Count separately | It is planned work; mixing it in hides how reactive the desk is. |
| Duplicate or merged ticket | No | Count the surviving ticket once. |
| Internal ticket for your own IT | No | It is overhead, not client support. |
Keep the definition stable. If you change it, restate the previous months under the new rule before comparing, or a trend line will show an improvement that never happened.
Why Outside Benchmarks Mislead
It is tempting to compare your figure to a published service desk average. Be careful. MetricNet's benchmarking has found cost per ticket varying by more than ten times, and in later HDI guidance more than a hundred times, from the cheapest desks to the most expensive, driven mainly by utilization, handle time and wage rates. Published benchmarks come from service desks in general, not from MSP desks, which handle a wider range of systems across many clients.
An MSP ticket often includes work a corporate desk would not see: a client's line-of-business application, a vendor escalation, a site with no local contact. That makes a higher cost per ticket normal, not a failure. What matters is the trend in your own number and how it compares with what your agreements are priced to absorb.
A low cost per ticket is not automatically good either. If it falls because technicians are closing tickets without fixing the cause, the ticket reopen rate will rise and total volume will climb, so the cost reappears in the denominator next month.
Putting the Number to Work
Cost per ticket becomes useful when you combine it with volume per client. Three uses matter most to an MSP owner:
- Client profitability. Multiply cost per ticket by each client's monthly tickets and compare it with what that client pays for support. Clients who raise far more tickets per seat than the rest of your base show up immediately; the tickets per endpoint KPI makes the same comparison on a per-device basis.
- Pricing. When you build or review your price book, the expected tickets per user times your cost per ticket is the labor floor under your per-seat price. The pricing answer and the managed services pricing calculator take it from there.
- Onboarding forecasts. New clients usually raise more tickets in their first months while you clean up their environment. Knowing your cost per ticket lets you price that onboarding period rather than absorbing it.
Reading the result per client is where the conversation with a client starts. A client whose support cost is well above what they pay is a candidate for a repricing discussion or a better-fitting agreement, not automatically a client to lose.
Bringing Cost per Ticket Down
There are two ways to lower the figure: spend less per hour of support, or need fewer hours per ticket. The second is almost always the better lever, because cutting pay or tools tends to raise turnover and slow the desk.
| Lever | Effect on Cost per Ticket | Watch For |
|---|---|---|
| Resolve more on first contact | Fewer touches and handoffs per ticket | Rushed fixes that reopen later |
| Route by skill at intake | Senior time goes to senior work | Dispatch becoming a bottleneck |
| Automate common fixes in the RMM | Removes whole categories of tickets | Automation that fails silently |
| Fix recurring causes at the root | Lowers volume across the client | Project time that nobody bills |
| Standardize client environments | Shorter diagnosis on every ticket | Exceptions creeping back in at renewal |
The first contact resolution and hands-on time per ticket KPIs tell you which lever is moving. Track them beside cost per ticket each month so you can see why the number changed, not only that it did.
A Monthly Routine That Keeps It Honest
Calculate cost per ticket at the same point every month, after your books close, so payroll and tool invoices are complete. A short routine is enough:
- Pull the service team's payroll and benefits, plus the desk's share of tools and overhead, from the closed month.
- Pull ticket counts from the PSA using the saved filter that matches your written definition.
- Divide, record the result, and compare it with the trailing average rather than the previous month alone.
- Break the tickets out by client and flag any client whose share of volume is far above their share of revenue.
Kept this way, cost per ticket stops being a vanity number and becomes one of the plainest views you have of whether the desk and your pricing agree. It also feeds straight into your managed services gross margin, because support labor is usually one of the largest costs inside that margin.
Common Questions
Should I include my own salary as owner?
Only the share of time you actually spend working tickets. Include it, or the number will jump the day you hire someone to replace your desk time.
Can I calculate it per technician?
You can, but it mostly measures ticket mix. Senior technicians handle harder tickets and will always look more expensive, so use it for the desk as a whole and per client.
How do I handle tickets that span months?
Count a ticket in the month it closed and keep that rule consistently. Long-running tickets are usually few enough not to distort the result.
Should after-hours tickets be separate?
Yes if your agreements charge differently for them. Otherwise keep them in the main figure but tag them so you can see how much after-hours work costs.
Is cost per ticket useful for a very small MSP?
Yes, though monthly ticket counts will swing more. Use a rolling three-month average so a single unusual month does not drive a pricing decision.
Does cost per ticket replace cost per seat?
No. Cost per seat is what you price on; cost per ticket explains why some seats cost more than others. Use both.