Fyncall wrote this page. The example of SLA metrics in another helpdesk links to Zendesk's own help centre, checked 19 November 2026. Details of Fyncall's SLA tracking come from the Fyncall docs, checked the same day. Example targets on this page are illustrations, not industry benchmarks.
What is an SLA in customer support?
An SLA, or service level agreement, is a promise about how fast customers will hear back and how fast their issue will be dealt with. Zendesk's help centre describes an SLA policy as an agreed measure of the response and resolution times your support team delivers.
The word “agreement” comes from contracts between businesses, where missing a target can carry a penalty. Most Shopify stores have no such contract with shoppers. For them, an SLA is an internal service level target: a goal the team sets for itself, often shown to customers as “we reply within one working day”.
Which metrics do support SLAs measure?
Most support SLAs measure how long until the first reply, how long between later replies, and how long until the issue is resolved. Each one catches a different kind of delay.
| Metric | What it measures | What it catches |
|---|---|---|
| First response time | Time from a ticket being created to the first reply from your team | New messages sitting unread |
| Next response time | Time from the customer's oldest unanswered message to your team's next reply | Conversations that stall after a quick first answer |
| Resolution time | Time from a ticket being created to it being resolved | Issues that drag on across many replies |
Helpdesks name and count these differently. Zendesk, for example, lists first reply time, next reply time, periodic update, pausable update, requester wait time, agent work time and total resolution time, and lets you choose calendar hours or business hours for each priority. Before comparing numbers between tools, check exactly when each clock starts, stops and pauses.
What is an SLA breach?
An SLA breach happens when the deadline passes without the required action, such as a first reply or a resolution. A breach is a signal to look at, not proof that the agent did something wrong.
Common causes in small ecommerce teams are easy to spot once you look:
- A spike after a sale or a courier delay, when WISMO questions arrive all at once.
- Messages arriving overnight or at weekends, measured against a clock that never stops.
- Tickets left open while waiting on a supplier, a courier or the customer.
- The wrong priority, so a routine question is judged against an urgent target.
How do you set realistic SLA targets for a Shopify team?
Start from what your team already achieves, then set targets you can meet on your busiest normal day. A target that is breached every week teaches people to ignore it.
- Measure first. Look at your current first response and resolution times for a few typical weeks, including a busy one.
- Set targets by priority. A damaged order or a payment problem deserves a tighter target than a question about gift wrapping.
- Decide which hours count. If nobody works on Sunday, either measure in business hours or set a target that allows for the weekend, and say so to customers.
- Pause the clock fairly. Time spent waiting for the customer to send a photo or an order number should not count against your team's resolution target.
- Review monthly. Read the breached tickets, fix the cause (staffing, a missing saved reply, a slow handover), then tighten targets only once you meet them comfortably.
For example, a two-person team might start with something like “Urgent: first reply within the working hour; Normal: first reply the same working day”. These are illustrations to adapt, not recommended figures.
Pair SLAs with a quality measure such as CSAT. Fast replies that do not solve anything can meet a response target and still leave customers unhappy.
How does Fyncall track SLAs?
Fyncall tracks SLA compliance for every ticket based on its priority, measuring first response time and resolution time. Ticketing with SLAs is part of the Pro plan; escalation rules are on Free (see pricing).
According to the tickets docs:
- SLA timers start when a ticket is created.
- The first response timer stops when an agent sends the first reply or comment on the ticket.
- The resolution timer stops when the ticket is moved to Resolved or Closed, and pauses while it is Waiting on Customer. It resumes when the customer responds.
- Priority (Low, Normal, High, Urgent) sets the deadlines, and changing a ticket's priority adjusts them. Reassigning a ticket does not reset the timer. The helpdesk page lists default targets of 1 hour for Urgent, 4 hours for High, 8 hours for Normal and 24 hours for Low, which you can change to suit your team.
- Each ticket shows whether it is On Track, At Risk or Breached. The SLA At Risk view lists tickets approaching or past their deadline, closest to breach first.
In the inbox, the Needs Attention queue flags a conversation as “SLA at risk” when a linked ticket's deadline is within the next hour, and conversations with breached SLAs always rise to the top. The helpdesk page shows how tickets fit with the rest of the inbox.
Common questions
What is the difference between an SLA and a KPI?
An SLA is a target for a specific ticket, such as “first reply within 4 hours”. A KPI is a broader measure you track over time, such as the share of tickets that met their SLA last month.
Should a Shopify store publish its SLA to customers?
Only if you can keep it. A simple, honest promise on your contact page, such as replying within one working day, sets expectations. Keep tighter internal targets so you meet the public one with room to spare.
Does an AI reply count towards the SLA?
It depends on the helpdesk. In Fyncall, SLAs apply to tickets, and the docs say the first response timer stops when an agent sends the first reply or comment on the ticket. They do not say whether a reply from the AI agent counts, so check how your own tool treats automated replies before relying on them for a target.
Does reassigning a ticket restart the SLA clock?
Not in Fyncall. The tickets docs say reassigning a ticket does not reset the SLA timer, so a handover between teammates does not hide a delay.