Response Time Is Not Resolution Time for Managed IT Support
Your provider answered in twelve minutes. Your team was still down at 10am. Both statements can be true, and the gap between them is where support contracts quietly fail.
When you assess managed IT support services, the first number you hear is usually response time: how quickly someone answers the phone or acknowledges a ticket. That number matters, but it says very little about when work resumes. Response, acknowledgement, resolution and restoration are four separate things, and only some of them carry a clock.
This tutorial unpacks what an agreement should actually commit to. We open with the twelve minute answer and the 10am problem, then separate those four words that are not synonyms. From there we examine why an unclocked promise is just marketing, what a P1 priority tier should genuinely guarantee, how after-hours cover is worded, and which exclusions quietly cancel the promise. We also cover escalation paths, the unfair contract terms regime that now reaches small business standard-form agreements, and a five-question checklist for your next negotiation.
By the end, you will read a support agreement the way it deserves to be read: by what has a clock attached.
The Twelve Minute Answer and the 10am Problem
Twelve-minute answers and 10am outages can both be true, which is why response time says little about recovery.
Response measures the provider’s first action on your ticket, not your business being back up. A fast clock and a slow recovery can both comply with the same clause. The practical test for any managed IT support services agreement is not the headline figure, but whether every promise carries a definition, a clock start rule, a clock stop rule, and a stated consequence. That standard holds whether you are weighing in-house IT versus Sydney managed providers or renegotiating an existing contract, and it applies too to the real scope of what a managed provider actually does. General information on Australia’s unfair contract terms regime appears near the end of this guide. It is not legal advice; have a lawyer review your specific agreement rather than this article.
Four Words That Are Not Synonyms: Response, Acknowledgement, Resolution and Restoration
The mismatch starts with vocabulary. Four terms are used interchangeably in sales conversations but mean different things in a contract.
Response is the provider’s first human action on your ticket, through a named channel: phone, portal chat or email. If the clause counts an automated reply, it is not measuring a person picking up your problem.
Acknowledgement is the ticket system saying it received the request. Ask whether that auto-reply starts the clock. Many short response targets are met by software, never by a technician.
Resolution means the root cause is fixed so the fault does not recur. This clock decides whether next week repeats this week, and it deserves its own target rather than being folded into response.
Restoration, or a workaround, means service is usable again, sometimes temporarily. Incident management’s stated primary objective is to return the service to users as quickly as possible, not the same as fixing it (IT Process Wiki). This is the number your staff experience, so it deserves the same precision as response.
When you compare managed IT support providers, ask each to state in writing its target for all four events, per priority tier. A single response figure collapses them into one flattering number.
Why an Unclocked Promise Is Just Marketing
A promise with no clock attached is not a commitment. A real one names a target number, a rule for when the clock starts and stops, and a stated consequence for missing it. Anything missing one of the four is an aspiration wearing a commitment’s clothes.
Watch for wording such as “we aim to respond promptly”, “best endeavours will be used”, or “targets are indicative only and do not form part of this agreement”. Each sounds like a promise without pinning the provider to anything you can hold it to.
The Miss Is Where the Commitment Lives
Ask what happens on a miss: a service credit, automatic escalation, a right to terminate, or a line in a monthly report. If the last is your only remedy, price the risk accordingly.
Clock rules matter more than target numbers. Whether time pauses outside business hours, while the provider waits on you, or while a third party is engaged determines whether the target is ever reachable.
Ask for the commitment in writing before you sign. In managed IT support services, a provider that will not put a target into the agreement has told you how it intends to administer it.
Priority Tiers: What a P1 Should Actually Commit To
With the clock rules settled, the next question is which clock applies to your outage. Write tier definitions in your language: how many users are affected, whether a workaround exists, whether revenue has stopped, and whether it is one desk or an entire site. Put classification in the agreement too: who assigns severity, how quickly you are told, and how you dispute it. Wording such as “provider determines severity at its sole discretion” leaves your outage sitting in someone else’s queue.
Each tier needs a pair of clocks, one for response and one for restoration, with the tightest restoration commitment on the highest tier. That is where a P1 earns its name. Check the top tier’s scope: only systems the provider hosts, or also your internet connection, cloud hosting, line of business software and staff devices? Look for the managed IT support services schedule that names covered systems, and apply the same discipline to cloud capacity planning with a two-year sizing worksheet. Illustrative wording to compare against: “P1 covers a full business outage or more than 30 percent of staff unable to work, with restoration the same business day.” Treat it as a template, not a benchmark.
After-Hours Cover: The Detail That Decides Whether Anyone Answers
Priority tiers only work if someone is awake to action them. Write the covered hours precisely: start and finish times, AEST and AEDT across daylight saving, public holidays, and whether weekends are included or excluded.
Separate remote support from on-site attendance. Ask what an out-of-hours callout costs, because physical attendance is often a separate line item rather than part of the plan.
Then confirm how a 2am call arrives. The same published number, a paging service with a stated answer target, and an answering service that logs a ticket for the next business day produce three completely different outcomes.
Ask for the on-call roster and after-hours escalation numbers in writing. Ask directly whether after-hours is staffed, run on an on-call rotation, or simply not offered on your plan.
Finally, check the accounting: does after-hours work draw down prepaid hours, bill at a premium rate, or trigger a minimum charge, and how is that usage reported? If your domain, mailboxes and website sit with separate vendors, consolidating email and hosting removes a source of disputed causes before the call even happens.
Exclusions: The Clauses That Quietly Cancel the Promise
After-hours cover settles who answers at 2am. Exclusions decide whether that answer counts. Map the exclusion list against your actual stack, line by line: internet provider faults, unsupported or end-of-life hardware, software outside the managed scope, and problems traced to a change your own team made. Treat these like insurance gaps, much as you would when reviewing what cyber policies cover. Reasonable endeavours to liaise with third parties is not a restoration commitment. Ask whether your clock keeps running while the internet provider is engaged, or stops until the provider hears back. Flag catch-all causes such as any factor outside the provider’s reasonable control; the broader that phrase, the fewer real outages the promise covers. Establish the support and project boundary: how migrations, major changes and after-hours callouts are quoted, approved and billed, so a support target cannot turn into a change request. When comparing managed IT support providers, ask each for a written list of exclusions at every priority tier, then compare the lists rather than the brochures.
Escalation Paths: Who You Call, When, and What Happens Next

