How Long Should an IT Ticket Actually Take?

Most businesses have an agreed response time with their IT support. Very few could actually tell you what it is. Fewer still could tell you whether it is being met, or whether anyone outside their own IT provider is checking.

That gap matters: if nobody in your business knows the target, there is no way of judging whether your support is good, average, or quietly getting worse month by month. The risk is that a slipping ticket sits unnoticed until it becomes a real problem: a new starter locked out on day one, a security alert nobody has actioned. The opportunity sits right alongside it. A business that knows its own numbers and checks them turns IT support from a guessing game into something it can actually manage, and that is a meaningful part of its Technology Resilience Score™. The free assessment benchmarks exactly this against businesses your size in under ten minutes. Get your free Technology Resilience Score.

What should you actually expect?

There is no single correct number of hours or minutes, because a reasonable response time depends entirely on what has broken and how many people it affects. A good support desk does not treat a locked-out laptop the same as an office-wide outage. It sorts incoming tickets by impact, usually into a small number of priority levels, and sets a different expectation for each one.

As a rough benchmark to measure your own provider against: a critical, business-stopping issue should be picked up and actively worked within minutes, not hours. A high-priority issue affecting one person or team should get a same-day response. Routine requests, a software install, a new user setup, should be scheduled with a realistic date, not left open indefinitely. If your provider cannot describe their own version of this framework without checking, or cannot tell you which tier your last ticket sat in, that is useful information in itself. For a deeper look at what a properly written response standard should cover, see our breakdown of what a reasonable response actually looks like.

Do you actually know your own numbers?

Before judging whether your IT support is slow, it is worth checking whether you can even answer the basic questions. Three are worth asking this week, not eventually: Do you have a contract or service agreement that states response times in writing, rather than something you were told once at the sales stage? Do you know which priority level applies to your most recent ticket, and whether it was met? And has anyone other than your provider ever looked at the actual timestamps, rather than taking their word for it?

If the honest answer to any of those is no, you are not alone. Most growing businesses never had this conversation when they first took on IT support, because nobody flagged it as something to ask about. That is not a reason to feel behind. It is simply the starting point for putting a proper benchmark in place.

The signs that slow has become the norm

Slow service rarely arrives all at once. It creeps in, and teams adjust without noticing. A few signs worth watching for: nobody chases an update any more because nobody expects one; "sorry for the delay" has become a stock phrase rather than an apology; staff have quietly started working around IT issues themselves instead of logging them, which hides the real scale of the problem; and a ticket's priority seems to depend on who shouts loudest rather than what it has agreed to be measured against. None of these show up in a single bad week. They show up when you compare how your team talks about IT support now to how they talked about it a year ago. That drift is also the opportunity: catch it early with a straightforward conversation about the numbers, and it stays a five-minute fix instead of becoming the reason a critical ticket gets missed.

Is anyone actually checking?

A provider telling you they hit their targets is not the same as proving it. The honest check is whether you can see real, timestamped ticket data, not a verbal assurance after the fact, and whether your provider is independently assessed against a recognised standard such as Cyber Essentials, rather than only grading their own homework. We cover exactly how to ask for that evidence, and what a provider confident in their own numbers should be willing to show you, in this companion piece.

Quick answers

How long should an IT ticket take? It depends on priority, not a single number: a critical, business-stopping issue should be actively worked within minutes, a high-priority single-user issue within the same working day, and routine requests on a realistic, agreed date. The specific targets should be written down, not assumed.

What counts as a critical IT ticket? Generally anything that stops the whole business working, or anything with a security dimension, such as a live breach or a locked-down system. A good provider will have already defined this with you rather than deciding case by case.

Does every ticket need the same response time? No. Treating every request identically either slows down genuine emergencies or wastes urgency on routine work. A tiered approach, agreed in writing, is what a properly run support desk looks like.

Where this leaves your Technology Resilience Score™

Not knowing your own numbers is not a small admin gap. It makes it harder to trust that the rest of your IT, backups, security monitoring, patching, is being looked after as promised, and that is a real factor in your Technology Resilience Score™. The opportunity is straightforward: businesses that benchmark their support properly tend to be the ones whose whole technology estate is in better shape, because they have made a habit of actually checking rather than assuming.

You do not need to guess where you stand. The free Technology Resilience Score™ assessment takes under ten minutes and benchmarks your IT support, and the rest of your technology estate, against businesses your size. Start your free assessment.