Understanding IT SLAs: What You Should Expect From Your Provider
What an SLA Actually Is
A Service Level Agreement (SLA) is a commitment in your IT support agreement defining how quickly your provider will respond to and resolve different types of issues. SLAs are typically tiered — a business-down emergency has a faster response commitment than a password reset request.
Most managed IT agreements include an SLA, but not all SLAs are equally useful. Understanding what the terms mean — and what is missing — helps you evaluate whether the agreement you are signing actually meets your business needs.
Typical SLA Tiers
Priority 1 — Critical / Business Down. A system, service, or multiple users completely unable to work. Examples: server failure, complete internet outage, email system inaccessible for the whole business, ransomware attack.
*Typical SLA:* 1–2 hour response; 4–8 hour resolution target. Some providers commit to same-day resolution for P1 issues.
Priority 2 — High / Significant Impact. A major function is impaired but the business can continue with workarounds. Examples: a key application slow or intermittent for multiple users, a server degraded but still operational, internet partially working.
*Typical SLA:* 2–4 hour response; next business day resolution target.
Priority 3 — Medium / Minor Impact. A single user affected, or a non-critical function impaired. Examples: one user unable to print, one application crashing on one device, a minor configuration request.
*Typical SLA:* 4–8 hour response; 2–3 business day resolution target.
Priority 4 — Low / Request. General requests, questions, minor improvements. Examples: new software installation, user preference changes, general IT questions.
*Typical SLA:* Next business day response; best-effort resolution.
What the Fine Print Often Hides
"Response" vs "Resolution." Response time means when they acknowledge and begin working on the issue. Resolution time is when it is fixed. Many SLAs have strong response time commitments but vague resolution commitments. Look for both.
Business hours definitions. "Same business day" means nothing if the provider defines business hours as 9 am–5 pm Monday to Friday and your business runs evenings or Saturdays. Check that support hours cover your business hours.
Exclusions. SLA commitments often exclude issues caused by third-party software, issues outside the provider's control, or issues requiring hardware that must be ordered. Understand what is excluded before a crisis.
Measurement and reporting. Good providers report on SLA performance monthly — actual response times versus committed response times. If a provider cannot tell you how they are tracking against their SLA, the commitment is aspirational, not operational.
What Is Reasonable to Expect
For a small business on a managed IT agreement:
- P1 (business down) response within 1–2 hours, on-site if needed within 4 hours (for local providers)
- P3 (single user, minor issue) resolved within 48 business hours as a minimum standard
- Monthly reporting on ticket volume and SLA performance
- Proactive communication about P1 issues — you should not have to chase for updates
The Three SLA Metrics That Matter Most
IT Service Level Agreements typically include multiple performance metrics, but three matter most for small businesses evaluating managed IT providers:
Response time. How long after logging a support request does the provider acknowledge it? Response time is not resolution time — it is the first contact back, confirming the ticket has been received and someone is looking at it. For critical issues (a server down, ransomware, total outage), response within 30 minutes to one hour is reasonable. For high-priority issues (a key staff member cannot access critical systems), one to two hours. For standard issues (minor inconveniences, cosmetic problems), same business day is acceptable.
Resolution time. How long does it take to resolve the issue from first contact? Resolution time is harder to define precisely because the complexity of issues varies enormously. A well-written SLA acknowledges this: it defines target resolution times for issue categories, with escalation procedures when initial timelines cannot be met. Be sceptical of providers who promise fixed resolution times for all issues regardless of complexity.
Uptime/availability. For managed services that include infrastructure components (hosted servers, managed internet, cloud platforms), uptime SLAs specify the guaranteed availability percentage. 99.9% uptime equates to approximately 8.7 hours of downtime per year; 99.99% equates to approximately 52 minutes. For managed internet with failover, the SLA covers the combined primary + failover connection availability.
What Response Time SLAs Look Like in Practice
A typical Netluma IT managed services SLA for SE Queensland clients:
| Priority | Definition | Response Target | Resolution Target |
These targets apply during business hours (7 AM – 6 PM AEST/AEDT, Monday to Friday). After-hours support for critical issues is available via an emergency contact number.
After-Hours Support: What Small Businesses Need
Most small business IT issues occur during business hours. However, there are specific after-hours scenarios that require IT support:
Ransomware discovered outside business hours. This is the most important after-hours scenario. If a staff member discovers ransomware at 7 PM, the ability to reach IT support immediately is critical — every hour without containment means more files encrypted, more systems affected, more potential data exfiltration.
End-of-month or end-of-quarter system failures. Financial processing, payroll runs, and billing cycles often happen outside standard hours. System failures during these periods have direct financial impact.
Events and hospitality operations. Gold Coast hospitality businesses frequently operate into late evening. POS failures, payment processing issues, and connectivity problems during service need after-hours response.
When evaluating an IT provider, ask specifically about after-hours support: Is there an emergency phone number? Is it answered by technical staff or a message service? What is the after-hours response time SLA? Is after-hours support included in the monthly fee or billed separately?
SLA Reporting and Accountability
A well-managed IT SLA is measurable. Your provider should deliver periodic reports showing:
- Tickets raised in the period, by priority
- Average response time for each priority level
- Average resolution time
- SLA compliance rate (what percentage of tickets met the response/resolution targets)
- Recurring issues that may indicate underlying problems
Ask prospective providers how SLA performance is reported. If they cannot describe a reporting process, the SLA is unlikely to be actively managed.
Netluma IT provides documented SLAs with all managed service agreements and reports on performance monthly. Call 1300 521 162 to discuss what service level commitments make sense for your business.
Ready to Stop Fighting Your IT?
Proactive monitoring, unlimited remote support, and a fixed monthly price from $130/user. No surprises, no hidden fees.
Related Services