Once you know what is excluded, ask how a problem gets escalated. A written path needs four elements: who (a name or role), how to reach them, what triggers the step up, and what they must do once triggered. Prefer automatic triggers to goodwill. A P1 that moves to a duty manager if unacknowledged within a stated interval beats a number you must ring and argue with. Insist on auditable reporting: ticket-level data on response, restoration, missed targets and root cause, on a fixed schedule with a named reviewer. Ask about exit before you need it: notice period, handover of documentation, credentials, configurations and administrative access, and who owns configurations at term end. If you operate in a SOCI asset class, our scoping test for incident duties is worth reading before you sign.
The Legal Backstop: Unfair Contract Terms and Your IT Agreement
Escalation and exit terms are where goodwill runs out. Australia’s unfair contract terms regime extended to small business standard form contracts entered into or renewed from 12 November 2016 (Jones Day, 2017). Reforms from 9 November 2023 widened coverage: small business now means fewer than 100 employees or annual turnover under $10 million, the Consumer Law’s monetary threshold was removed while the $5 million upfront price limit still applies under the ASIC Act, and substantial penalties were introduced. A contract is presumed to be standard form unless proven otherwise; pre-printed terms with no genuine negotiation are typical. A term found unfair is void, cannot be enforced or relied on, and is cut out of the rest of the contract. Read the clauses that sit beside the service commitments: liability caps, broad exclusions and unilateral variation clauses were flagged as exposure areas (Jones Day, 2017). The ACCC’s first case concerned JJ Richards (Jones Day, 2017). Enforcement runs through the ACCC nationally, with state and territory fair trading bodies applying mirror legislation. This is background information, not legal advice, and the sources do not establish that any particular IT support clause is unfair or void. Have a lawyer assess your agreement. See our guide to the first hour of a cyber attack.
Checklist: Five Questions to Take Into the Negotiation
With the legal context established, take these five questions into the negotiation.
- Definitions and clocks. For every tier, confirm the start rule, the stop or pause rule, and targets for both response and restoration. Get all four definitions written into the agreement, not explained on a sales call.
- Consequences. Ask what happens when a target is missed: service credits, automatic escalation or exit rights. Confirm who monitors misses and how they are reported.
- Exclusions. Request the full exclusion list per tier. Get a straight answer on whether the clock stops when an exclusion is claimed, and who decides that it applies.
- Cover and escalation. Pin down business hours, time zone rules across daylight saving, the after-hours route and its cost, named contacts, automatic escalation triggers and the reporting schedule.
- Review and exit. Secure an annual review of tiers and scope, handover of documentation and credentials, and legal review where the contract is standard form and you qualify as a small business. If you are planning an IT provider switch, this checklist doubles as your transition brief.
Conclusion: Judge the Agreement on What Has a Clock Attached

