The most common signs that IT support isn’t delivering are tickets that take too long to resolve, the same faults coming back, invoices that are hard to match to what was agreed, and no clear picture of how support is performing. If two or more sound familiar, you have four realistic options at renewal: renew as is, renegotiate the scope, add an internal IT lead, or change provider. We set out each one below, along with what we’d choose.

Most firms will recognise the scene. It’s Monday morning and three people can’t get into the shared drive. The ticket went in at 9am, it’s now lunchtime, and nobody has been in touch. In the meantime, someone in accounts is copying files onto a USB stick so they can keep working.

Moments like that are small on their own, but they add up to lost hours, frustrated staff and risks nobody is tracking. This article sets out seven observable signs, what each one usually means, and what good support looks like instead. It’s written for Managing Directors, Finance Directors and IT Managers at professional services firms with 20 to 100 staff, where clients expect reliability and an IT failure can quickly become a reputational issue.

Timing matters too. Most support contracts carry a notice period, and some renew automatically. Checking your renewal date now gives you time to review your arrangement properly, whether that leads to a better agreement with your current provider or a planned move to a new one.

When Support Becomes Reactive

Many IT frustrations come down to one thing: support that responds to problems rather than preventing them. It usually builds up gradually. Firms in this position tend to describe constant firefighting, problems fixed only after they’ve caused disruption, and costs that surprise them at renewal.

Each person in the business sees it differently. The Managing Director senses IT is holding the firm back but can’t pinpoint why. The Finance Director sees invoices that don’t match expectations. The IT Manager, if there is one, spends more time managing the provider than improving anything.

Reactive support isn’t always a sign of a poor provider. Sometimes the contract only covers fixing things when they break, and nobody has checked whether that still suits the business. Either way, the cost isn’t only lost productivity. The UK Government’s Cyber Security Breaches Survey 2025/2026 found that 43% of UK businesses identified a breach or attack in the previous 12 months. That figure only counts incidents businesses actually spotted, and without monitoring, some go unnoticed.

What a First Audit Usually Finds

When a business asks us to review its IT, the same issues come up time and again: laptops that haven’t had a security update in months, backups nobody has checked can actually be restored, admin passwords that only a previous supplier knows, and software licences still being paid for people who left last year. Most business owners would never think to check any of these, and nothing flags them until something goes wrong. That’s why we start new support relationships with a full audit before anything is changed.

When a server failure took the whole of facilities company D&M Group offline, Director David Goodwin found out what good support looks like when it matters:

“We were up and running again in less than an hour from Azure, with no data loss or lasting damage. They explain things in plain English, which saves so much time and means staff are comfortable calling them.”

The rest of this article will help you work out where your own support stands.

Want a quick, objective view? Download the IT Support Renewal Check and score your current support in under ten minutes.

The Seven IT Support Provider Red Flags Explained

Each sign below is something you can observe. For each one, we explain what it usually indicates and what to expect instead. One bad week isn’t a pattern, so think about the last three months rather than a single incident.

What good looks like also depends on the level of service you’ve contracted. The real question is whether your provider has offered it, explained what it costs, and delivered what you agreed.

1. Tickets aren’t answered within agreed times

The symptom: Tickets sit open for hours or days, and urgent issues wait in the same queue as a printer query.

What it usually indicates: Stretched resources or unclear priorities. Issues aren’t being triaged by business impact, or response targets aren’t being measured.

What to expect instead: Response targets set by severity and met consistently, with the figures available when you ask for them. SLA numbers look similar across most providers, so ask what actually happens when you call: who answers, how quickly, and whether they can fix it there and then. At DMS, experienced engineers often answer the phone themselves, so complex issues are frequently resolved on the first call.

2. The same faults keep coming back

The symptom: The email sync that drops every few weeks. The printer that needs resetting every Monday. The VPN that works for everyone except the one partner who travels.

What it usually indicates: Root causes aren’t being investigated. A reset fixes the immediate problem in ten minutes; finding out why it keeps happening takes longer, and nobody has been asked to do it or report on it.

