An IT support contract’s response-time promise is usually more specific than it sounds in a sales conversation — and the specifics matter, because “fast response” means something different depending on severity, coverage hours, and whether the number refers to acknowledgement or resolution.

What you’ll learn

  • How response-time clauses are actually structured
  • What support tiers typically mean in practice
  • What to check before relying on a promised response time

Acknowledgement versus resolution

A “one-hour response” commitment usually means someone acknowledges and starts working your ticket within an hour — not that your problem is solved within an hour. These are genuinely different commitments, and a contract that’s vague about which one it’s promising is worth clarifying before you sign, not after you need it.

How tiers typically work

Most providers structure support around tiers — a standard tier might guarantee next-business-day response for routine issues; a priority tier guarantees a same-day or few-hour window, usually at higher cost. Neither is wrong; the right tier depends on how disruptive downtime actually is for your organisation, which is worth being honest about rather than defaulting to the cheapest option and hoping it’s enough.

How priority is actually decided

A well-run support operation prioritises by impact — an issue affecting multiple users or a business-critical system moves ahead of a single non-urgent request. If a provider can’t describe how they actually prioritise tickets, that’s worth probing, since it suggests tickets may just be handled in the order they arrive regardless of urgency.

The gap between promised and actual

A contractual response-time promise only holds if the provider has the staff to deliver it consistently across their entire client base, not just for you in a sales conversation. Asking how many clients or devices a provider supports per technician is a reasonable, specific question that tells you more than the response-time number itself.

What to check before relying on a number

Confirm whether the quoted time is for acknowledgement or resolution, what counts as each severity level, what coverage hours apply, and — ideally — ask for a reference from an existing client about whether promised response times actually hold in practice. See our broader piece on realistic response times for IT services in Kigali for the wider context this fits into.