What is Service Level Agreement (SLA)?
A Service Level Agreement (SLA) is a documented commitment between a service provider and a customer that defines the expected level of service using measurable targets such as response time, resolution time, and uptime. It specifies how performance is tracked, who is responsible, and what remedies apply if the agreed targets are not met.
How an SLA works
An SLA turns vague expectations into specific, measurable obligations. It typically covers the scope of services included, the performance targets the provider commits to, the method and frequency of measurement, and the consequences if targets are missed. SLAs can be external (between a company and its customers) or internal (between departments, often called an OLA, or Operational Level Agreement). Because everyone works from the same agreed definitions, an SLA reduces disputes and creates a shared standard for accountability.
Common SLA metrics
SLAs are built around a handful of measurable commitments:
- Response time — how quickly the provider acknowledges a request or incident.
- Resolution time — how long it takes to fully resolve the issue.
- Uptime or availability — the percentage of time a service is operational, often expressed as “99.9%”.
- First-time fix rate — the share of issues solved on the first visit or contact.
Availability is a simple ratio: uptime divided by total time, expressed as a percentage. Each metric usually carries a defined threshold and a measurement window (for example, monthly), so compliance can be calculated objectively.
Response time vs resolution time
These two are constantly conflated, and they are the most common source of SLA disputes.
| Response time | Resolution time | |
|---|---|---|
| What it measures | How quickly the provider acknowledges the request and starts work | How long until the issue is fixed and the customer is operating again |
| Clock starts | Ticket raised | Ticket raised |
| Clock stops | Someone takes ownership | Service restored |
| Dominated by | Staffing levels, routing, out-of-hours cover | Diagnosis, travel, parts availability |
They fail for different reasons, so they need different fixes. A four-hour response commitment is a rostering problem. A next-day resolution commitment is a logistics and expertise problem — and no amount of faster acknowledgement will rescue it.
Committing to one and reporting on it as though it covered the other is how providers end up with excellent SLA dashboards and unhappy customers. The related trap is mean time to repair, where the “R” can mean repair, recovery, respond or resolve — agree which clock you mean before it goes in a contract.
Does a remote fix count as meeting the SLA?
This is a live commercial question for any service organization adopting remote support, and it is usually left unanswered.
Many SLAs were drafted assuming an on-site visit, so they promise that an engineer will attend within a window rather than that the issue will be resolved. Under that wording, resolving a fault remotely in twenty minutes can technically breach an agreement that a two-day site visit would have satisfied.
If remote resolution is part of how you deliver service, say so in the contract: define whether a remote session satisfies the response obligation, whether the customer can decline it, and how it is evidenced. Getting this right also makes lower-cost service tiers viable in geographies where dispatch was never economic — see field service KPIs for how service delivery cost shapes contract economics.
Benefits of a well-defined SLA
A clear SLA aligns expectations before problems arise. It gives customers confidence in the service they are buying, gives providers a defensible standard to operate against, and gives both sides an objective basis for measuring performance. SLAs also support continuous improvement: tracking targets over time surfaces recurring bottlenecks and shows where processes or staffing need to change.
Common pitfalls
SLAs fail when targets are unrealistic, unmeasurable, or disconnected from what customers actually value. Setting an aggressive resolution time without the tools or staff to meet it invites breaches and penalties. Vague language (“prompt response”) is unenforceable. And measuring the wrong thing — optimizing response time while resolution quality slips — can make the numbers look good while customer satisfaction falls. Good SLAs are specific, achievable, and reviewed regularly.
How VSight helps
Meeting resolution-time SLAs depends on how quickly your team can diagnose and fix an issue. VSight AR remote assistance connects an on-site technician’s camera view to a remote expert who guides the repair in real time with AR annotations, so problems get resolved faster and often without a second visit — directly supporting response and resolution targets. VSight Workflow adds digital work instructions, SOPs, checklists, and task management so procedures stay standardized and repeatable. As a connected worker platform, VSight is GDPR, HIPAA, and ISO 27001 certified.
Worth being precise about which part of the clock this affects: remote assistance compresses response and diagnosis — an expert can be looking at the asset in minutes rather than after a travel window — but it does not compress parts lead time. If your resolution-time breaches are dominated by waiting for a component, that is an inventory problem and should be tracked separately.
See how VSight can help your team hit its service targets — request a demo.
Related terms: field service KPIs, field service management, first-time fix rate, MTTF and MTTR, technician utilization rate, field service.
Frequently asked questions
What is a Service Level Agreement (SLA) in simple terms? A Service Level Agreement (SLA) is a documented commitment between a service provider and a customer that defines the level of service expected, such as response time, resolution time, and uptime. It sets measurable targets, how they are tracked, and what happens if they are missed.
What is the difference between an SLA and a KPI? An SLA is a contractual commitment the provider must meet, often with penalties for failure. A KPI is an internal performance metric a team uses to measure and improve its own operations. SLA targets are frequently measured using KPIs, but not every KPI is written into an SLA.
What happens if an SLA is breached? When an SLA target is missed, the agreement usually defines remedies such as service credits, refunds, escalation procedures, or in serious cases the right to terminate the contract. The specific consequences depend on the terms negotiated between the provider and the customer.
How can a company improve its SLA compliance? Companies improve SLA compliance by setting realistic targets, tracking performance continuously, standardizing procedures, and resolving issues faster. Tools that speed up diagnosis and repair, such as remote assistance and digital work instructions, help teams stay within response and resolution windows.
What is the difference between response time and resolution time? Response time measures how quickly the provider acknowledges the request and begins work. Resolution time measures how long until the issue is actually fixed and the customer is operating again. They are separate clocks with separate causes: response time is a staffing and routing problem, while resolution time is dominated by diagnosis, travel and parts availability. An SLA that commits to one says nothing about the other.
Does a remote fix count as meeting an SLA? Only if the contract says so. Many SLAs were written assuming an on-site visit, so they specify an engineer attending rather than the issue being resolved. Service organizations adopting remote support should decide explicitly whether a remote resolution satisfies the response obligation, and reword the agreement if it does — otherwise a faster remote fix can technically count as a breach.