SLA.
aka service level agreement, service commitment, uptime guarantee
The promise, in writing: how good the service will be, and what happens if it isn't.
What it actually means
An SLA, or service level agreement, is a written commitment between a provider and a customer that defines how a service will perform, using measurable targets like uptime, response time or delivery time. It also spells out how performance is measured and what the customer gets, often a credit or refund, when the provider misses the target.
You will see SLAs anywhere one party relies on another to keep something running. A cloud company promises a system will be available 99.9% of the time each month. An IT help desk promises to answer urgent tickets within one hour. A logistics partner promises next-day delivery for most orders. Inside a company, teams sometimes write internal SLAs too, like finance promising to pay approved invoices within five working days.
The nuance people miss: an SLA is a floor, not a forecast. It is the minimum the provider is willing to be held to, so the real service is usually better most of the time. The other thing to check is the remedy. Many SLAs only pay out a small service credit, not your actual losses, and you often have to claim it yourself within a deadline. Also notice the small print on what counts: scheduled maintenance is frequently excluded from the uptime math.
Where you'll hear it
Their SLA says four hours to respond on a priority one ticket, but nothing about time to fix. I want a resolution target in there before we sign.
Translation: replying fast is not the same as solving the problem. She wants the contract to promise an actual fix, not just an acknowledgment.
Also in customer support dashboards, where tickets turn red when they are about to breach the SLA; in cloud and software contracts, next to uptime percentages and credit tables; and in outsourcing deals, where an SLA report is reviewed every month and repeated misses can give the customer the right to exit the contract.
The pop-culture version
You order something online and the checkout page says it arrives in two days. That line is a promise with a measurable target. You know exactly what success looks like, and you will notice instantly if day three comes and the box is not at your door.
Now read what happens if it is late. Maybe the app gives you a small voucher, or refunds the delivery fee. It rarely pays for the party you needed the item for. And if a storm closes the roads, the fine print usually says the promise does not apply. That is an SLA in miniature.
Businesses sign the same kind of promise, just with bigger numbers. The target is the two days, the measurement is the tracking data, the exclusions are the storm clause, and the remedy is the voucher. When you read an SLA, look for all four pieces, not just the headline number.
The practical rule: an SLA is only as useful as its measurement and its remedy. Before you trust the headline number, ask how it is measured, what is excluded, and what you actually get when it is missed.
Say it like you mean it
“The vendor breached the response SLA twice this month, so I've logged both and requested the service credits.”
It names which SLA was missed, keeps a record and uses the remedy the agreement actually provides.“We have an SLA with them, so they have to cover whatever this outage cost us.”
Most SLAs cap the remedy at a credit or partial refund, so assuming full compensation usually leads to disappointment.You will often hear SLO and SLI nearby. An SLO, or service level objective, is the internal target a team aims for, usually stricter than the SLA. An SLI, or service level indicator, is the actual measurement, like the percentage of successful requests.
A comparison of leading incident management tools in 2026, covering pricing, features and how they help teams respond to outages and meet service targets.
Decoded next
Decoded by the Kurums editorial team. Kurums Decoded translates the language of business for people who are new to it. Definitions are kept short on purpose; the serious version above goes deep. Nothing here is financial, legal or career advice.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.
