A support operations administrator at a cloud software company observes an issue with after-hours case handling. When high-severity cases enter Salesforce via Email-to-Case outside of standard company business hours, Case Assignment Rules successfully route them to the 'After-Hours Support Queue'. However, a Case Escalation Rule configured to reassign unassigned high-severity cases to an 'Executive Escalation Queue' after 2 hours fails to trigger overnight, only escalating several hours after business hours resume the following morning. The administrator verifies that the Escalation Rule and its rule entries are active and correctly configured. What is the most likely cause of this delayed escalation behavior?
- The Escalation Rule entry is set to evaluate case age using Business Hours, which pauses the escalation timer while the org is outside operational hours.Answer
- BCase Escalation Rules can reassign case ownership only to active individual users, causing queue-based escalation actions to fail silently.
- CAuto-Response Rules executed immediately after Case Assignment Rules and cleared the escalation clock trigger.
- DCase Escalation Rules apply exclusively to cases submitted through Web-to-Case and do not evaluate records created by Email-to-Case.
Answer
The Escalation Rule entry is set to evaluate case age using Business Hours, which pauses the escalation timer while the org is outside operational hours.
Salesforce Case Escalation Rules allow administrators to customize how case age is calculated by associating Business Hours with the rule entry or case record. When Business Hours are enabled for an escalation entry, the escalation clock only ticks during defined working hours. During non-business hours, the clock pauses entirely, causing a 2-hour escalation rule to wait until business hours resume before counting down.
Step-by-Step Solution
Key Concept
Business Hours impact on Case Escalation Rule timers