Overview
SLA breaches happen when no one is watching the clock. Zendesk's time-based automation can detect tickets approaching or exceeding your response time target and automatically escalate them — changing the priority to Urgent, reassigning to a senior agent, and sending a Slack or email alert. This creates a self-monitoring support system where critical tickets bubble up automatically without a supervisor manually checking the queue every hour.
Before you start
- Zendesk Support Team plan or higher (Automations available on all paid plans)
- Escalation team or senior agent group defined in Zendesk
- Zapier for Slack integration (optional)
Step-by-step guide (5 steps)
Define your escalation thresholds
Decide at what time thresholds tickets should escalate. Common SMB example: warn at 4 hours (no first response), escalate at 8 hours, critical at 24 hours. Set different thresholds for priority levels: Urgent tickets might escalate after 1 hour.
Create a Zendesk Automation (not a Trigger) for time-based escalation
Go to Zendesk Admin → Business Rules → Automations → Add Automation. Automations run on a schedule, unlike Triggers which fire on events. Set condition: Hours since created is greater than 4 AND Status is New AND Assignee is not set (or group is General Queue).
Automations in Zendesk run hourly. This means escalation might trigger up to 59 minutes after your threshold — build that buffer into your SLA commitments.
Set escalation actions
Set actions: Change Priority to High, Assign to group 'Escalation Team', Add tag 'sla-warning', Add comment (internal note): 'This ticket has not received a first response within 4 hours — escalating automatically'. This creates a clear audit trail.
Send a Slack alert via Zapier
Use Zapier to watch for the 'sla-warning' tag being added in Zendesk. When triggered, post a Slack message to the #support-escalations channel: 'ESCALATED: Ticket #{{id}} — [Subject] — [Customer Name] — has been waiting [X] hours. Assign here: [link]'.
Create a second automation for repeat escalation
Create another Automation for the 8-hour threshold with harsher actions: set priority to Urgent, assign to Support Manager, add tag 'sla-breach', and send an email notification to the support manager directly.
What you'll get
SLA breaches are caught and escalated before they become complaints
Senior agents handle only escalated tickets, not the full queue
Full audit trail of escalation events in ticket history
Management has visibility into breach patterns for staffing decisions
Common mistakes to avoid
Using a Trigger instead of an Automation — triggers fire on events, not time conditions
Setting escalation thresholds too low, causing constant escalations that desensitize the team
Not adding an internal note on escalated tickets — agents don't know why they received the ticket
Forgetting to reset escalation tags when a ticket is resolved, causing re-escalation
Frequently asked questions
Do I need coding experience to set up this Zendesk automation?
No coding is required. This guide walks you through everything using Zendesk's built-in features and Zapier's visual interface. If you can follow a recipe, you can follow this guide.
How long does this automation take to set up?
Most users complete this setup in 30–60 minutes on their first try. Once set up, it runs completely automatically with zero ongoing effort.
What happens if the automation fails?
Zapier and Make both have error notifications and task history, so you'll know immediately if something goes wrong. We cover troubleshooting steps in the guide above.
Can I customize this automation for my specific business?
Absolutely. The guide includes notes on common customizations. Most automations have multiple variation points — timing, conditions, notification recipients, and more.