Study guide
5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation
Salesforce Admin Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Platform Administrator Orientation and Official Source Control
1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow
2 Chapter 2: Configuration, Setup, User Management, and Org Controls
2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab
3 Chapter 3: Security, Access, Identity, and Sharing Model
3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab
4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling
4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab
5 Chapter 5: Sales, Marketing, Service, and Support Applications
5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab
6 Chapter 6: Data and Analytics Management
6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab
7 Chapter 7: Automation, Flow, Approval, and Operational Processes
7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab
8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange
8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab
9 Chapter 9: Agentforce for Platform Administrators
9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab
10 Chapter 10: Integrated Salesforce Admin Scenario Labs
10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy
11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy
11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review
5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation
Key Takeaways Explain This Topic AI
Cases represent customer issues or requests, and support processes control status values for different Case record types.
Queues hold unowned or team-owned work so support agents can accept, route, or manage Cases before final ownership is assigned.
Assignment rules, auto-response rules, and escalation rules solve different problems and should not be confused.
Case automation must respect customer communication, service level commitments, ownership, and security.
Last updated: May 2026
Case Management Model
A Case is a record of a customer question, issue, request, complaint, or support interaction. Cases can come from agents, Email-to-Case, Web-to-Case, Experience Cloud, integrations, phone work, chat, messaging, or manual entry. The admin configures fields such as Status, Priority, Origin, Type, Reason, Subject, Description, Contact, Account, Asset, Product, and Owner so the support team can triage and resolve work consistently.
Support processes control which Case Status values are available for a Case record type. This mirrors the sales process idea for Opportunities. A technical support team might use New, Working, Waiting on Customer, Escalated, and Closed. A returns team might use Received, Approved, Replacement Sent, and Closed. The admin should keep statuses reportable and operational. If every team invents similar statuses with slightly different names, dashboards and service metrics become unreliable.
- Feature Primary purpose Setup clue Common exam trap
- Case queue Hold work for a group Setup, Queues Confusing queue membership with ownership transfer logic
Assignment rule Set owner based on criteria Setup, Case Assignment Rules Expecting it to send customer acknowledgments
Auto-response rule Send initial email response Setup, Case Auto-Response Rules Expecting it to route the Case
Escalation rule Reassign or notify after time criteria Setup, Escalation Rules Expecting it to run immediately like assignment
- Support process Status values by record type Setup, Support Processes Editing global status values only
- Queues And Ownership
Queues let groups own records, including Cases and Leads. A queue can include users, roles, public groups, and other supported members. When a Case is owned by a queue, members can take ownership if they have access. Queues are useful for first-line triage, regional support, billing questions, partner support, and after-hours work. They also make list views and work distribution easier than assigning every new Case to a single manager.
Queue membership does not automatically mean a user can see every field or perform every action. Object permissions, sharing, field-level security, record types, and page layouts still matter. If a user is in the queue but cannot work the Case, check whether they have Read and Edit on Cases, access to the record type, visibility to related Account or Contact if needed, and access to the list view or console app.
Assignment Rules
Case assignment rules evaluate criteria and set the Case owner. A rule entry can assign to a user or queue. Entries are processed in order, so specific criteria should usually appear before broad catch-all entries. Assignment rules can be invoked from supported Case creation paths and user actions. In Setup and automation design, admins should know when the active assignment rule applies and when a Flow or integration is bypassing or replacing it.
Example assignment logic might route Priority High and Product A Cases to the Tier 2 Product A queue, billing Cases to Billing Support, and all remaining Web Cases to Tier 1. If a Case is not routed as expected, inspect the active rule, entry order, criteria logic, field values at creation time, and whether the creation path selected the assignment rule option. Also check for after-save automation that may overwrite the owner after assignment.
Auto-Response Rules
Auto-response rules send an email acknowledgement based on Case criteria. They are useful for confirming receipt, setting expectations, sharing a case number, or giving next steps. They do not choose the Case owner. A common exam clue is a requirement to send different acknowledgement emails based on language, product, priority, or origin. That points to auto-response rules, email templates, and organization-wide email addresses rather than assignment rules.
Be careful with customer communication. The email should not promise a response time that the organization cannot meet. It should not expose internal fields or confidential information. Test merge fields, sender address, deliverability, and criteria. If customers are not receiving the email, check the active auto-response rule, criteria, email template, support settings, deliverability, spam handling, and whether the Case creation source allows the rule to fire.
Escalation Rules
Escalation rules take action when a Case remains unresolved or in a certain state beyond defined time criteria. They can notify users, reassign the Case, or perform escalation actions according to business hours and criteria. Escalation is about time-sensitive service management, not initial routing. It should align with support commitments, priority definitions, business hours, and entitlement processes if those are used.
Case routing troubleshooting checklist
Confirm the Case was created with the expected Origin, Product, Priority, Account, Contact, and record type.
Check the active assignment rule and the order of rule entries.
Verify whether the creation source used assignment rules.
Review Flow, Process Builder legacy automation, Apex, or integrations that may update owner after assignment.
Confirm queue membership and Case object permissions for users expected to work the record.
For auto-response, check email template, organization-wide sender, deliverability, and criteria.
For escalation, check business hours, age calculation, paused states, and criteria.
Business Hours And Priority
Support teams often have different commitments for urgent, standard, and low-priority work. Native Case features use fields such as Priority, Status, Business Hours, and entitlement-related milestones to measure time. Even before entitlements are enabled, admins should define priority values carefully. If every customer can mark every Case urgent, escalation becomes noise. Use page layouts, validation, customer portal settings, Flow, or assignment criteria to keep priority meaningful.
Business hours affect escalation timing. A Case created at 6 PM on Friday may have a different escalation target than one created at 10 AM on Tuesday. If the scenario mentions support hours, holidays, or regional service teams, check whether business hours are part of the configuration. Do not assume elapsed clock time is always the same as support time.
Scenario Walkthrough
A company wants web cases about outages to go to an urgent queue, send customers an immediate acknowledgement, and notify a manager if the Case is still New after one business hour. The right design uses a Case assignment rule for owner routing, an auto-response rule for the customer email, and an escalation rule for the delayed manager action. A single Flow could do pieces of this, but native features are clearer, easier to maintain, and match the standard support model.
Practice in a Developer Edition org by creating two queues, a Case assignment rule, and an auto-response rule with a simple email template. Create Cases with different Origin and Priority values and inspect owner, emails, and field history if enabled. Then add an escalation rule using test-friendly criteria. The hands-on lesson is that each rule type has a narrow job, and most troubleshooting starts with whether the right rule was active and eligible when the Case was created.