To set up case escalation rules in Salesforce, open Setup, type Escalation Rules in Quick Find, create a rule, add rule entries (criteria), then attach escalation actions that auto-reassign the case and notify users after a set age. Only one case escalation rule can be active per org at a time, and cases escalate through a periodic background process rather than the instant a threshold is crossed.
Key takeaways
- Path: Setup > Quick Find > Escalation Rules (Service area). Keep only one rule active at a time.
- Rule entries are evaluated in sort order — the first matching entry wins, then evaluation stops.
- Escalation actions (up to 5 per entry) set the Age Over time, auto-reassign to a user or queue, and notify recipients.
- The escalation clock can ignore business hours (24/7) or run only during a chosen Business Hours record.
- "Set escalation times based on" controls when the timer starts: case created, created (disabled after first modification), or most recent modification.
- Escalation runs as a background batch, so a case escalates shortly after its age threshold, not the exact second.
What are Salesforce case escalation rules?
A case escalation rule automatically escalates a Case that is not resolved within a defined time threshold — for example, reassigning an untouched high-priority case to a senior queue after a few hours and emailing the support manager. Escalation rules belong to Service Cloud and are the standard, fully supported way to enforce response and resolution SLAs without writing code.
A rule is made of a few nested parts:
| Component | What it does | Limit |
|---|---|---|
| Escalation rule | Top-level container for the logic | Only one active case escalation rule per org |
| Rule entry | An ordered row of criteria; first match wins | Multiple entries per rule, processed by sort order |
| Criteria / formula | Conditions a case must meet (field/operator/value or a formula) | Filter logic supported |
| Escalation action | What happens on match (Age Over, reassign, notify) | Up to 5 actions per rule entry |
Escalation rules are most useful once cases are flowing in from channels like Web-to-Case and On-Demand Email-to-Case, and they sit firmly in Service Cloud rather than Sales Cloud.
How do escalation rules relate to assignment and auto-response rules?
Salesforce runs three separate case rule types, and they fire at different moments. Escalation rules only act on cases that are still open after time passes.
| Rule type | When it runs | What it does |
|---|---|---|
| Assignment rules | On case create or edit | Route the case to the right owner or queue |
| Auto-response rules | On case create | Email an acknowledgement to the contact |
| Escalation rules | Periodically, after creation | Escalate cases that breach a time threshold |
Plan all three together so a case is first assigned, the customer is auto-acknowledged, and only unresolved cases get escalated.
How do you set up a case escalation rule, step by step?
Step 1: Create the escalation rule
Go to Setup, enter Escalation Rules in Quick Find, and open Escalation Rules (under the Service section). Click New, give the rule a name (for example, "Standard Case SLA"), tick Active, and Save. In Salesforce Classic this lived under Setup > Build > Customize > Cases > Escalation Rules. Because only one rule can be active at a time, activating a new rule deactivates the previous one.
Step 2: Add rule entries (criteria)
Open the saved rule and click New under Rule Entries. Enter a Sort Order — the sequence Salesforce evaluates entries in, stopping at the first match. Then define the criteria with either Run this rule if the criteria are met (field, operator, value, plus optional filter logic) or formula evaluates to true. Example: Case Priority equals High AND Status not equal to Closed.
Step 3: Set the business hours behaviour
Decide whether the escalation clock counts only during working hours. Define the hours first under Setup > Quick Find > Business Hours.
| Business hours setting | Escalation clock behaviour |
|---|---|
| Ignore business hours | Clock runs 24/7; cases can escalate any time |
| Use business hours set on the case | Clock runs only during the case's own Business Hours |
| Set business hours | Clock runs only during the Business Hours record you pick |
Step 4: Choose what the escalation age is based on
The Set escalation times based on option controls when the timer starts and stops:
| Option | Timer starts | Timer stops / resets |
|---|---|---|
| When the case is created | At case creation | When the age threshold is reached |
| When created, disable after first modification | At case creation | As soon as the case is first modified |
| Based on most recent modification | At the last modification time | Resets on each further modification |
Step 5: Define the escalation actions
Save the entry, then add escalation actions (up to five). For each action, set Age Over — the time (in hours and minutes) after which an unresolved case escalates — then choose Auto-Reassign Case to a user or queue and Notify the new owner and any email recipients with a template. Stagger multiple actions (for example, notify at 1 hour, reassign at 4 hours) to build a tiered SLA.
SELECT CaseNumber, Subject, Priority, Status, IsEscalated, CreatedDate, LastModifiedDate
FROM Case
WHERE IsEscalated = true
AND Status != 'Closed'
ORDER BY CreatedDate ASCHow do you monitor and test escalations?
Escalation is driven by a background process that runs on a schedule, so a case escalates a few minutes after it crosses the threshold — not the exact second. To make escalations visible:
- Add the Escalated checkbox (the IsEscalated field) and any escalation date/time fields to the Case page layout and list views so agents can see escalated cases.
- Use a report or the SOQL query above to track open, escalated cases.
- To test, create a case that matches your criteria with a short Age Over (a few minutes), wait for the background job, then confirm the reassignment and notification fire.
If escalations are not firing, check that the rule is Active, the criteria actually match, the business-hours window is open, and the case is still open — closed cases do not escalate.
When should you use Flow or Entitlements instead?
Classic escalation rules remain fully supported and are the fastest way to cover simple, org-wide SLAs. For richer requirements, many teams now layer on:
- Entitlements and Milestones — track multiple response and resolution targets per case with milestone time triggers and a built-in SLA timeline.
- Omni-Channel — supervisor alerts and routing when work ages in a queue.
- Flow with scheduled paths — flexible, multi-step escalations (Slack/Teams alerts, Chatter posts, custom field updates) that go beyond reassign-and-email.
A common pattern is escalation rules for the baseline and Flow or Entitlements for tiered, channel-specific SLAs across Service Cloud channels such as Live Agent chat. If you want help designing case SLAs, routing, and automation, our Salesforce consulting team can implement it end to end.
Frequently Asked Questions
Where do I find escalation rules in Salesforce?
In Lightning, open Setup, type Escalation Rules in Quick Find, and select Escalation Rules under the Service section. In Salesforce Classic the same screen sits under Setup > Build > Customize > Cases > Escalation Rules.
How many case escalation rules can be active at once?
Only one case escalation rule can be active per org at any time. You can create many rules, but activating one automatically deactivates the others, so use multiple rule entries inside that single active rule to handle different scenarios.
Do escalated cases get reassigned automatically?
Yes. An escalation action can auto-reassign the case to another user or a queue and notify the new owner plus extra email recipients with a template. Reassignment is optional — you can escalate by notification only if you prefer.
Why isn't my case escalating immediately?
Escalation runs through a periodic background process, so a case escalates shortly after its Age Over threshold, not the instant it is crossed. Confirm the rule is active, the criteria match, the case is still open, and the business-hours window is currently open.
What's the difference between escalation rules and assignment rules?
Assignment rules route a case to the right owner or queue when it is created or edited. Escalation rules act later, escalating cases that stay unresolved past a time threshold. They are complementary: assignment decides the first owner, escalation handles SLA breaches.
Should I use escalation rules or Flow and Entitlements for SLAs?
Use escalation rules for simple, org-wide time-based escalation. Choose Entitlements and Milestones or Flow with scheduled paths when you need multiple SLA tiers, channel-specific logic, or alerts to tools like Slack. Many orgs run escalation rules as a baseline and add Flow or Entitlements on top.