An IT support contract should make things clearer for your business, not leave you wondering what happens when something goes wrong.
Yet two agreements described as “Managed IT Support” can cover very different things.
One may include day-to-day helpdesk support, proactive monitoring, patching, Microsoft 365 administration and regular planning. Another may provide little more than access to technical support when somebody reports a problem.
The monthly price therefore tells you very little unless you understand what sits behind it.
Whether you are reviewing an existing provider, approaching a renewal or comparing a new proposal, there are several areas worth checking before you make a decision.
Helpdesk and user support
Start with the service your employees are most likely to use.
How do they request help? Is there a ticketing system, telephone number and email address? What hours are covered? How are urgent incidents prioritised?
The agreement should also make clear whether user support is genuinely included in the monthly charge or whether there are allowances, thresholds or additional charges.
Response and resolution are different things too.
A provider may respond quickly to acknowledge an issue without necessarily resolving it immediately. A good agreement should explain the service expectations clearly enough for a non-technical business owner or manager to understand them.
Monitoring and preventative maintenance
Managed support should normally involve more than waiting for somebody to report a fault.
Ask which devices and systems are monitored, what alerts the provider receives and what routine maintenance takes place.
This might include operating system updates, patching, device health monitoring and reviewing warnings before they become larger problems.
J700's current Managed IT Support service, for example, describes proactive monitoring, regular scheduled maintenance and alerting as part of its approach. J700 Group
That does not mean every technical problem can be prevented. It does mean the support relationship should include some effort to reduce avoidable disruption rather than simply responding after something breaks.
Microsoft 365 administration
For many businesses, Microsoft 365 is now central to email, files, Teams, identities and day-to-day collaboration.
Do not assume all Microsoft 365 administration is automatically included in an IT support contract.
Clarify who handles new users, leavers, licences, password and MFA issues, permissions, security settings and general Microsoft 365 support.
It is particularly important to know what is considered routine administration and what would be treated as a separate project.
Cybersecurity responsibilities
Security is one of the areas where unclear responsibilities can create real gaps.
Ask who is responsible for endpoint protection, patching, MFA, email security, account security, alert monitoring and employee awareness.
Some security products may quite reasonably be separately priced.
The important thing is that the business understands who is responsible for each area rather than assuming something is being managed when it is not.
Backup and recovery
Having a backup product and having a managed recovery arrangement are not necessarily the same thing.
Your agreement should help you understand:
what data is backed up
how frequently it is protected
who monitors failed backups
how long data is retained
what happens when something needs restoring
whether recovery work is included or chargeable
Microsoft 365, cloud systems, servers and local data may all have different protection arrangements.
The question to ask is not simply “Do we have backups?”
It is “If something important disappeared tomorrow, who would recover it and what would happen next?”
New starters and leavers
As a business grows, onboarding and offboarding become regular IT tasks.
A managed agreement should explain what happens when somebody joins or leaves.
That may include creating or disabling accounts, assigning licences, configuring devices, applying security policies and setting the correct access permissions.
The process should also make clear what information the customer needs to provide and how much notice is required.
Onsite support
A large amount of IT support can now be delivered remotely, but some issues still require somebody to attend the premises.
Clarify whether onsite support is included, restricted to particular circumstances or charged separately.
Businesses with multiple sites should also understand which locations are covered.
J700 currently provides remote and onsite support across Lancashire, Greater Manchester and the wider North West from its Rossendale and Bury teams. J700 Group
Projects and changes
One of the most common misunderstandings in managed support is the difference between day-to-day support and project work.
Installing a new server, moving office, migrating a major application or carrying out a large Microsoft 365 project may reasonably sit outside the monthly support charge.
The agreement should explain how project work is identified, approved and priced.
That helps prevent an apparently inexpensive contract from producing regular unexpected charges.
Hardware and software
Ask who is responsible for recommending and supplying devices, network equipment and software.
You should also understand whether the provider manages warranties, equipment lifecycle information and replacement planning.
A managed IT relationship should ideally make it easier to plan technology spending rather than waiting for equipment to fail before discussing replacement.
Reporting and regular reviews
Good IT management needs some form of ongoing conversation.
That does not necessarily mean pages of technical statistics every month.
For many SMEs, a useful review is more practical: recurring problems, ageing devices, security priorities, upcoming renewals, projects, business changes and decisions that need planning.
The purpose is to connect the technology to what the organisation is trying to achieve.
Exclusions matter just as much as inclusions
One of the most useful parts of any support agreement can be the exclusions.
What is not covered?
Does the provider support every piece of software? What happens with third-party applications? Are home devices included? Is out-of-hours support separate? Are major projects chargeable?
Clear exclusions are not necessarily a negative.
They allow both sides to understand the service and avoid disagreements later.
Do you know when your contract renews?
Finally, check the renewal date and notice period.
Do not wait until a few days before renewal to decide whether the service is still right for your business.
Knowing several months in advance gives you time to review recurring problems, understand the current scope, speak to your existing provider and compare alternatives if necessary.
It also reduces the risk of simply rolling an arrangement forward because there was no time to consider it properly.
Before you compare prices, compare the service
The lowest monthly figure is not automatically the least expensive option for the business.
Slow support, repeated problems, unclear security ownership, unexpected charges and poor planning can all create costs elsewhere.
Before comparing providers, make sure you are comparing like with like.
Look at what is included, what is excluded, how proactive the service is, where responsibilities sit and whether the arrangement still fits the business you have today.
Want a clearer view of your current IT?
If reviewing your IT support contract has raised questions about your wider setup, J700's Free IT & Cyber Security Review provides a structured way to look at areas such as security, resilience, access, devices, Microsoft 365 and continuity.
It is designed as a conversation starter rather than a technical scan or certification. J700 Group