Slow IT support
IT support feels slow. Here’s how to find out why.
Slow support is usually a symptom of something specific. Name it, raise it plainly, and most of the time it gets better. Here’s how to work out what’s going on.
The hard part
What slow support really costs
Waiting on IT costs your people hours, and nobody tracks those hours.
-
What it costs you
Every stalled request is someone who can’t do their job, often for longer than anyone notices.
-
What it feels like
You stop reporting small problems because it doesn’t seem worth the wait.
-
Why it shouldn’t be this way
Support should be predictable: you know how requests are handled and where each one stands.
Diagnosis
What you notice, and what’s usually behind it
Most slow support traces back to one of a handful of causes. Find yours before you decide anything.
-
Replies come quickly, but nothing gets fixed
The first reply is fast, and the actual fix waits in a queue.
What to ask for Two measures, not one: how long until someone responds, and how long until it’s resolved.
-
A new person every time
Nobody on their side is assigned to your account.
What to ask for A named engineer and account contact who know your setup.
-
You can’t tell what’s open
Requests live in someone’s inbox instead of a tracking system.
What to ask for A place where you can see every open request and what it’s waiting on.
-
Urgent and routine wait in the same line
The agreement doesn’t separate urgent issues from routine ones.
What to ask for Written commitments, with urgent issues held to a different standard.
-
Everyone calls someone different
Requests reach them five different ways, from five different people.
What to ask for One way to submit requests, and one person on your side who owns IT.
The last row is worth checking honestly. Sometimes the fix is on your side of the relationship.
What to do
How to raise it
-
Write down three examples.
Dates, what happened, and how long it took. Specifics get a response. General frustration gets reassurance.
-
Ask for a meeting, not a ticket.
Bring your examples and the table above. Ask which of those causes they think applies.
-
Agree on what changes, in writing.
A named contact, a way to see open requests, or clearer priorities. Whatever you agree, write it down.
-
Give it a month.
If things improve, you’ve kept a relationship that works. If they don’t, you’ll know it’s time to look at a change.
If you get there, here’s what a good handover looks like.
Who we are
How we keep support from feeling slow
We built our support around the causes in that table. A small team that knows your account, commitments written into the agreement with urgent issues separate from routine, every request tracked where you can see it, and a named person to escalate to from day one.
Named people
You’ll know your engineer and account contact by name.
Written commitments
Urgent and routine are handled to different standards, in writing.
Nothing hidden
Every request is tracked, and you can see where it stands.
A name to escalate to
You know who that is on day one, not during a crisis.
Where to start
Where to start
The choice is yours.
- Want a second opinion on your current setup? Book my free IT risk review →
- Comparing providers? Questions to ask before you sign →
- Already decided to change? What a good handover looks like →
What success looks like
Support you can predict.
And stop chasing.
- You know who’s working on your request.
- You can see where every request stands.
- Urgent problems are treated as urgent.
Questions about slow IT support
What’s a reasonable response time for IT support?
Whatever is written in your agreement, split by urgency. If nothing is written down, that’s the first thing to fix.
Is it worth talking to our provider before changing?
Yes. Most slow support has a specific cause, and a direct conversation with examples often fixes it. Changing providers is a bigger step, so try the conversation first.
How do we raise it without souring the relationship?
Bring specifics, not frustration. Dates and examples turn a complaint into a problem you can solve together.
What if our own process is part of the problem?
It often is. One way to submit requests and one person who owns IT on your side speeds up almost any provider.
When is it time to change providers?
When you’ve raised it with examples, agreed on changes, and a month later nothing is different.
How do you handle urgent issues?
Our agreements separate urgent issues from routine ones in writing, and you have a named person to escalate to from day one.
Want a second opinion?
Book a free IT risk review and we’ll look at how your support is set up, whatever you decide. Or start with a few questions about your tech.