Your most experienced engineer just spent twelve minutes walking a client through a password reset. The same engineer who debugged a technically demanding Exchange issue yesterday morning. The ticket is closed, the client is happy, and your P&L absorbed a cost you probably have not calculated.
Password resets represent the highest volume L1 request type across MSP benchmarks, yet most operators treat them as a necessary cost of doing business rather than a profit leak that compounds daily. When you calculate the true cost per password reset ticket against typical MSP margins, the economics become uncomfortable quickly. At DaemonLayer, we built our triage automation specifically around this problem after seeing how consistently it erodes margins across MSPs of every size.
Most MSPs calculate support costs using blended hourly rates across their entire technical team. This creates a dangerous blind spot when it comes to routine credential requests. Your L3 engineer earning £45,000 annually costs approximately £35 per hour when you factor in employer contributions, overheads, and billable utilisation rates. HDI benchmarks (2019, corroborated by SDI UK) put average triage handle time at approximately eight minutes for L1 tickets. SDI UK data from subsequent reporting cycles corroborates this figure. Password reset tickets often exceed this when you include identity verification, credential generation, user guidance, and ticket documentation.
The mathematics work against you immediately. Eight minutes of a senior engineer’s time costs roughly £4.67 in direct labour. Add queue management, context switching between tickets, and the inevitable follow-up when users cannot remember their temporary password, and you are approaching £7 per incident. Compare this to typical MSP margins of 15-20% on support contracts, and these tickets become a loss leader you never intended to offer. The figure climbs higher still once you account for the SLA clock running on other tickets whilst the reset is in progress.
Client expectations compound the problem. Users expect immediate support regardless of the complexity of their other open tickets. Your engineers interrupt critical project work to handle what should be low-complexity administrative tasks. The opportunity cost multiplies when you consider what that same engineer could accomplish in those eight minutes on chargeable delivery work or specialist technical issues that actually differentiate your service.
Password reset tickets do not arrive evenly distributed across your working day. They cluster around Monday mornings, post-holiday periods, and during seasonal password policy refreshes. This creates resource allocation problems that most MSPs solve by overstaffing their helpdesk during peak periods. The pattern we observe is that post-holiday volume spikes routinely run two to three times the weekly average, hitting exactly when engineers are already working through a backlog of deferred issues.
The volume problem extends beyond simple mathematics. These tickets require immediate attention in most client SLAs, which means they jump ahead of more involved tickets that might be partially complete. Engineers lose momentum on troubleshooting tasks that require sustained concentration. The mental overhead of constant interruption reduces overall productivity across your entire technical team.
This category of work also distorts your productivity metrics in a way that serves neither engineers nor clients. Your ticket closure rates look impressive when 40% of your resolved tickets are eight-minute resets, but your client satisfaction scores suffer when technical issues remain in the queue whilst engineers handle repetitive, administrative tasks. The disconnect between busy work and valuable work becomes obvious when you track engineer utilisation against billable project revenue. An MD reviewing their monthly board pack sees high ticket volumes and thinks the helpdesk is performing. The margin tells a different story.
The real cost of these tickets is not the eight minutes spent on each incident. It is the cognitive overhead of switching between non-technical administrative tasks and multi-variable problem-solving. Your engineers develop different mental frameworks for different types of work, and constant switching between them creates inefficiency that does not appear in your ticket metrics.
The sequence is predictable and the steps are consistent across every MSP we work with:
Each transition costs time and energy that accumulates across dozens of daily interruptions. MSPs we work with often underestimate this effect until they start tracking time-to-resolution on high-complexity tickets and find it correlates directly with routine reset volume on the same shift.
Engineer retention becomes a secondary cost factor that most MDs do not connect to their support workload composition until someone hands in notice. Technical staff join MSPs to solve interesting problems and develop their skills. Repetitive, low-complexity work that advances neither their career nor your clients’ outcomes erodes engagement steadily. Losing experienced staff to frustration with administrative tasks creates recruitment and training costs that dwarf the direct cost of low-complexity reset volume.
Based on recruitment fees and onboarding time we observe across clients, replacement costs typically sit between £8,000 and £15,000 per head for a mid-level helpdesk engineer, including reduced productivity during ramp-up. If you are losing one engineer per year partly due to frustration with low-complexity, repetitive work, that cost needs to sit alongside your per-ticket calculations.
Before evaluating any automation solution, establish your current baseline across three figures. Use the following steps to build the calculation:
Those three numbers will tell you whether your bottom line problem is a technology problem, a process problem, or both. Most MDs who run this exercise find the answer is both, and that the technology fix is the faster one to implement.
The L1 credential problem has a solution that changes the fundamental economics: intelligent triage automation that handles these tickets without human intervention. Rather than treating them as an unavoidable cost, automation reframes the problem as a systems issue with a measurable fix.
DaemonLayer’s triage automation reduces cost per ticket to approximately £1 by removing the human from the resolution loop on password reset tickets entirely. The platform handles identity verification, credential generation, and user communication through an automated workflow that operates outside your helpdesk queue. Your engineers never see the ticket. Your SLA clock still stops. Your client gets a faster resolution than they would from a human.
| Factor | Manual Handling | Automated Handling |
|---|---|---|
| Cost per ticket | ~£7 | ~£1 |
| Average handle time | 8-12 minutes | Under 1 minute |
| Engineer involvement | Required | None |
| SLA clock compliance | Dependent on queue | Consistent |
| Context switching impact | High | None |
| Resolution speed for end user | Variable | Faster than human |
| Retention risk | Elevated | Reduced: engineers handle higher-value work |
| Monthly saving (500 tickets) | Baseline | £3,000 saved |
Admin fatigue is a documented attrition driver across technical support roles; the retention risk row above reflects that reality.
The unit economics shift immediately. At £1 per automated ticket versus £7 for human-handled resolution, an MSP processing 500 of these tickets per month saves £3,000 monthly in direct labour costs alone. Across a year, that is £36,000 returned to margin without reducing headcount or compromising service quality. For an MSP running at 15% EBITDA margins on a £2m revenue base, recovering £36,000 in previously invisible cost represents a material improvement to the figures your accountant and any future acquirer will scrutinise. That figure excludes the revenue uplift from redirecting those recovered hours toward higher-margin project engagements, which in practice makes the real-terms improvement larger still.
The secondary benefit is harder to quantify but more strategically significant. When engineers stop handling routine resets, their available hours shift toward revenue-generating activity and technically demanding issues. Utilisation rates improve. Project delivery timelines tighten. Client satisfaction on the work that actually matters to them improves. The helpdesk stops being the cost centre that keeps the business running and starts contributing to the margin profile that funds its growth.
MSPs that restructure their L1 economics this year will carry a cost advantage into every contract renewal and acquisition conversation that follows. Those that do not will keep explaining the margin to their accountant.
Kevin Wright
Co-founder & CEO, DaemonLayer
Kevin built and exited an IT services business before working in M&A and then as Operations Director at an MSP. He holds an MBA from the University of Manchester. He founded DaemonLayer to fix the coordination problems he watched erode engineer capacity firsthand.
Connect on LinkedIn →