The Hidden Cost of L1 Tickets: What Most MSPs Do Not Measure

Ask an MSP owner what an L1 ticket costs, and most will do the same calculation. Take a technician at $60,000 per year. Divide by the number of tickets they close in a year. Arrive at something between $10 and $20 per ticket and call it done.

That number is wrong. Not slightly wrong. Wrong by a factor of two to three at most MSPs.

The salary-per-ticket calculation ignores the majority of what that ticket actually costs. This is not an accounting quirk. It is why automation projects consistently underestimate their ROI potential, and why the savings often look larger in practice than anyone projected.

Start with the overhead multiplier

Salary is not what an employee costs you. Benefits, payroll taxes, equipment, software licenses, and management overhead typically add 30 to 40 percent on top. A technician at $60,000 costs closer to $80,000 to $85,000 fully loaded.

Run the same per-ticket calculation with the loaded number and you are already at $16 to $25 per ticket before you account for anything else.

Context switching is a real cost

L1 tickets are interruptive by nature. A technician working on a configuration task gets pulled to reset a password, then pulled again for an MFA lockout, then again for a printer issue. Each interruption has a recovery cost.

Research from the University of California, Irvine found that it takes an average of 23 minutes to fully regain focus after an interruption. L1 tickets do not just cost the time to resolve them. They cost the focus time that surrounds them.

For a technician handling 15 to 20 L1 interruptions per day, the context-switching overhead alone can consume two to three hours of productive capacity. That is time not spent on higher-margin project work.

Escalation carries a multiplier

Not every L1 ticket stays at L1. Industry data suggests 15 to 20 percent of L1 tickets escalate to L2 or above, either because the resolution failed the first time or because the classification was wrong.

L2 tickets cost five to ten times more than L1. When you blend the escalation rate into your per-ticket calculation, the average effective cost rises significantly. A ticket classified as L1 that escalates to L2 carries both costs: the failed L1 attempt and the full L2 resolution effort.

Slow resolution affects client retention

There is a cost to ticket resolution time that does not show up on any P&L directly: client satisfaction and the churn it influences. MSP clients notice when simple issues take hours to resolve. They do not always say anything. They just do not renew.

Attaching a dollar value to this is harder, but it is real. Client acquisition in the MSP space typically costs several months of recurring revenue. If slow L1 resolution contributes to even a modest increase in churn, the impact on annual revenue is material.

The opportunity cost is the largest number

L1 tickets are not just expensive in isolation. They displace work that generates more revenue. An engineer spending 40 percent of their time on password resets is not spending 40 percent of their time on projects, security reviews, or work that commands a higher billing rate.

For an MSP with an average project billing rate of $150 per hour, each hour consumed by L1 tickets is an hour not generating that rate. Across a team of five engineers, if two to three hours per day per engineer are consumed by L1 volume, the opportunity cost runs into tens of thousands of dollars per month.

The complete number

When you account for loaded salary, context switching, escalation rates, and opportunity cost, the real cost per L1 ticket at a typical MSP falls somewhere between $35 and $65. For high-volume environments or smaller teams where L1 tickets represent a larger share of overall time, it can go higher.

An MSP handling 2,000 repetitive tickets per month at $45 average real cost is spending $90,000 per month, or over $1 million per year, on work that follows a predictable script.

What to do with this

The first step is measuring. Track where your technicians' time actually goes for two weeks. Categorize every ticket by type. Calculate the percentage that are repeatable and pattern-based. The number is usually higher than expected.

The second step is separating the repetitive from the complex. Most MSPs do not need to eliminate their help desk. They need to eliminate the 60 to 80 percent of volume that should never require a human decision in the first place.

Autonomous resolution handles that category. The remaining tickets, the ones that actually benefit from human judgment, get handled faster because engineers are not buried in password resets.