Every IT support company will tell you they're reliable, responsive, and proactive. Ignore all three words, they've been used so often they've stopped meaning anything. There's really only one thing that separates a good IT support company from a bad one: whether they treat your problem as theirs to solve, or someone else's to blame.
The diagnosis trap
Here's how it usually goes wrong. Something breaks. You call for help. And instead of a fix, you get a diagnosis: that's a software issue, you'll need to speak to the vendor, or that's your internet provider's problem, not ours. Every one of those answers might be technically true. None of them are actually useful to a business owner whose systems have stopped working. You didn't call to find out whose fault it was. You called to make it stop being a problem.
Ownership isn't the same as fault
If your car broke down on the motorway, you wouldn't want the recovery driver to explain that it's actually a manufacturer defect and drive off. You'd want them to get you moving again. Good IT support works the same way. It's not that they never encounter problems outside their direct control, they do, constantly. It's that they absorb the hassle of sorting it rather than handing you a phone number and wishing you luck.
That comes with two honest caveats worth stating rather than glossing over. With software like Adobe or Sage, a good provider will get on the phone to the vendor and sort it out on your behalf wherever possible, but that only works if proper support is already in place with the vendor to begin with. No IT company, however good, can act for you with a vendor's helpdesk if that support was never bought in the first place. It's one of the few things worth paying for separately, whatever provider you use.
Hardware works a little differently. Good providers will sell machines with an upgraded warranty, three years as standard is common where it's available. When something goes wrong, a decent provider will hand over the warranty details, the number to call, and everything they've already diagnosed, but the manufacturer will still want to speak to you directly and run their own checks before they'll act. It's rarely fast. Even with next-business-day cover, manufacturers will often try a replacement part or a software fix before committing to send an engineer, so a repair can take a few days rather than one. There's no real way around that stretch, it's the manufacturer's process to own, not the provider's, and short of paying for specialist hardware support beyond servers, which most providers don't offer and charge a premium for when they do, there isn't a shortcut. Realistically, the best a provider can usually do at that point is translate the jargon and load the user's profile onto another machine, assuming a spare one's available.
Why this is rarer than it should be
Owning a problem you didn't cause is expensive. It means being the one on hold with a software vendor's support desk. It means chasing the internet provider yourself instead of forwarding on their number. It's far cheaper, in time and effort, to hand over a correct diagnosis and step back. So the market ends up full of companies that are excellent at identifying whose fault something is, and much thinner on companies willing to make it their problem anyway.
What to listen for
Next time something breaks and it turns out not to be your provider's system at fault, notice what happens next. Do they stay on the case until it's actually resolved, or does the conversation end the moment blame has been assigned? That's the whole test. Everything else is marketing language.
Whether a provider treats a problem as theirs to solve, or someone else's to blame, regardless of whose system actually caused it in the first place.
Only if proper support is already in place with that vendor. No IT company, however good, can act on your behalf with a vendor's helpdesk if that support was never bought to begin with.
A good provider will hand over the diagnosis and the warranty details, but the manufacturer will still want to speak to you directly and run their own checks, so it's rarely instant even with next-business-day cover.
Watch what happens after they discover something isn't technically their fault. A good provider stays on the case anyway rather than ending the conversation the moment blame is assigned.
Quick recap
- Every provider claims to be reliable and proactive, the words are meaningless from overuse
- The real difference is whether they treat a problem as theirs to fix, regardless of whose system caused it
- A correct diagnosis that ends the conversation isn't the same as help
- Good support absorbs the hassle of chasing other vendors so you don't have to
- Test any provider by what happens after they've worked out it "isn't their fault"
Want to know how we'd handle a problem that isn't technically ours to fix? Get in touch and ask us directly, it's a better test of us than anything on this page.