Kaseya’s 2026 State of the MSP Report, a survey of more than 1,000 managed service providers (MSPs), found that 53% already use AI to automate ticketing, patching and monitoring. Those routine tickets are also where junior technicians learned the job.
An MSP that hands those tickets to software loses the place its new engineers learned each client’s setup.
MSPs using AI this way report faster first responses, better technician efficiency and less burnout. Still, more than half of the MSPs surveyed have automated only about a quarter of their workload so far.
Junior Technicians Learned Client Systems on Tier 1 Tickets
A new technician working that queue learned how each client had set up its systems and which problems kept coming back. It also taught them when to hand a ticket up. Many of today’s Tier 2 and Tier 3 engineers started there.
In August, Stanford researchers reported a similar pattern across the job market. Hiring of workers ages 22 to 25 is falling fastest in jobs where AI does the task itself.
A failed backup or a firewall change that breaks a client’s VPN still needs an engineer who knows that client’s environment. And those engineers are getting harder to find. In the same Kaseya survey, the share of MSPs reporting trouble hiring skilled technicians nearly doubled in a year, from 9% to 16%.
Training junior hires gets harder too, with fewer easy tickets to learn on. Some MSPs now bring in engineers a support partner has already trained and manages.
LTVplus Trains New Engineers on Each MSP’s Clients Before Go-Live
LTVplus, a managed technical support partner for MSPs with 500+ team members across 22 countries, starts with engineers trained in ConnectWise, Datto, Kaseya and NinjaOne.
“Knowing the platform gets an engineer to the starting line,” said David Henzel, Co-Founder of LTVplus. “The important work is learning how that MSP serves its clients, how the environments are documented and where an issue goes when it needs to move up the chain.”
LTVplus teams go live in about 30 days from the discovery call. Platform training happens before the engineer joins, so that month goes to the MSP’s clients, systems and escalation procedures.
The MSP sets the tools, tiers and coverage the seat needs on the discovery call. During onboarding, LTVplus manages the engineer. The MSP supplies system access, client documentation, its escalation matrix and its service-level agreement (SLA) requirements, plus time from its own team in onboarding sessions. The two sides also agree on runbooks during solution design.
After go-live, LTVplus handles quality assurance, coaching, performance reviews, scheduling, shift coverage and daily oversight. At the MSP’s request, it runs ticket QA on each engineer, checking their work against those runbooks and the escalation matrix, and it sends the MSP weekly reporting. Response and resolution targets are set for each of the MSP’s clients during solution design and reported monthly, so the MSP can show SLA compliance in its quarterly business reviews. The helpdesk reports also track first-contact resolution and backlog for each client.
Each engineer works only for that MSP, inside its tools and under its name. The MSP directs the work and sets ticket priorities.
MSPs Lose Client Knowledge When Technicians Leave
When an experienced technician leaves, the replacement starts over on every client environment. Much of what the last technician knew came from months of tickets on the same accounts, and a runbook only captures part of it.
“Anybody can find you a résumé. Keeping that seat filled three years later takes quality assurance, coaching, coverage planning, and noticing when someone’s about to burn out. That’s what MSPs are buying,” Henzel said.
LTVplus assigns its dedicated Tier 1-3 engineers for MSPs to one MSP each, so an engineer stays on the same accounts long enough to learn their recurring problems. LTVplus recruits every engineer it assigns and handles retention and replacement when someone leaves.
The MSP Still Owns the Runbooks New Engineers Learn From
The MSP runs the accounts. It keeps its client relationships and technical direction and writes the escalation rules and documentation every new engineer studies. It also makes the escalation calls the matrix doesn’t cover and reviews the results.
LTVplus asks MSPs to have four things ready on day one of onboarding:
- Environment documentation for each client the engineer will support
- The escalation matrix, including severity definitions and client-specific exceptions
- Ticket categories and the priorities attached to them
- The SLA terms the MSP already reports to its clients
If the client documentation or escalation rules are incomplete, a new engineer can have a harder time routing tickets correctly. And with fewer Tier 1 tickets to learn on, that engineer has fewer chances to find out what the documents missed.