With those five questions answered, the final test is simpler. Judge every promise in the agreement by one standard: is it written down, is it measurable, and does something happen when it is missed? If any part is missing, discount it. Before you sign, ask for the missing definitions, priority tiers, exclusion lists and escalation triggers in writing. A provider’s reluctance to supply them is itself part of the answer. This is general information, not legal advice.
Zectron provides managed IT services and strategic IT support from Norwest for businesses across Sydney’s Hills district, and is one provider worth putting these questions to before you commit.
Finally, diarise a review before renewal. Your systems and risk profile will change before the contract term does, and a clause that fitted last year may not fit next year.
Frequently Asked Questions
Why is a fast response time not enough to judge a managed IT support agreement?
Response measures the provider's first action on your ticket, not when your business is back up. A provider can meet a twelve-minute response target while your team is still down at 10am. The post recommends checking whether each promise has a definition, a clock start rule, a clock stop rule, and a stated consequence for missing it.
What is the difference between response, acknowledgement, resolution and restoration?
Response is the provider's first human action on your ticket through a named channel. Acknowledgement is the ticket system confirming it received the request, which may be an automated reply. Resolution means the root cause is fixed so the fault does not recur. Restoration, or a workaround, means service is usable again, sometimes temporarily. Each should have its own target per priority tier.
What makes a commitment real rather than marketing?
A real commitment names a target number, a rule for when the clock starts and stops, and a stated consequence for missing it. Wording such as "we aim to respond promptly" or "targets are indicative only" is not a binding commitment. The post also advises asking what happens on a miss, such as a service credit, automatic escalation, or a right to terminate.
What should a P1 priority tier guarantee?
Each tier needs a pair of clocks, one for response and one for restoration, with the tightest restoration commitment on the highest tier. The post suggests defining tiers by factors such as how many users are affected, whether a workaround exists, whether revenue has stopped, and whether it is one desk or an entire site. It also recommends checking whether the top tier covers only provider-hosted systems or also internet, cloud, line-of-business software and staff devices.
What should I check about after-hours support?
Write out the covered hours precisely, including time zones across daylight saving, public holidays, and weekends. Separate remote support from on-site attendance and ask what an out-of-hours callout costs. Confirm whether after-hours is staffed, run on an on-call rotation, or not offered on your plan, and ask how after-hours work is billed.
Is your business protected?
Get a free cyber risk scan and see what attackers can see about your business. It takes about two minutes, with no obligation.
Prefer to talk? Call 1300 133 770 or book a 15-minute call.




