SLA Explained: What Your IT Support Agreement Should Include

SLA terms decide what happens when systems fail at 10:00 AM on a busy workday. Response times sound good in sales meetings, but scope, exclusions, priority definitions, and reporting are where real accountability lives. Do you know exactly what your IT support agreement includes before you need to rely on it?

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: 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:

• Average response time: 13 minutes
• 99% of issues responded to within 1 hour
• 98% of issues 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 specifically: “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.

Where monitoring differs from support: 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.

Red Flags in IT Support Contracts

• No published SLA metrics. If a provider cannot or will not give you specific numbers, they are not confident in their performance. Ask for last quarter’s average response time in writing.
• Response defined as automated acknowledgement. Confirm that “responded” means a qualified engineer, not a ticket system confirmation.
• Vague scope definitions. Phrases like “reasonable support” or “standard business issues” leave room for disputes about what is and is not covered. Get a clear inclusion list in writing.
• Per-incident billing for included work. If every support call generates a separate invoice, your team will avoid calling for help. Unlimited support within a per-seat price removes this disincentive.
• Hidden out-of-scope charges. Ask what falls outside the agreement and how that work is handled before you sign – not when you receive an unexpected invoice.
• No regular reporting. A provider without monthly reporting is a provider without accountability. You should receive regular documentation of what happened with your IT environment.

How to Compare SLAs Across Providers

When comparing IT support providers, ask each one the same set of questions and compare the answers:

• What is your actual average response time – not your SLA ceiling?
• How do you define “responded” – automated acknowledgement or engineer action?
• What percentage of issues are responded to within one hour?
• What percentage of issues are resolved within one hour?
• Over what time period are these metrics measured?
• Can I see a sample of your monthly reporting?
• Is onsite support included in the per-seat price, or charged per visit?
• What falls outside the support agreement?

Providers who answer these questions specifically and confidently are providers who track their performance and hold themselves accountable. Providers who deflect, give ranges, or reference their contract rather than actual metrics should be evaluated accordingly.

What Is Included in Milnsbridge Plans

Every Milnsbridge plan includes SentinelOne EDR, email security, 24/7 monitoring, and patch management. Plans start at $89 per seat per month for Core. The Growth plan at $99 per seat per month adds unlimited remote and onsite support during business hours, cyber awareness training, DNS filtering, and password management (Keeper). Enhanced is $149 per seat per month.

Cloud backup ($149 per month per server), disaster recovery ($229 per month per server), Duo MFA enforcement, ThreatLocker application control, and Essential Eight uplift assessment are available as separate add-ons quoted to your specific requirements.

We operate on straightforward 12-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

1. What is your average response time, and how is it measured?
2. Is unlimited support (remote and onsite) included, or are there caps or per-visit charges?
3. What does 24/7 monitoring cover, and who responds to after-hours alerts?
4. What falls outside the agreement and how is that handled?
5. What does monthly reporting look like, and who provides it?
6. What is the agreement term and what does the annual review process look like?
7. Can you provide references from businesses of similar size in similar industries?

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.

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.