An SLA matters most when something has already gone wrong. Response times may sound reassuring in a proposal, but the real value sits in scope, exclusions, escalation rules, priority definitions, and how performance is actually measured.
If those details are vague, the agreement often protects the provider more than the client. This guide explains what an IT support SLA should include and what buyers should look for before signing.
What an SLA Actually Is
A Service Level Agreement (SLA) is a documented commitment from your IT provider about the performance standard they will deliver. In the context of IT support, the most important SLA metrics are response time and resolution time.
What an SLA is not is a guarantee that nothing will go wrong. Even the best-managed IT environments experience incidents. The SLA defines how quickly your provider will respond when something does go wrong – and that speed matters enormously for a business that depends on its systems.
SLAs are only useful when they are specific, measurable, and reported against. Vague commitments like “best efforts” or “reasonable timeframes” are not SLAs. If a provider cannot give you specific numbers, ask why – and treat the answer as a data point about how seriously they take accountability.
Response Time vs Resolution Time – The Critical Difference
These two metrics are often used interchangeably but mean very different things.
Response time is the time from when you log a ticket to when a technician acknowledges it and begins working on it. A fast response time means your issue is not sitting in a queue – someone is actively on it.
Resolution time is the time from ticket creation to the issue being fully resolved. This is harder to standardise because different issues have vastly different complexity. A password reset and a server migration are both “issues” – they have nothing in common in terms of resolution time.
When evaluating providers, ask for both numbers. Response time is the metric that reflects how a provider is staffed and how seriously they take your business. Resolution time tells you whether problems actually get solved, not just acknowledged.
Be careful with how “response” is defined. Some providers count an automated confirmation email as a response. Milnsbridge defines response as a qualified engineer acknowledging your ticket and beginning investigation – not a system-generated acknowledgement.
Milnsbridge SLA Published Numbers
Our SLA metrics measured across the previous 12 months are shown below.
- Average ticket/email first response time is 13 minutes
- 98% of P1/P2 incidents resolved within 1 hour
We publish these because we are confident in them. If a provider cannot tell you their actual average response time – not their SLA ceiling – they probably do not track it closely enough to know. Ask this directly. “What was your average response time last month?” If the answer is vague, that tells you something.
What 24/7 Monitoring Actually Means
Most managed IT providers offer “24/7 monitoring” – but what does that mean in practice?
Milnsbridge’s 24/7 monitoring means automated agents running on all managed devices and infrastructure, sending alerts directly to our service desk when anomalies are detected. Patch management, security alerts, disk health warnings, backup status, and performance thresholds are all monitored continuously – not just during business hours.
Monitoring differs from support in a practical way. Our service desk operates during business hours. Issues detected by automated monitoring outside business hours are logged and queued for immediate action when the service desk opens. For most business-hours-only organisations, this is entirely appropriate. For organisations that require after-hours human response capability, discuss the Enhanced plan options with us.
24/7 monitoring means most problems are discovered and investigated by our team before your staff notice anything is wrong. That is the operational benefit – not just knowing something failed, but catching it early enough to prevent the failure from impacting your business.
SLA Comparison Checklist
A useful SLA comparison should make the practical differences obvious before you sign. Use this table when comparing Sydney IT support providers.
| Question | Weak SLA answer | Stronger SLA answer |
|---|---|---|
| Who responds? | Automated ticket acknowledgement | Qualified engineer starts investigation |
| What is measured? | Contract ceiling only | Actual average response time and monthly reporting |
| What support is included? | Remote help only or per-visit onsite billing | Clear inclusion list with unlimited support where the plan includes it |
| How is security handled? | Security tools quoted separately after onboarding | Endpoint protection, email security, monitoring, and patching included from day one |
| What happens after hours? | No clear monitoring or escalation process | 24/7 monitoring with documented alert handling and escalation rules |
| How do you exit? | Vague handover terms | Documented ownership, credentials, and transition process |
What Is Included in Milnsbridge Plans
Core, Growth and Enhanced have different response targets and support hours. Growth includes unlimited business-hours support; Enhanced adds after-hours cover. Compare the plan inclusions and SLA targets against your business priorities.
Cloud backup ($199 per month per server), disaster recovery ($299 per month per server), Duo MFA enforcement, ThreatLocker application control, and Essential Eight transition/uplift assessment are available as separate add-ons quoted to your specific requirements.
We operate with a choice of 12-, 24- or 36-month agreements with a 10-seat minimum, serving businesses from 10 to 200 seats across Greater Sydney. Adrian Weir founded Milnsbridge in 2002 after three decades in senior IT roles at Telstra, Citibank, and Unilever. We hold a 4.9-star Google rating across 99 reviews.
Questions to Ask Before Signing an IT Support Agreement
- What are your actual response and resolution results, and which reporting period, priorities and support hours do they cover?
- Does a response mean contact from a qualified technician rather than an automated acknowledgement?
- Which remote and onsite support is included, and what allowances or per-visit charges apply?
- What does 24/7 monitoring cover, and who handles after-hours alerts and escalation?
- Which work falls outside the agreement, and how is it priced?
- Can I see a sample report showing performance, recurring issues and improvement work?
- What are the agreement term, annual price review and exit arrangements?
- Can you provide references from businesses of a similar size and industry?
If your current IT provider cannot answer these questions confidently – or if you have never thought to ask – it might be time to reassess whether your support arrangement is delivering what your business actually needs.
IT Support SLA FAQ
What should an IT support SLA include?
An IT support SLA should define response times, resolution expectations, priority levels, included support channels, onsite support rules, monitoring scope, escalation process, reporting frequency, exclusions, and exit terms. The most useful agreements also show how performance is measured each month.
Is response time the same as resolution time?
No. Response time measures how quickly a qualified technician starts working on an issue. Resolution time measures how long it takes to fix the issue. Both matter, but response time is usually the clearest indicator of how well the provider is staffed and how seriously they treat your tickets.
Should onsite support be included in an SLA?
For many Sydney businesses, yes. If onsite support is charged per visit, staff may avoid asking for help until issues become bigger. Milnsbridge includes unlimited remote and onsite support in Growth and Enhanced plans, while Core is designed for limited remote support.
How often should SLA performance be reported?
Monthly reporting is the practical benchmark. A provider should be able to show response performance, ticket volume, recurring issues, monitoring alerts, and improvement work. If they cannot report against the SLA, the SLA is mostly a sales document.
To discuss what a transparent, accountable IT support agreement looks like for your Sydney business, contact Milnsbridge. You can also review our published per-seat pricing, learn more about our managed IT services, or explore our cyber security services.
See our Sydney IT provider comparison guide for a structured approach.
