The Hidden Cost of L1 Triage for MSPs

Every MSP owner knows the feeling: the ticket queue is growing, your technicians are busy, but resolution times keep climbing. The problem usually isn’t a lack of skill or effort. It’s that your L1 team spends the bulk of their day on triage — reading tickets, pulling up device records, searching documentation, and routing requests — before they ever start fixing anything.

That triage work is invisible. It doesn’t show up as a line item on your P&L. But it’s one of the largest drags on your help desk’s capacity, and it compounds in ways most MSP owners don’t fully account for.

Where the Time Actually Goes

When a new ticket hits the queue, a technician doesn’t just read it and start working. There’s a predictable sequence of steps that plays out dozens of times a day, and each one takes longer than you’d think.

Reading and Interpreting the Ticket

Most tickets arrive incomplete. The end user writes “my email isn’t working” or “the printer is down again,” and the technician has to figure out what that actually means. They’re reading between the lines, checking the sender’s history, and trying to determine urgency — all before they even open a tool.

Looking Up the Device and the User

Once the technician has a rough sense of the issue, they switch to NinjaOne or Datto to pull up the device. Then they check ConnectWise or Autotask for the client’s contract and SLA. Then they might cross-reference the user in Active Directory or Microsoft 365 to see what’s provisioned. That’s three or four tool switches just to establish context.

Searching Documentation

If the client has a specific configuration or a known workaround for this type of issue, it’s probably documented somewhere — ITGlue, a SharePoint folder, a pinned Slack message. The technician has to know where to look and spend time searching. Often, the documentation exists but doesn’t get found at the right moment.

Categorizing and Routing

After all that context-gathering, the technician decides whether they can handle the ticket or need to escalate. They update the ticket type, priority, and sub-category in ConnectWise. If it needs to go to L2 or a specialized team, they write up a summary of what they’ve found so far and reassign it.

This entire cycle — read, research, contextualize, categorize, route — takes anywhere from 5 to 15 minutes per ticket. Multiply that by 30 or 40 tickets a day across your L1 team, and you’re looking at a significant portion of your payroll going toward work that never directly resolves a problem.

The Costs You Don’t See on the Invoice

The direct time cost is easy enough to calculate. But the real damage from manual triage is harder to measure because it shows up indirectly.

Slower Resolution Times

When triage takes 10 minutes and the actual fix takes 5, your SLA clock is burning on context-gathering, not problem-solving. Clients don’t see the difference — they just see that it took 15 minutes for a 5-minute fix.

Technician Burnout

Repetitive, low-autonomy work is draining. Your best technicians didn’t get into IT to copy-paste device serial numbers between tabs all day. When the majority of the workday is spent on rote triage rather than meaningful problem-solving, people check out — or leave. And replacing a trained technician costs far more than their salary.

Inconsistent Quality

When triage is manual, it depends on who’s working the queue. Your senior tech might catch a pattern across three related tickets. Your newest hire might miss it entirely. There’s no standardization, no guarantee that every ticket gets the same level of context before someone starts working on it.

The Growth Ceiling

This is the one that matters most. Manual triage doesn’t scale. When you add a new client, you add more tickets. To handle more tickets, you need more technicians doing the same triage loop. Your margins shrink with every new logo because the help desk becomes the bottleneck — not the services you deliver.

Most MSPs hit a point where they can’t take on new clients without hiring, and they can’t hire without the revenue from new clients. That’s the growth ceiling, and manual triage is one of the biggest contributors.

What 30-40% of a Technician’s Day Looks Like

Let’s put real numbers on it. If an L1 technician works an 8-hour day and spends 35% of that time on triage activities, that’s roughly 2 hours and 48 minutes — every single day — spent on tasks that don’t directly resolve an issue.

For a team of five L1 technicians, that’s 14 hours of triage per day. Over a month, it’s roughly 280 hours. At a blended cost of $30 per hour, you’re spending $8,400 per month on reading tickets, switching between tools, and routing requests.

That’s $100,000 a year — not on solving problems, but on getting ready to solve problems.

And those numbers assume a steady ticket volume. During onboarding, security incidents, or seasonal spikes, triage time balloons further because every new ticket still requires the same manual research loop.

Why This Problem Persists

MSPs have tried to optimize triage for years. Ticket templates, triage checklists, better categorization schemes — these all help at the margins, but they don’t change the fundamental loop. A human still has to read the ticket, open multiple tools, gather context, and make a routing decision.

Automation rules in ConnectWise or Autotask can handle some categorization, but they’re brittle. They break when ticket subjects don’t match expected patterns, and they can’t pull context from NinjaOne, ITGlue, and Microsoft 365 the way a technician can.

The problem persists because triage is inherently a cross-system, judgment-based task. It requires pulling data from multiple sources, synthesizing it, and making a decision. Until recently, that was something only a human could do.

What Changes When Triage Happens Automatically

AI is changing this equation — not by replacing technicians, but by handling the context-gathering and categorization steps that consume most of their triage time.

When a ticket arrives, an AI-powered triage system can instantly pull the relevant device information from NinjaOne, check the client’s documentation in ITGlue, look up the user’s provisioning in Microsoft 365, review historical tickets in ConnectWise, and classify the request by type and priority. All of that context lands on the technician’s screen before they even open the ticket.

The technician still makes the call. They still review, approve, and act. But instead of spending 10 minutes gathering context, they spend 30 seconds reviewing it. The human judgment stays. The manual research disappears.

That shift — from technician-as-researcher to technician-as-decision-maker — is what unlocks the growth ceiling. Your existing team handles more tickets, responds faster, and spends their time on work that actually requires their expertise.

The Triage Tax Is Optional

Every MSP pays the triage tax today. It’s baked into your labor costs, your resolution times, and your growth constraints. But it doesn’t have to be.

The first step is understanding where the time actually goes. If you haven’t mapped out your technicians’ triage workflow — every tool switch, every documentation search, every categorization decision — do that this week. The numbers will probably surprise you.

The second step is deciding whether you want your most expensive resource (trained technicians) spending a third of their day on work that a system can handle in seconds.

Ready to see how AI can handle triage for your team? Start with Junto and give your technicians their time back.