Examkin

Question

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

A support administrator at a financial services firm is troubleshooting case automation behavior. When a High-Priority case is created via Web-to-Case, the active Case Assignment Rule successfully routes the record to the 'Tier 2 Support Queue', the Escalation Rule (configured with criteria 'Case Owner equals Tier 2 Support Queue') escalates the record after two hours of inactivity, and the Auto-Response Rule sends an automated email acknowledgment to the contact. However, when a support agent manually creates a High-Priority case in Salesforce on behalf of a customer, the case remains owned by the agent, fails to escalate after two hours, and no auto-response email is sent. What explains why these three automation behaviors occurred for the manually created case, and what is the native Salesforce capability regarding these rules?

  1. The agent did not check the 'Assign using active assignment rule' checkbox during manual creation, leaving the agent as the owner and failing the Escalation Rule criteria; additionally, Auto-Response Rules natively execute only for cases generated via Web-to-Case, Email-to-Case, or API, and do not trigger on manual UI creation.Answer
  2. B
    Escalation Rules must be configured to reassign newly created cases to support queues upon creation rather than using Case Assignment Rules, which only execute on updated cases; Auto-Response Rules were suppressed because the agent lacked object-level create permissions on the Case object.
  3. C
    System validation rules executed before record-triggered flows and suppressed the Auto-Response and Escalation rules from firing during manual record insertion by the agent.
  4. D
    Web-to-Case submissions bypass standard daily system limits, whereas manual case creation by agents causes the Auto-Response and Escalation Rules to route all notifications directly to the organization's default case owner email address.

Answer

The agent did not check the 'Assign using active assignment rule' checkbox during manual creation, leaving the agent as the owner and failing the Escalation Rule criteria; additionally, Auto-Response Rules natively execute only for cases generated via Web-to-Case, Email-to-Case, or API, and do not trigger on manual UI creation.
For cases created manually in the Salesforce UI, Case Assignment Rules only execute if the user selects the 'Assign using active assignment rule' checkbox (or if configured to be checked by default on the page layout). Because this checkbox was not used, ownership remained with the creating agent. This caused the Escalation Rule to fail its entry criteria ('Case Owner equals Tier 2 Support Queue'). Furthermore, Salesforce Auto-Response Rules natively only fire for automated case capture tools (Web-to-Case, Email-to-Case) and never fire during manual UI creation.

Step-by-Step Solution

1
Analyze why Case Assignment Rules did not fire during manual creation.
In Salesforce, manually created cases default ownership to the creating user unless the 'Assign using active assignment rule' checkbox is enabled on the page layout or manually checked during creation.
Case Assignment Rules execute automatically on Web-to-Case / Email-to-Case, but require explicit user opt-in or default layout settings for manual UI creation.
2
Evaluate why Escalation Rules failed to trigger.
The Escalation Rule entry criteria required 'Case Owner equals Tier 2 Support Queue'. Because the assignment rule did not fire, ownership remained with the creating agent, causing the case to fail the escalation criteria.
Escalation Rules evaluate criteria against current record attributes; failing entry criteria prevents SLA timers from scheduling.
3
Determine the operational limits of Auto-Response Rules.
Salesforce Auto-Response Rules are specifically designed for automated lead and case capture mechanisms (Web-to-Case, Email-to-Case, Portal). They do not trigger for records created manually via the standard user interface.
Auto-response emails prevent duplicate or unnecessary automatic replies when an internal agent is directly creating the record in the app.

Key Concept

Case Automation Execution Contexts and Rule Trigger Mechanisms
Rate this question

Topics

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

More questions from this topic