6/12/2026
SLA in IT Support: What It Actually Means and How to Verify a Vendor’s Promises
"24/7 support" on a website commits a vendor to nothing. Here’s what a working SLA is actually made of, and what belongs in the contract.
Vendors love printing SLA in bold on the homepage and almost never explain what’s actually behind those three letters. Quite a lot, as it turns out: specific, measurable commitments written into the contract — not a vague feeling of “they fix things fast."
If a commitment can’t be measured, it can’t be met or breached — which means, for the client, it means nothing beyond a nice-looking line in a sales deck.
What a working SLA is made of
The minimum working set: response time (when a specialist actually starts on the issue), resolution time by priority, coverage hours, and an escalation path for when the first line can’t resolve something on its own.
| Tier | Coverage & response |
|---|---|
| Basic | 8×5, business hours · response within 8 hours |
| Standard | 12×6 · response within 4 hours |
| Premium | 24×7 · response within 1 hour |
What "under 1 hour" actually means
This is where the sleight of hand usually happens. A one-hour response means a specialist engages with the issue within an hour — not that the issue is fully resolved within an hour. A trustworthy vendor always keeps these two numbers separate in the contract and doesn’t let the client fill in a more flattering interpretation.
Penalties for breach are the real marker of intent
An SLA with no consequences for breach is a wish dressed up as a document. A working SLA includes a concrete compensation mechanism — a reduced rate for the month, a fixed penalty, or some other financial liability for the vendor when a deadline slips. If the contract is silent on this, that silence isn’t an accident — it’s worth asking about directly, before signing, not after the first missed deadline.
How to verify it in practice
Ask the vendor for real incident-response statistics from recent months, not just promises. A company that genuinely holds itself to an SLA is usually willing to show it — because it’s already tracking those numbers internally. If there’s no data to show, it probably was never collected.
What’s promised on a website and the actual speed of response aren’t always the same thing. The difference shows up not in marketing copy, but in the contract and in the history of incidents that already happened.