What to expect instead: The underlying cause fixed, with a short note on what’s been done so it doesn’t happen again. If you ask which faults keep coming back, your provider should be able to tell you.

3. You only hear from them when something breaks

The symptom: No proactive contact. No notice of patches applied, no early warning that a disk is filling up, no regular review.

What it usually indicates: Either no monitoring is in place, or it isn’t part of what you’ve agreed. If nothing is being watched, problems are only found once someone notices them.

What to expect instead: If proactive monitoring is part of your service, you should see evidence of it: issues caught before they cause disruption, and a clear answer when you ask what was found. If it isn’t, ask what adding it would involve.

4. Invoices are hard to match to what you agreed

The symptom: Line items that were never discussed. Charges for work you assumed was included, with nobody explaining beforehand that it sat outside your contract. Licence counts that creep upward.

What it usually indicates: The scope has become unclear. Often neither side has revisited the agreement since it was signed.

What to expect instead: Costs agreed upfront and explained in plain English. Anything outside your support contract, such as project work, should be scoped and quoted before it starts, and licences should be reviewed regularly. If you suspect you’re paying for seats nobody uses, a Microsoft 365 licensing review is a good place to start.

Who notices: This one usually lands with the Finance Director. Compare your last three invoices with your contracted scope and note anything recurring that hasn’t been explained.

5. You can’t get a clear picture of performance

The symptom: When you ask how support is performing, you get either no real answer or a list of ticket IDs and uptime percentages the board can’t interpret.

What it usually indicates: Performance isn’t being communicated in a way the business can use.

What to expect instead: Information your leadership team can use, whether as a regular report or a review when you ask: response and resolution times against agreed targets, recurring issues and what was done about them, security posture and licence spend.

6. Nobody is talking about what’s next

The symptom: Nobody has asked where the business is heading. Hardware is replaced when it fails. Microsoft changes arrive as surprises.

What it usually indicates: Support is focused on day-to-day issues with no forward planning. That may be all your agreement covers, but it leaves the business reacting to change rather than planning for it.

What to expect instead: A simple twelve-month roadmap covering hardware refresh, licensing, security certification such as Cyber Essentials, and anything your clients or regulators will expect. Some firms get this through a Virtual IT Director service alongside their day-to-day support. A quick test: ask your provider what they see as your firm’s three biggest IT risks.

7. Staff have stopped logging tickets

The symptom: Ticket volumes have fallen but nothing has improved. People fix things themselves, share passwords, or email files to personal accounts to get work done.

What it usually indicates: Staff have lost confidence that raising an issue leads anywhere. Workarounds hide the real picture, and data may be ending up in places nobody is protecting.

What to expect instead: A helpdesk people are happy to use because it responds. Ticket volumes often rise when support improves, and that’s a healthy sign.

Who notices: IT Managers can test this in an afternoon by asking three colleagues what workarounds they use day to day. The answers often say more than any report.

What Are Your Options When Your IT Support Contract Is Up for Renewal?

You have four realistic options at renewal. Which one is right depends on how many of the signs above apply, and whether your provider is willing to change.

1. Renew as is. This makes sense when none of the signs apply, costs match the agreed scope and performance has been stable. It’s simple and low risk, but check the notice period and any price increase before it renews automatically.
2. Renegotiate the scope. This makes sense when one or two signs apply and your provider is open to adding monitoring, clearer visibility of performance or a roadmap. You keep the knowledge your provider already has, but costs may rise, and it only works if commitments are written down and reviewed.
3. Add an internal IT lead. This makes sense when the business has grown to the point where someone needs to own IT decisions day to day. It gives you an in-house view of priorities, but adds salary cost and still relies on a provider for depth and cover.
4. Change provider. This makes sense when several signs apply, or when your provider can’t or won’t commit to improvements. It can reset the relationship, but needs planning around your notice period and a careful handover.

What we’d choose

For most firms of 20 to 100 staff where two or more signs apply, we’d start by renegotiating with your current provider: share the evidence, agree written commitments and set a review date. A provider who already knows your systems has an advantage worth keeping, if they’re willing to improve.

