Every MSP leader knows the feeling. Tickets are piling up. SLAs are slipping. The team seems overwhelmed despite recent hires. The instinct is to blame volume, too many tickets, not enough techs.
But here's what the metrics miss: the problem often isn't how many tickets you're handling. It's what happens before anyone touches them.
The Invisible Queue
When a ticket arrives at your help desk, what happens next?
In most MSPs, it lands in a shared queue or goes to a dispatcher. Someone needs to look at it, understand what it is, figure out who should handle it, and make an assignment. Only then does the actual work begin.
This seems reasonable. It's how help desks have always worked.
But consider the math. If your dispatcher takes an average of 12 minutes to route a ticket—and that's optimistic when they're also answering phones and handling escalations, and you process 150 tickets per day, that's 30 hours of queue time. Every day. Before anyone even starts troubleshooting.
For tickets with 1-hour SLAs, you've burned 20% of your response window on logistics.
The Cascade Effect
Triage delays don't exist in isolation. They create problems that multiply.
When tickets wait for assignment, several things happen simultaneously. Clients experience silence - they've reported an issue and have no idea who's working on it or when to expect contact.
Your dispatcher is making rapid-fire decisions with incomplete information, increasing the odds of misrouting. And your technicians start their day reacting to whatever finally lands in their queue rather than working systematically.
The misrouting problem is particularly expensive. A ticket assigned to the wrong technician doesn't just delay resolution. The wrong tech spends time reviewing the issue before realizing they can't help. They reassign it, adding their notes (helpful) and confusion about ownership (not helpful). The correct technician now has to parse through multiple notes and potentially conflicting information.
One bad routing decision creates 2-3x the work.
Why Hiring Doesn't Fix This
The natural response to an overwhelmed help desk is to add headcount. But if the bottleneck is triage, more technicians just means more people waiting for tickets to be assigned.
You can't hire your way out of a process problem.
This is why some MSPs with larger teams still feel understaffed while smaller, operationally-focused MSPs handle similar volume with less chaos. The difference isn't capacity - it's flow.
What Actually Helps
The MSPs that escape the queue-time trap share a few characteristics:
-
They've defined what good triage looks like. Not just "get tickets to techs" but specific routing logic: this type of issue goes to this skill set, this client tier gets this priority, this complexity level requires this experience.
-
They've eliminated single points of failure. If one person getting sick or taking lunch destroys your triage process, you have a structural problem.
-
They've automated what can be automated. Not everything requires human judgment. A password reset ticket doesn't need a dispatcher to contemplate the optimal assignment. Routine routing should be instant.
-
They measure triage as a distinct metric. Time-to-assignment is different from time-to-resolution. If you don't track the former, you're blind to one of your biggest efficiency levers.
The Question Worth Asking
Before you post another job listing or approve another overtime request, ask this: What's happening in the first five minutes after a ticket arrives?
If the answer involves waiting, deciding, re-routing, or hoping the dispatcher isn't too busy, you've found your bottleneck.
The good news is that bottlenecks have solutions. Triage is a solvable problem. The MSPs that figure this out don't just improve SLA compliance, they create capacity that enables growth without proportional headcount increases.
For a complete framework on building a triage system that scales, download our guide: Ticket Triage: The First Five Minutes That Define Everything.
Your tickets are waiting. Your SLAs are ticking. The question is what happens in those first five minutes.