Escalation rules automatically take action on tickets that match specific conditions.
In the admin panel (/support/admin/escalation-rules), define rules with:
- Name — Rule identifier
- Trigger Type —
time_basedorcondition_based - Conditions — Array of conditions to match
- Actions — Array of actions to execute
- Order — Execution priority (lower = first)
- Is Active — Enable/disable the rule
| Field | Operator | Description |
|---|---|---|
status |
equals | Match specific status |
priority |
equals | Match specific priority |
assigned |
equals | 'unassigned' or 'assigned' |
age_hours |
greater_than | Hours since ticket created |
no_response_hours |
greater_than | Hours with no first response |
sla_breached |
equals | SLA has been breached |
department_id |
equals | Match specific department |
| Action | Value | Description |
|---|---|---|
escalate |
— | Change status to Escalated |
change_priority |
priority value | Change ticket priority |
assign_to |
agent ID | Assign to specific agent |
change_department |
department ID | Move to different department |
Auto-escalate unresponded tickets after 4 hours:
{
"conditions": [
{"field": "status", "value": "open"},
{"field": "no_response_hours", "value": 4}
],
"actions": [
{"type": "change_priority", "value": "high"},
{"type": "escalate"}
]
}A rule acts on a ticket once. The sweep records each firing in the escalated_rule_executions table and skips tickets the rule has already acted on. When a ticket stops matching (for example it is answered, resolved, or moves out of the matched status), its record is removed, so the rule fires again if the ticket matches later.
Set repeat_after_hours on a rule to let it fire again after that many hours while the ticket still matches. Leave it null (the default) to fire once. Automations follow the same rules and accept the same repeat_after_hours field.
Each ticket is handled on its own. An action that cannot apply (escalating a ticket that is already escalated, a transition escalated.transitions does not allow, an unknown priority) is skipped and logged, and the sweep continues. A rule escalation dispatches TicketEscalated once, with Escalation rule: <name> as the reason.
Add to your app/Console/Kernel.php:
$schedule->command('escalated:evaluate-escalations')->everyFiveMinutes();