Routing & Automation
Part of Support routing and automation
Escalating an unassigned ticket automatically
Define the unassigned state, escalation clock, recipient and stop condition before automating overdue ticket alerts.
Escalate a ticket when it stays without an individual owner beyond an agreed interval. Send the alert to a monitored person or team. Stop the rule once the case is claimed or enters a separately monitored escalation stage. Keep an unassigned-ticket view so work stays visible if an alert fails.
Define the eligible tickets and clock
A ticket can belong to a group with no agent assigned. Decide whether the rule covers those tickets, tickets with no group, or both. Exclude finished cases and waiting states that genuinely need no assignment, using conditions that match the team's workflow.
Choose the clock that answers the problem. Age since creation covers new intake. A transferred ticket may need time since transfer if the system records and exposes that event for rules. A customer reply on an existing case may need a separate coverage path.
Specify calendar or staffed hours in the team's policy. Check what the selected rule type actually supports.
Rule element / Choice to record
- Eligible work
- Active ticket without an individual owner
- Threshold
- Agreed age and supported time condition
- Recipient
- Named queue lead or staffed fallback team
- Stop
- Assignment or a separately monitored escalation stage
- Follow-up
- Person responsible for checking that the case was accepted
These are proposed choices, not default product settings. An email sent to an empty assignee field cannot serve as the escalation.
Allow for hourly processing and limits
Zendesk automations run hourly, though not at an exact minute. They require an action that makes a qualifying condition false, or a condition that can be true only once. A continuing ‘unassigned for longer than’ condition with only a notification action is unsuitable because it can keep firing.
Freshdesk hourly rules run every hour and execute when conditions match. Examples include sending unattended tickets over 48 hours to agents and assigning long-overdue tickets to an Escalations team.
Freshdesk says hourly rules act on tickets created or updated in the last 30 days; tickets inactive beyond 30 days will not be impacted. An old, idle ticket therefore needs a separate queue review. Check the account's available conditions and actions before choosing a stage field or bounded time window.
Hourly Automation Rules: Zendesk vs Freshdesk
- Execution frequency
- Hourly (Zendesk), every hour (Freshdesk)
- Trigger scope
- Tickets created or updated in the last 30 days (Freshdesk only)
- Action requirement
- Must include action that changes condition state (e.g., assignment)
- Support for continuous conditions
- Not suitable for ongoing 'unassigned for longer than' with only notification
Check whether the escalation worked
Use safe sample cases: a ticket claimed before the threshold, one still unassigned, one assigned to a group but not an agent, and one already resolved. Inspect the rule log, recipient and resulting owner. Check the next hourly cycle for a repeat alert. An escalation is complete when someone accepts the next action, not merely when the system records a send.
