What SLA metrics can I monitor?

Zendesk SLA policies track four metrics: first reply time, next reply time, resolution time, and agent work time. Each metric has separate targets for business hours and calendar hours. Most teams prioritize first reply time and resolution time for breach alerts.

How far in advance should I alert before a breach?

Alert at least 1 hour before breach for standard tickets and 2 hours for high-priority tickets. This gives agents enough time to respond or escalate. Avoid alerting too early (4+ hours) — agents tune out alerts that feel premature.

What happens after an SLA breach?

Zendesk marks the SLA target as breached in reporting and the ticket's SLA indicator turns red. There's no automatic action — breaches are tracked for reporting purposes. Use the approaches in this recipe to add proactive actions like Slack alerts and priority escalation.

Do I need SLA policies set up before using this recipe?

Yes. SLA policies must be configured in Zendesk first (Admin Center → Objects and rules → Service level agreements). Define response and resolution targets per priority level. Without active SLA policies, there are no breach times to monitor.

How to alert Slack before a Zendesk SLA breach

Why alert before SLA breaches?

SLA breaches are preventable — but only if your team knows they're coming. By the time a ticket breaches its SLA, the damage is done: you've missed your response commitment, reporting takes a hit, and the customer's frustration has compounded.

Proactive Slack alerts when tickets approach their SLA deadline give agents a window to act. A first-reply-time warning 30 minutes before breach means the difference between a timely response and a missed commitment. Over time, breach prevention also surfaces capacity issues — if the same time slots or ticket types consistently approach breach, you know where to add staffing.

What you'll get

#sla-warnings

SLA Monitorapp9:41 AM

⏰ SLA Breach Warning — 22 min remaining

Ticket: #63104 — Unable to export reports since update

Requester: Lisa Wang (Acme Corp)

SLA Target: 2h first reply (1h 38m elapsed)

Priority: High

Assigned: Unassigned

View in Zendesk →

What you'll need

Prerequisites

Zendesk account on a plan that supports SLA policies (Professional plan or above)
SLA policies configured in Admin Center with response and resolution targets
Slack workspace with a channel for SLA alerts (e.g., #sla-warnings)
(For n8n/code approaches) Zendesk API credentials: subdomain, agent email, API token
(For n8n/code approaches) Slack Bot Token with chat:write scope

Choose your approach

Select an approach below to see the full step-by-step guide.

Troubleshooting

Compare approaches

Approach	Complexity	Cost	Latency	Code	Reliability
Zendesk Automation	low	$0 (included)	real-time	none	24/7 cloud
n8n	medium	$0-24/mo	polling	low	24/7 cloud
Agent Skill	low	Usage-based	scheduled	medium	On demand
Claude Cowork	low	Usage-based	scheduled	none	On demand

Zendesk Automation

low

Cost: $0 (included)

Latency: real-time

Code: none

Reliability: 24/7 cloud

n8n

medium

Cost: $0-24/mo

Latency: polling

Code: low

Reliability: 24/7 cloud

Agent Skill

low

Cost: Usage-based

Latency: scheduled

Code: medium

Reliability: On demand

Claude Cowork

low

Cost: Usage-based

Latency: scheduled

Code: none

Reliability: On demand

Frequently Asked Questions

How to alert Slack before a Zendesk SLA breach

Why alert before SLA breaches?

What you'll need

Choose your approach

Troubleshooting

Compare approaches

Zendesk Automation

n8n

Agent Skill

Claude Cowork

Zendesk Automation

n8n

Agent Skill

Claude Cowork

Related Recipes

How to send Slack alerts for low Zendesk CSAT scores

How to alert Slack when a VIP customer creates a Zendesk ticket

How to auto-triage and tag Zendesk tickets with triggers

How to send CSAT surveys after ticket resolution in Gorgias and alert Slack on low scores

Frequently Asked Questions

Need help implementing this?