A support SLA dashboard that shows risk, not just history
A support SLA dashboard should show whether you’re meeting your SLA targets (e.g. first reply within 4h, resolution within 24h) and where breach risk is—before you miss. This guide covers what to put on that dashboard and how to use it, with links to the glossary for definitions.
What is an SLA in support?
In support, an SLA (service level agreement) is usually a target for first response time and/or resolution time (e.g. “90% of tickets get a first reply within 4 business hours”). SLA compliance is the percentage of tickets that met the target; SLA breach by priority breaks that down so you see which priorities or segments are at risk. For definitions, see the glossary.
What to put on an SLA dashboard
- Compliance rate — Percentage of tickets that met the SLA in the period (e.g. first reply within 4h). Compare to last period so you see trend.
- Breach risk — Tickets that are close to breaching (e.g. open 3.5h with a 4h first-reply SLA) so you can act before they miss. See SLA breach by priority if you track by priority.
- Breakdown — By group, tag, or priority so you see where breaches or risk concentrate.
- Path to tickets — When compliance drops or risk spikes, you need to open the list of tickets that breached or are at risk so you can triage.
For the full set of support KPIs (including volume, backlog, first reply, resolution, reopens), see support metrics dashboard and support ops metrics.
Breach risk vs compliance rate
- Compliance rate — Tells you how you did in the past (e.g. “last week we hit 92%”). Useful for reporting and trend.
- Breach risk — Tells you what’s about to breach now (e.g. “12 tickets are within 30 minutes of first-reply SLA”). Useful for real-time triage.
A good SLA dashboard shows both: compliance over time and a view of current risk so you can escalate or reassign before the clock runs out.
How to report SLA in Zendesk
Zendesk has SLA policies and metrics; Explore (or your plan’s reporting) can report on SLA compliance and breach. For first reply and resolution definitions and reporting, see first reply time in Zendesk and Zendesk resolution time report. Use business hours in your SLA and reports so the numbers match.
When to escalate (and when to fix process)
- Single ticket at risk — Reassign or escalate that ticket.
- Many tickets at risk in one segment — May be a capacity or routing issue in that group or tag; fix process or add coverage there.
- Compliance dropping over time — Volume may have grown; check backlog and ticket volume and consider capacity or triage. See reduce first response time for levers.
FAQ
What’s the difference between SLA compliance and first reply time?
First reply time is the metric (e.g. median 3.2h). SLA compliance is the % of tickets that met a target (e.g. “first reply within 4h”). You report both: the metric for trend, the compliance for “did we hit the target?” See SLA compliance and first response time.
Should we track SLA by priority?
If your SLA differs by priority (e.g. high = 2h, normal = 4h), then yes. Use SLA breach by priority and break down your dashboard by priority so you can triage the right tickets.
Where does SLA fit in our weekly review?
After volume, backlog, first reply, resolution, and reopens. See support dashboard template and support ops metrics for the full order.