An IT support agreement should remove uncertainty. It needs to explain what is covered, who is responsible, how help is requested and what happens when something serious goes wrong. A short price page is not enough: the useful detail is in the service scope, operating process and assumptions behind it.
Start with a clear service scope
List the users, sites, devices, servers, cloud services and network equipment included in the service. If printers, mobile devices, line-of-business applications or third-party suppliers are supported, say how far that support extends. A good agreement distinguishes day-to-day user help from projects, procurement and major change work.
The scope should also identify supported operating systems and any equipment that must be replaced or upgraded before it can be managed safely. This is especially important in mixed Windows, Mac and Chromebook environments.
- Named businesses, sites and supported users
- Included endpoints, servers, networks and cloud services
- What counts as routine support versus a chargeable project
- Support for third-party applications and supplier liaison
- Any exclusions, prerequisites and out-of-support equipment
Response, priority and escalation
Response time is not the same as resolution time. The agreement should define when the clock starts, the hours in which targets apply, how incidents are prioritised and how progress is communicated. Ask for examples of critical, high, normal and low-priority incidents so both parties interpret severity consistently.
It should also name the escalation route for a widespread outage, suspected cyber incident or issue that is not progressing. MSP247 averages an initial response within ten minutes, but the correct resolution path still depends on impact, cause and access to third parties.
Monitoring, maintenance and security responsibilities
Managed support usually includes more than waiting for a ticket. Check what is monitored, how alerts are reviewed, which updates are applied and what reports you receive. MSP247 uses all-platform RMM software to identify many developing issues before customers notice them. The agreement should still state what remains the customer’s responsibility, including approving change windows and maintaining appropriate insurance and policies.
- Endpoint and server monitoring coverage
- Patch and maintenance approach
- Backup monitoring and restore testing
- Security alert handling and incident coordination
- Regular service reviews and recommendations
Commercial and exit terms
Look beyond the monthly fee. Confirm minimum terms, annual changes, project rates, equipment ownership, notice periods and how licenses are handled. A professional exit clause should require an orderly transfer of documentation and access, subject to security checks and settled accounts. You should never be trapped because only the supplier understands your environment.
Review the agreement against your real environment
A reliable agreement is specific enough to set expectations and flexible enough to cope with change. Before signing, inventory your users, devices, sites, critical applications, suppliers and risks. MSP247’s free business IT review can identify support gaps and help you compare a proposed agreement with what your organisation actually needs.