A managed IT help desk should commit to two separate numbers, not one: how fast a technician responds to a ticket, and how fast the problem actually gets resolved. Most IT providers only quote the first number. The second one is the one that determines whether your team is back to work in an hour or still stuck three days later.
Ask most IT providers what they promise on a help desk ticket, and you’ll get a response time. Fifteen minutes for a critical issue, an hour for everything else. That number sounds reassuring until you notice what it doesn’t cover: whether the problem actually gets fixed.
A technician can respond in five minutes and still leave you stuck for three days. Response time measures how fast someone says hello. Resolution time measures how fast your problem goes away. Businesses evaluating managed IT support should be asking about both, and most don’t know to ask about the second one until they’ve already been burned.
Response time: the easy promise to make
Every MSP will quote you a response SLA, usually tiered by priority. A server outage gets a faster commitment than a single user’s printer issue. That tiering makes sense. What matters is what “response” actually means in the contract. Does it mean a human looked at the ticket and started working? Or does it mean an automated email went out confirming receipt? Those are very different things, and the second one is worth almost nothing.
Resolution time: the promise that actually matters
A resolution SLA commits to a timeframe for actually fixing the problem, not just acknowledging it. At TekNation, every ticket in our HaloPSA queue carries a resolution target tied to its priority level, and tickets approaching that target without progress trigger an internal alert automatically. You shouldn’t have to call and ask why nothing’s happened. The system should catch it before you notice. For the full mechanics of how these targets are set and enforced, see how IT ticket SLAs actually work.
Escalation shouldn’t feel like starting over
When a ticket needs a senior technician or a specialist, escalation should be internal and invisible to you. Your ticket stays open, you get a note that it’s been picked up by someone with deeper access, and the history travels with it. What shouldn’t happen: your ticket gets closed at level one and reopened at level two, forcing you to re-explain the problem to someone who’s starting from zero. That pattern is common at large MSPs that measure level one performance by how many tickets they hand off, not how many they solve. We wrote more about this specific failure mode in why offshore level one IT support fails small and mid-size businesses.
Closure requires your confirmation, not a clock
The most corrosive habit in IT support is closing a ticket automatically after a set number of days with no response, whether or not the problem is actually fixed. It looks good on a metrics dashboard. It’s useless to you if the issue is still there and you just haven’t had time to reply. A ticket should stay open until you confirm resolution, full stop.
What good escalation and resolution look like together
A mobile app breaks after a Windows update. The ticket comes in, a technician who already knows your Microsoft 365 environment picks it up inside the response window, traces it to the update push, applies the fix, and tests it on the affected device before touching the ticket status. You get a note that says it’s resolved and a request to confirm. You confirm. Done. No resubmitted tickets, no automated compliance emails for a problem someone else was supposed to fix.
Questions to ask your current provider
If you’re not sure whether your help desk is actually built this way, ask a few direct questions: What’s your resolution SLA, not just your response SLA? Who works my tickets, and do they have the access to fix things without escalating? What happens if a ticket isn’t resolved by its target time? Can I see the status of my open tickets myself, or do I have to call and ask?
If the answers are vague, that’s the answer. TekNation runs its service desk on HaloPSA with SLA enforcement, client confirmation before closure, and full ticket transparency built in. If you want to see what that looks like against your current provider’s numbers, get in touch for a free IT review.
Frequently asked questions
What’s a good response time for a managed IT help desk?
Most well-run help desks target 15 minutes or less for critical, business-down issues and under an hour for standard priority tickets. The response commitment matters less than what happens after it: whether a technician with real access starts working the problem right away.
What’s the difference between response time and resolution time in IT support?
Response time is how quickly someone acknowledges your ticket. Resolution time is how quickly the actual problem gets fixed. A provider can hit every response SLA and still leave issues open for days if resolution isn’t tracked and enforced separately.
How do I know if my IT provider is actually meeting its SLA?
Ask for visibility into your own ticket queue, including open time, priority, and target resolution date for every ticket. If your provider can’t show you that in real time, it’s a sign the SLA exists on paper more than in practice.