We’d recommend moving if your provider can’t commit to measurable improvements, if commitments have already been made and missed, or if you can’t get your own admin access and documentation. Those are problems a contract change won’t fix.

If none of the signs apply, we’d renew. Not every working arrangement needs changing.

What a Good SLA Should Cover

Many support frustrations start with the agreement itself. A service level agreement (SLA) sets out how quickly your provider should respond to and resolve issues. It’s most useful when it covers both response and resolution, when you can see how performance measures up against it, and when it’s clear what happens if targets are repeatedly missed.

How to Review or Change Your IT Provider Without Disruption

Start with a review. Some issues can be resolved by agreeing clearer expectations with your current provider; if they can’t, a planned move avoids disruption.

1. Check your contract. Find your renewal date and notice period. Some agreements renew automatically unless you give written notice, often 60 or 90 days in advance.
2. Gather the evidence. Pull three months of tickets, response times and recurring faults, and score your support using a structured health check rather than gut feel.
3. Confirm your own access. Your provider may need admin rights to do their job, but your business should hold its own administrator account, domain registrar login, and ownership of your Microsoft tenancy and software licences.
4. Talk to your current provider. Share what you’ve found and ask for a service review. Agree specific, written commitments and a date to check progress. If you’d like an outside view before you sign a renewal, ask another provider to look it over. A discount on the same service won’t fix a service problem.
5. If you decide to move, compare at least three providers. Ask how they prevent problems, how they’ll keep you informed about performance, which accreditations they hold (ISO 27001, Cyber Essentials and Microsoft partner status are all worth asking about), and for references from firms of a similar size and sector. Make sure any proposal includes measurable SLA commitments.
6. Plan a parallel handover. A good incoming provider will audit and shadow your systems before taking over, so nothing is switched off until the new arrangement is proven to work.
7. Set 90-day success measures. Agree in writing what improvement looks like, and review progress against it from day one.

Frequently Asked Questions

What are the signs of a poor IT support provider?

The main signs are slow responses to tickets, recurring faults, unexplained charges, no clear picture of performance, no proactive contact, no forward planning, and staff working around IT instead of logging tickets. One bad week isn’t a pattern, but two or more of these over three months is worth acting on.

Should I renew my IT support contract or change provider?

It depends on how many signs apply and whether your provider will commit to improving. If none apply, renewing is sensible. If one or two apply, renegotiating the scope with written commitments is usually the better first step. Changing provider makes sense when several apply, or when commitments have already been made and missed.

How quickly should an IT support provider respond to a ticket?

A reasonable benchmark for a firm of 20 to 100 staff is a phone response within 30 to 60 minutes for critical issues and within four hours for routine requests, with on-site attendance where remote diagnosis can’t resolve the fault. More important than the numbers is whether your provider sets these targets and measures against them. If you’ve never seen how your provider performs against its targets, it’s reasonable to ask.

Is it difficult to switch IT support provider in the UK?

Switching IT support provider is usually far less disruptive than firms expect, provided it’s planned around your notice period. The incoming provider does most of the work: auditing your systems, collecting documentation and running in parallel before cutover. Most transitions for a firm of this size complete within four to eight weeks with no interruption to daily work. The most common cause of delay is credentials taking time to hand over, which is why it’s worth confirming ownership of your accounts early.

What should a managed IT provider review cover?

A good review looks at response and resolution performance against your SLA, recurring faults and their root causes, security posture, licence spend, and whether costs have moved beyond the agreed scope. It should end with a clear outcome: specific written commitments to improve the current arrangement, or a plan to move before renewal.

Where to Go From Here

Most firms already have a sense of whether their IT support is working. The tickets, the invoices and the workarounds staff have adopted usually tell the story. The next step is to turn that sense into evidence, then decide whether to improve your current arrangement or plan a move.

Checking your renewal date and notice period now gives you time to do either properly, rather than finding out after the window has closed.

Start with the evidence. Get your copy of the IT Support Renewal Check and see how your current arrangement measures up.

Renewal coming up? Before you sign it, ask us. We’ll look at your current arrangement and tell you plainly whether we’d renew, renegotiate or move. If it looks right, we’ll say so.