Skip to content

Glossary

SLA (Service Level Agreement)

In customer support, an SLA (service level agreement) is a set of time targets a team commits to, such as how quickly a customer gets a first reply and how quickly the issue is resolved. SLAs can be promised in a contract or set internally, and they are usually measured in business hours.

What is an SLA in customer support?

A support SLA turns "we reply quickly" into numbers. A typical policy sets a first response target, a next response target for each follow-up, and a resolution target. Different customers or priorities get different policies: an urgent issue from an enterprise account might get a one-hour first response, while a general question gets eight business hours.

External SLAs are written into customer contracts and can carry service credits. Internal SLAs are targets the team sets for itself. Both work the same way in the help desk.

How SLA clocks work

Most teams measure SLAs in business hours. If your team works 9 to 5 on weekdays, a message that arrives at 4:30 on Friday with a two-hour target is due at 10:30 on Monday, not 6:30 on Friday. Holidays are excluded the same way.

Clocks also pause when the ball is in the customer's court. If you've asked a question and are waiting for an answer, the time they take shouldn't count against you.

Setting SLAs you can keep

Base targets on what the team achieves today, then tighten them. The SLA compliance calculator works out your attainment from your own numbers. A target you miss every week teaches the team to ignore it. Report attainment by policy and by team, and look at what happens after a miss: a reply ten minutes late is a different problem from one two days late.

Act before the breach, not after. An approaching-breach alert that reassigns or escalates the conversation saves more SLAs than a report at the end of the month.

SLAs in Quackback

Set a default SLA and it applies to every new conversation, on every plan. It carries the targets you choose and needs no workflow. Clocks follow your office hours, with weekly windows per timezone and one-off or yearly holidays, and pause while a conversation is snoozed or waiting on the customer. Tickets add their own time-to-resolve clock.

On Business and up you can create SLA policies with different targets by team, customer or priority, and build workflows that start when an SLA is approaching breach or has breached: reassign it, raise the priority or post a note. The inbox shows a countdown on each conversation, and the SLA report shows attainment by policy and a breach heatmap.

Common questions

What does SLA mean in customer support?

An SLA is a set of time targets a support team commits to, such as first response time and resolution time. It can be promised in a customer contract or set as an internal target.

Which targets should a support SLA include?

Most start with first response time and resolution time. Next response time, the wait after each customer reply, catches conversations that go quiet after a fast first answer. In Quackback, an SLA policy can set first response, next response and time to close, plus time to resolve for tickets, on Business and up.

Should every conversation get the same SLA?

Rarely. Most teams set shorter targets for urgent issues or larger customers and longer ones for general questions. In Quackback, you keep several named SLA policies, and a workflow applies the right one to each conversation or ticket.

Have another question? Talk to the team.

Run support and feedback in one place