Most organisations don't go looking for managed IT support because they've developed a sudden interest in IT. They go looking because something isn't working. Issues keep coming back, nobody's quite sure who owns the problem, or the person who used to sort it has left. By the time you're reading proposals, you mostly want to know one thing: if we sign this, what actually happens on a Tuesday morning when something breaks?
That's a fair question and it's rarely answered clearly. So rather than list features, this is a walk through what a managed IT support agreement usually covers, where the edges normally sit, and how to tell whether a proposal is a genuine service or a help desk with a nicer name.
The bit everyone expects: day-to-day support
The visible half of managed IT support is the help desk. Someone can't print, a laptop won't wake up, a file's gone missing from a shared folder, Teams won't connect from home. Your people need one obvious way to report it and a realistic sense of when someone will pick it up.
What separates a good desk from an average one isn't the technology behind it. It's whether the same issues stop coming back, whether updates are written in language your team understands, and whether anyone chases the ticket that's gone quiet. Response times matter, but resolution habits matter more. Ask any provider how they handle a problem that's been reported three times by three different people.
The bit that matters more: the work you never see
The best IT support often goes unnoticed, because most of it is preventative. Behind the help desk sits a set of routines that quietly reduce how often anything reaches your team at all:
- Monitoring, so failing disks, full drives and struggling servers get flagged before they stop someone working.
- Patching and updates on a schedule, rather than whenever someone remembers or a machine nags loudly enough.
- Device management, so laptops are set up the same way and a new starter isn't a week-long project.
- User administration, including the leavers process that's forgotten far more often than anyone admits.
- Backup checks, which means confirming restores actually work, not just that a job says it finished.
- Documentation, so knowledge lives somewhere other than in one person's head.
If a proposal is heavy on response times and light on any of this, you're buying reactive cover. That can be the right call for some organisations, but it's worth knowing that's what you've bought.
What usually sits outside the agreement
Nearly every managed IT support contract has boundaries, and that's reasonable. Problems only start when nobody explains where they are. The common exclusions:
- Project work, such as office moves, server migrations, new sites or a Microsoft 365 rollout. Usually quoted separately.
- Hardware and licence costs. Support covers the looking after, not the buying.
- Third-party line-of-business applications. A provider will usually log and chase with your software vendor, but they can't fix somebody else's product.
- On-site visits beyond an agreed number, or outside normal hours.
- Anything caused by kit that's out of support. Ageing systems can often be worked around, but they change the risk and usually the price.
A clear exclusion list is a good sign. It means someone has thought about the service properly rather than hoping the edge cases don't come up.
How it's normally priced
Most managed IT support is priced per user per month, sometimes per device. Per user tends to be more predictable, because people have a laptop, a phone and occasionally a desktop, and you don't want to be counting hardware every month to work out your bill.
Watch for what's inside that number. Some agreements include security tooling, backup and Microsoft 365 administration. Others price those as add-ons, which makes the headline figure look better and the annual cost look worse. When you're comparing two quotes, the useful exercise isn't lining up the monthly rate. It's writing down the ten things you actually need and checking which of them each price includes.
Questions worth asking any provider
- Who will we speak to, and will it be the same people each time?
- What are your response times, and what happens when you miss one?
- How do you handle repeat issues, and can you show us an example?
- What's included for security as standard, and what costs extra?
- How often do you test a restore from backup, and will you show us the result?
- What does onboarding look like in the first ninety days?
- If we wanted to leave, what would you hand over and how long would it take?
That last one tells you a lot. A provider who's comfortable explaining how you'd leave is usually confident you won't want to.
Managed, co-managed, or something in between
Fully managed support suits organisations with no internal IT, or with one person who's stretched across far too much. If you already have an IT team, co-managed support is often the better fit: overflow cover for the help desk, specialist input on security, and capacity for projects that keep slipping down the list. It's the same underlying work, arranged differently, and it's worth asking about rather than defaulting to the standard package.
Where to start if you're not sure
You don't need to decide on a provider to make progress. Start by writing down the three things that frustrate your team most, and how often each one happens. That list will tell you more about what you need than any feature comparison, and it makes every conversation with a provider considerably shorter.
From there, an honest review of your support, security and Microsoft setup will tell you what's worth doing first. Some of it you'll be able to sort yourselves. Some of it will need help. Either way, you'll be choosing on the basis of what your organisation actually needs, rather than what's easiest to sell.