Examkin

Question

Difficulty: HardCase Automation Rules (Assignment, Auto-Response, and Escalation)

A system administrator at a renewable energy manufacturing firm is configuring Salesforce Service Cloud to automate support operations. The support manager requests that if any High Priority case remains in an unassigned or pending state for more than 4 business hours after creation, the case must automatically be reassigned to the Tier 3 Escalation Queue and the Support Director must be notified via email. The administrator attempts to implement this requirement by adding an entry with a time offset of 4 hours to the active Case Assignment Rule. Why will this configuration fail to fulfill the requirement?

  1. Case Assignment Rules evaluate criteria only at record creation or manual assignment submission and cannot execute time-delayed actions; Escalation Rules must be used for time-elapsed reassignment.Answer
  2. B
    Case Assignment Rules can only route cases to individual users, so Escalation Rules are required whenever a case must be reassigned to a Support Queue.
  3. C
    Case Assignment Rules only run for cases submitted through Web-to-Case or Email-to-Case channels, whereas Escalation Rules apply to all case origins.
  4. D
    Case Assignment Rules are evaluated after record-triggered flows in the system order of execution, which automatically cancels any pending time-based routing criteria.

Answer

Case Assignment Rules evaluate criteria only at record creation or manual assignment submission and cannot execute time-delayed actions; Escalation Rules must be used for time-elapsed reassignment.
Case Assignment Rules are designed exclusively for immediate, synchronous owner routing when a case is created or when a user checks the 'Assign using active assignment rules' checkbox during an update. They do not support time-based criteria or delayed execution offsets. To automatically reassign a case and send notifications based on the amount of time a case has remained open or unhandled, Case Escalation Rules must be configured.

Step-by-Step Solution

1
Analyze the operational business requirement.
The requirement involves monitoring elapsed time (4 business hours after creation) and performing automated actions (reassigning ownership and sending notification emails).
Time-based criteria tied to SLA compliance require automation tools designed specifically for time offsets.
2
Evaluate the capabilities of Case Assignment Rules versus Case Escalation Rules.
Case Assignment Rules specify how cases are assigned to users or queues synchronously when created or updated. They do not possess time-based triggers. Escalation Rules specifically evaluate time criteria (e.g., hours open) to reassign cases and notify users.
Using the wrong automation feature leads to failure in executing delayed logic.
3
Determine why the administrator's setup fails.
Attempting to configure a 4-hour delay within a Case Assignment Rule entry fails because assignment rules only execute synchronously upon record save.
Only Case Escalation Rules can trigger actions after a specified time threshold has elapsed.

Key Concept

Distinction between Case Assignment Rules (initial synchronous routing) and Case Escalation Rules (time-elapsed reassignment and notification).
Estimated Time:2m 0s
Rate this question

Topics

Case Automation Rules (Assignment, Auto-Response, and Escalation)

More questions from this topic