Study guide
10.2 Service Team Case Management Integrated Lab
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
10.2 Service Team Case Management Integrated Lab
Key Takeaways Explain This Topic AI
A service setup combines support process design, Case fields, queues, assignment rules, escalation rules, Email-to-Case, knowledge, and reports.
Case automation should route and prioritize work without hiding ownership, entitlements, or exception handling from supervisors.
Admins must test service features with realistic channels, statuses, users, and case volumes before trusting dashboards or service-level metrics.
Good service labs include what agents see, what supervisors see, and what breaks when routing, sharing, or required fields are incomplete.
Last updated: May 2026
Lab scenario: support team case intake
A customer support team needs Salesforce to manage product questions, billing issues, and urgent outages. The team has six agents, one supervisor, and a shared support email address. Customers may email support, sales reps may create cases from accounts, and supervisors need dashboards for backlog, response age, and priority. The admin must configure enough of Service Cloud behavior to support daily work without overbuilding a full contact center.
Begin with the support process. In Setup > Object Manager > Case > Fields & Relationships , review standard fields before adding new fields. Case already includes Status, Priority, Origin, Type, Reason, Contact, Account, Owner, and Subject. Add a small number of fields only when they drive routing, service commitments, reporting, or resolution. Examples include Product Area, Customer Impact, Root Cause, and Resolution Category. Use restricted picklists where analytics need consistency. Avoid turning Subject or Description into structured data that belongs in a controlled field.
Configure statuses and support process from Setup > Object Manager > Case > Fields & Relationships > Status and Setup > Support Processes . A basic team might use New, Working, Waiting on Customer, Escalated, and Closed. If different teams need different statuses, use record types and support processes, but only after confirming that the added complexity is worth it. Expected observation: agents can move cases through a clear lifecycle and reports can separate active, waiting, escalated, and closed work. Failure mode: too many statuses produce inconsistent use and unreliable backlog reports.
Service component Setup path Expected observation Failure mode to watch
Case record types and support process Setup > Object Manager > Case Agents see statuses and page layouts that match their work Users choose wrong record type because labels are unclear
Queues Setup > Queues New cases can wait in Billing Support or Technical Support queues Cases remain unowned by a person with no supervisor review
Assignment rules Setup > Case Assignment Rules Email or created cases route by product, type, priority, or account segment Rule order sends urgent cases to a general queue
Escalation rules Setup > Escalation Rules Aging or high-priority cases raise visibility Escalations fire during waiting-on-customer statuses
Email-to-Case Setup > Email-to-Case Inbound email creates cases with usable origin and contact matching Duplicate or unmatched contacts create messy case records
Service reports Reports tab Backlog and aging reports reflect ownership and status Running user and sharing make supervisor dashboards incomplete
Create queues before routing. Use Setup > Queues and add Case as a supported object. Build Billing Support, Technical Support, and General Support queues, then add the right users or public groups. Queue membership is not a substitute for training or service ownership. Agents should know when to take ownership, when to transfer, and when to escalate. Expected observation: a new case can be owned by a queue, visible in a queue list view, and accepted by an agent. Failure mode: cases sit in a queue because no one is accountable for triage.
Configure assignment rules in Setup > Case Assignment Rules . Build rules in a deliberate order because Salesforce evaluates entries by sequence. Example: if Priority is High and Product Area is Platform, assign to Technical Support; if Type is Billing, assign to Billing Support; otherwise assign to General Support. Test each rule with sample cases created through the UI and through Email-to-Case if enabled. Include a case with missing Product Area to see the default behavior. The admin should capture rule criteria, owner result, notification behavior, and whether the assigned queue has active members.
Add escalation only after status meaning is stable. In Setup > Escalation Rules , create a rule that escalates high-priority cases after a defined time if they are not Closed and not Waiting on Customer. Escalation can change owner, notify users, or raise visibility, but it should not punish agents for cases that are properly waiting on a customer response. Test business hours, holidays, status changes, and ownership changes. A common failure mode is an escalation rule that keeps firing because nobody defined a clear exit condition.
Set up Email-to-Case in a safe lab context if available. Use Setup > Email-to-Case to review routing addresses and settings, then test with a controlled email account. Expected observations include a new case with Origin Email, subject and description populated, contact matched when the sender email exists, and assignment rules applied if configured. Failure modes include unmatched contacts, case threads splitting because reference information is missing, attachments exceeding limits, or agents replying outside Salesforce and losing activity history.
Build the agent workspace. Use Lightning App Builder and the Service app to make Cases, Accounts, Contacts, Knowledge, Reports, and Dashboards easy to reach. Add list views for My Open Cases, My Escalated Cases, Queue: Billing Support, Queue: Technical Support, and Cases Waiting on Customer. If Knowledge is in scope, enable and configure it in a Trailhead Playground or sandbox, then confirm agents can search approved articles and attach or reference them appropriately. Do not assume Knowledge solves process issues. Articles need ownership, review, and retirement.
Finish with reports that answer operational questions. Create reports for open cases by owner and priority, aged open cases by status, cases created by origin, first response or aging approximations where fields support it, and closed cases by resolution category. Build a supervisor dashboard and verify it as the supervisor. If records are private, the supervisor may need role hierarchy visibility, sharing rules, or team membership. If the dashboard uses a running user, make sure the choice aligns with the intended visibility model.
A manager dashboard that shows all cases because it runs as the admin may hide a sharing gap.
Review prompts before the quiz:
Which case fields are needed for routing, and which are only nice-to-have labels?
How should assignment rule order handle urgent cases before general cases?
Which statuses should pause or exclude escalation timing?
What happens when an email sender does not match an existing contact?
How would you prove a supervisor dashboard reflects team backlog accurately?