Zendesk Automations Dashboard Guide
Zendesk automations run in the background—closing stale tickets, sending follow-ups, escalating SLA breaches. But do you know which ones actually fire? And whether they’re helping or causing noise? This guide covers how to track automation effectiveness.
What automations do
Automations are time-based rules. Unlike triggers (event-based), automations check conditions periodically and act if conditions are met. Common uses:
- Close tickets pending for X days
- Send follow-up email after no response
- Escalate tickets approaching SLA breach
- Notify managers of aging tickets
The problem: automations run silently. You don’t see them fire unless you audit.
Why track automation performance
- Stale rules — Automations created years ago may no longer match your workflow.
- Unintended effects — Auto-close might be closing tickets customers thought were open.
- Volume impact — Follow-up automations can inflate ticket volume if customers reply to automated messages.
- Optimization — Know which automations save time so you can create more like them.
How to audit automations in Zendesk
- List active automations — Admin → Business rules → Automations. Export or screenshot the list.
- Check run counts — Zendesk shows how many times each automation ran (last 7 days). Look for zeros (dead rules) and high counts (busy rules).
- Review conditions — Are conditions still relevant? If you changed ticket statuses or tags, automations may need updates.
- Check outcomes — For each high-volume automation, sample a few tickets it affected. Did it do what you intended?
What to track in a dashboard
| Metric | Purpose |
|---|---|
| Automation fire count (7d) | Volume of each automation |
| Tickets affected by automation | Which tickets were touched |
| Outcome by automation | Did automated tickets resolve faster or reopen more? |
| SLA impact | Did SLA escalation automations prevent breaches? |
Zendesk Explore doesn’t have built-in automation reports, but you can infer from tags (add a tag when automation fires) or from Support: Tickets dataset filters.
Building a tracking system
Option 1: Add tags
For each automation, add a unique tag (e.g., auto_followup_3d). Then report on tickets with that tag.
Option 2: Use audit logs
Zendesk ticket events show when automations acted. Export and analyze in a spreadsheet or BI tool.
Option 3: Third-party
Some tools pull automation events and correlate with outcomes automatically.
Common mistakes
- Set and forget — Automations become stale. Review quarterly.
- No tagging — Without tags, you can’t report on which automation did what.
- Conflicting rules — Multiple automations or triggers acting on the same tickets. Audit for overlaps.
- Aggressive auto-close — Closing tickets too fast frustrates customers. Monitor reopen rate for auto-closed tickets.
Questions to ask in your audit
- Which automations haven’t fired in 30 days? (Consider disabling)
- Which automations fire the most? (Review for unintended effects)
- Do auto-closed tickets reopen at a higher rate? (Adjust timing or conditions)
- Are SLA escalation automations actually preventing breaches? (Correlate with SLA compliance)
FAQ
How often should I audit automations?
Quarterly is reasonable. More often if you’re actively changing workflows.
Can automations hurt customer experience?
Yes. Auto-close too soon, or follow-up emails that feel robotic, can frustrate customers. Monitor feedback and reopens.
Should I disable unused automations?
Generally yes. Dead rules clutter your admin and can confuse new team members.