Slow IT Support and Constantly Chasing Tickets? Here's What a Reasonable Response Actually Looks Like

If you spend more time chasing your IT provider than they spend fixing your problem, something in that relationship has stopped working. When tickets regularly sit untouched, the support line often goes to voicemail, or an engineer promises to call back and doesn't follow through, that's not a run of isolated bad days. For a growing business relying on its systems every working hour, slow support is itself the warning sign, whether or not anything has actually broken yet.

The risk is obvious: every hour a ticket sits unanswered is an hour your business is exposed, whether that is a member of staff locked out of the system they need for a client meeting, or a security alert nobody has looked at yet. The opportunity is just as real. A provider that actually measures, publishes and holds itself to clear response times turns support from a source of frustration into a measurable part of how resilient your business is.

Do you actually know how long your provider should take?

Most businesses have never been told what a reasonable response time looks like, so they have no benchmark to judge their current provider against. The first useful question to ask is not "are they slow?" but "slow compared to what?"

A well-run IT support desk does not treat every ticket the same. It triages by impact: an outage stopping the whole office working is a different problem to one person's printer. Good providers set this out as a priority framework, often built on the long-established ITIL approach to IT service management, where the most severe, business-wide incidents get the fastest guaranteed response and continuous work until resolution, while lower-impact requests are scheduled sensibly rather than left to drift. The detail that matters is not a specific number of hours, because a credible figure depends entirely on what has broken and how many people it affects. What matters is whether your provider has actually defined tiers like these for your business, in writing, and can tell you without hesitation which one your last ticket fell into and why. The one standard worth holding any provider to is that a genuinely critical, business-stopping issue is triaged in under 15 minutes: that does not mean fixed in 15 minutes, but it means someone has looked at it, understood what it is, and started treating it with urgency, rather than you discovering where you sit in the queue only when something goes wrong.

Have you actually got this in writing?

A verbal assurance that "we'll sort it quickly" is not a service level agreement. An SLA is a written, contractual commitment, and if you cannot point to a document stating your provider's response and resolution targets, you do not actually have one, no matter what you were told at the sales stage.

A proper SLA should set out, in plain terms: response times and resolution targets by priority level; the hours it covers, and what happens if something breaks outside them; who you escalate to if a ticket is not progressing, by name, not just "the helpdesk"; what the provider owes you if they miss their own targets, whether that is a credit, a review, or at minimum an honest explanation; and how often your service gets reviewed together, rather than running on autopilot. If your current contract is silent on all of this, that silence is itself useful information about how your account is actually being managed.

Are they marking their own homework?

Even a provider with a written SLA can fall short of it, and most businesses only discover this by living through the slow responses themselves, rather than seeing the numbers. The honest question to ask is: how would you actually know if your provider hit their targets last month? If the only answer is that they tell you they did, you are relying on self-reporting from the very party being measured.

A provider confident in their own performance will show you the real data: timestamped logs from their ticketing system showing when a ticket was raised, first responded to and resolved, not a summary written after the fact. Ask for this as a standing report, not a one-off. Independent signals help too. Cyber Essentials certification, the UK government-backed cyber security standard, tells you a provider's baseline controls have been externally assessed rather than self-declared, and a provider willing to be measured against a recognised external standard is generally more willing to be measured against their own SLA as well. A published status page or client portal showing live ticket status is another good sign: it means the numbers are visible to you in real time, not produced only when you ask.

Quick answers, for when you just want to know

How quickly should IT support respond to a ticket? It depends on the priority of the issue, not a single fixed number. A business-critical outage should get a fast, guaranteed response, with continuous work until it's resolved, and a genuinely critical issue should be triaged in under 15 minutes even if the fix itself takes longer. Lower-priority requests can reasonably be scheduled in order, with a realistic timescale communicated upfront. The specific targets should be agreed and written into your contract, not assumed.

What should an IT support SLA include? Response and resolution targets by priority level, hours of cover, a named escalation path, what happens if targets are missed, and a regular service review.

How do I know if my IT provider is actually hitting their SLA? Ask for real, timestamped ticket data rather than a verbal assurance, and look for independent signals such as Cyber Essentials certification or a live status portal.

Where this leaves your Technology Resilience Score™

Slow, unverifiable support is not just an irritation. It stretches the window in which a small problem can become a serious one, and it makes it harder to trust that the rest of your IT estate, backups, security monitoring, patching, is actually being looked after as promised. That is a real risk to your Technology Resilience Score™. The opportunity sits right alongside it: a provider with clear, written, independently checkable response times is also, in our experience, the kind of provider who takes the rest of your resilience seriously too.

If you are tired of chasing your own IT provider, you do not need to take our word for whether that is a problem worth fixing. Start with a clear, independent picture of what you are actually paying for, and whether a proper written response standard is even part of it: our free IT Investment Check benchmarks what you pay against what a business your size should be investing, and what that money should actually be buying you. From there, the free Technology Resilience Score™ assessment goes further and shows you exactly where the rest of your setup stands too. Related reading: five signs your IT provider has stopped caring, your MSP just got acquired, now what?, and switching IT provider without the downtime.

Check your IT investment in a few minutes, no obligation. Start your free IT Investment Check.