SLA Examples for Customer Support: Response and Resolution Times by Priority

"We reply quickly" is not a promise a customer can hold you to, and it is not a target your team can hit. A support SLA turns it into numbers: how fast you respond, how fast you resolve, and what happens when you are about to miss.

TL;DR

• A support SLA sets two clocks per ticket: first response time and resolution time.
• Define three or four priorities by business impact, not by how loudly the customer asks.
• Chat and WhatsApp need faster first responses than email, because customers are waiting live.
• Count business hours, pause the clock while you wait on the customer, and escalate before the breach.
• Start with targets you hit 90% of the time. Tighten them once you do.

What is an SLA in customer support?

A service level agreement (SLA) is a commitment about how quickly support responds to and resolves requests. Internally it is a set of targets your help desk tracks on every ticket. For business customers it can also be a written promise in the contract.

Every support SLA rests on two measures:

• First response time (FRT): time from the customer's first message to the first human reply. An automatic acknowledgement does not count.
• Resolution time: time from the first message to the issue being solved and the ticket closed.

How to define priorities

Priorities should describe impact, so any agent picks the same one:

• Urgent: the customer cannot operate or cannot pay. A system is down, an order is stuck, money is at risk.
• High: a key feature or order is broken for this customer, but there is a workaround.
• Normal: a question or problem that affects the customer but not their business today.
• Low: how-to questions, feedback, feature requests.

Write one example ticket under each priority in your team guide. It removes most of the guesswork.

SLA example 1: a small team on business hours

Good for teams of two to ten covering weekdays, mostly via email and WhatsApp:

• Urgent: first response 1 hour, resolution 4 business hours.
• High: first response 4 business hours, resolution 1 business day.
• Normal: first response 1 business day, resolution 3 business days.
• Low: first response 2 business days, resolution 5 business days.

SLA example 2: chat-first support

When customers reach you through website chat and WhatsApp, they are often waiting with the conversation open. First response targets should be much shorter, while resolution can follow the priority table above:

• Live chat: first response within 2 minutes during business hours.
• WhatsApp: first response within 15 minutes during business hours.
• Social messages: first response within 1 hour.
• Email: first response within 4 business hours.

Outside business hours, be honest: an away message that says when you open, or an assistant that answers from your help articles and creates a ticket, beats a fake "an agent will be with you shortly". We wrote about why in What "An Agent Will Be With You Shortly" Really Means.

SLA example 3: tiered by customer plan

If you sell to businesses on different plans, link the SLA to what they pay:

• Standard plan: the small team targets above.
• Premium plan: half the first response times, plus urgent tickets covered on weekends.
• Enterprise plan: a named account manager, urgent first response within 30 minutes around the clock, and a monthly SLA report.

Only promise round-the-clock coverage if someone is actually on call.

The rules that make an SLA fair

• Count business hours for business-hours teams. A ticket sent at 9 pm on Friday is not four hours late at 1 am.
• Pause the clock while the ticket is waiting on the customer, and restart it when they reply.
• Measure from the first message, not from when someone opened the ticket.
• Report the share met, not the average. "92% of urgent tickets answered within 1 hour" is honest. An average hides the customers who waited all day.

How to actually meet your SLA

Targets only work when something happens before the deadline:

1. Show what is due next. Agents should see every ticket due in the next few hours on one view, not discover breaches in a report.
2. Escalate automatically. When a ticket nears its deadline, raise the priority, notify a lead or reassign it.
3. Route correctly from the start. Category and department routing means the ticket reaches someone who can solve it, not someone who forwards it.
4. Cut volume with self-service. Every question your help centre answers is one fewer ticket on the clock.

QuiQ Help Desk tracks response and resolution deadlines by priority, shows tickets due in the next 8 hours on one strip, and escalates automatically before a breach. If you are just getting started, read how to set up a help desk for a small business first.

What to review each month

• Share of tickets meeting first response and resolution targets, by priority.
• The ten tickets that breached worst, and why.
• Satisfaction ratings for tickets that met the SLA versus those that missed it.

If a target is met 99% of the time with room to spare, tighten it. If it is met less than 80% of the time, the target, the staffing or the routing needs to change.