Overview
Case Management carries 13% of the exam and four objectives. The first asks you to design a case solution from creation to closure against requirements or KPIs: record types, support processes and statuses, assignment and escalation rules, auto-response rules, queues, case teams, merging duplicates and closing with satisfaction surveys.
The second covers case deflection through Experience Cloud sites, Agentforce and Knowledge, so fewer issues become cases at all. The third covers entitlement management: entitlements, entitlement processes, milestones and milestone actions, assets, business hours, service contracts and SLAs. The fourth asks you to differentiate service automation, choosing between assignment and escalation rules, Flow, macros, quick actions, Omni-Channel Flow, Einstein Case Classification and Agentforce actions for each job.
How it's tested
Questions present a case process with requirements such as faster response for premium tiers, fewer duplicate cases, less manual work or lower case volume. You choose the case configuration, entitlement design, deflection approach or automation tool that fits, favoring standard features and declarative tools.
-
Lifecycle design
A case process is described, and you set statuses, assignment, escalation and closure to meet KPIs.
-
SLA enforcement
Customers have contracted response times, and you design entitlements, milestones, business hours and actions.
-
Right automation
A manual step must be automated, and you choose rules, Flow, macros, classification or an AI agent action.
A software vendor promises Gold customers a first response within two business hours and resolution within one business day. An entitlement process with First Response and Resolution milestones, tied to Gold business hours, tracks both targets. Warning actions alert the owner before breach, and violation actions notify a manager. Escalation rules alone could reassign cases but would not track contractual milestones per customer tier.
Objectives 4
Official objectives from the Salesforce outline, in outline order.
6.1 Given a set of requirements or KPIs, design a case management solution from creation to closure.End-to-end case process design.
- What it means
- A case solution defines how cases are created, classified, assigned, worked, escalated and closed, with fields and statuses that support reporting on the client's KPIs.
- What to understand
- Use case record types and support processes to vary status values by team. Assign with assignment rules, queues or Omni-Channel; acknowledge with auto-response rules; escalate on time with escalation rules. Use case teams for collaboration, Slack-based Swarming for expert help, parent and child cases for related issues, and case merge for duplicates. Capture closure reasons, request surveys, and set fields that let reports measure FCR, backlog and time to resolve.
- How it shows up
- A case process problem is described, and you pick the configuration that fixes it while supporting the KPI.
- Common confusion
- Adding many status values that no report uses, instead of statuses that reflect real stages.
6.2 Given a set of requirements, explain how case deflection strategies are delivered in Experience Cloud sites, Agentforce, and Knowledge.Reducing case volume through self-service.
- What it means
- Case deflection resolves a customer's need before a case is created, through self-service content, community answers and AI agents.
- What to understand
- On Experience Cloud sites, the Contact Support form can suggest Knowledge articles as customers type, and help center search and community discussions answer common questions. Agentforce Service Agent can answer from Knowledge and perform actions such as order lookups on the site or in messaging. Measure deflection with site analytics and case trends, keep articles current, and always provide an easy path to create a case or reach a rep.
- How it shows up
- A client wants fewer cases, and you choose the deflection mechanism that suits its customers and content.
- Common confusion
- Hiding the contact option to force self-service, which raises effort and frustration.
6.3 Explain the capabilities, use cases, and how to configure service entitlements, milestones, assets, business hours, and service-level agreements (SLAs).Entitlement management for contractual service levels.
- What it means
- Entitlements define what support a customer is owed. Entitlement processes apply timelines of milestones, such as first response and resolution, to cases, honoring business hours and enforcing SLAs.
- What to understand
- Configure entitlements on accounts, contacts, assets or service contracts with contract line items. Build entitlement processes with milestones, criteria and time triggers, and milestone actions for success, warning and violation. Set business hours on the process or milestone, and use holidays. Add the milestone tracker to the case page. Use entitlement templates for products, versioning of processes, and auto-population of the entitlement on new cases through automation.
- How it shows up
- A support contract is described, and you choose the entitlement, milestone or business hours configuration that enforces it.
- Common confusion
- Confusing escalation rules, which reassign or notify on age, with milestones, which track SLA steps per entitlement.
6.4 Differentiate the use cases and capabilities of Agentforce Service automation.Choosing the right automation tool for service work.
- What it means
- Service automation spans rule-based tools, Flow, rep-triggered tools and AI. Each fits a different job, and exam questions test choosing the simplest tool that meets the requirement.
- What to understand
- Assignment, auto-response and escalation rules handle classic case routing, acknowledgement and aging. Record-triggered Flow handles field updates, related records and notifications. Screen flows guide reps, often through Actions and Recommendations. Macros automate repetitive rep clicks. Omni-Channel Flow routes work. Einstein Case Classification suggests or fills fields from past cases; Work Summaries and Service Replies assist reps; Agentforce actions let AI agents complete tasks. Use Apex only when declarative tools fall short.
- How it shows up
- A manual step is described, and you choose the automation tool best suited to it.
- Common confusion
- Choosing an AI feature when a simple rule or Flow meets the requirement more predictably.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Support process
Controls case status values per record type.
- Remember
- Lets teams have different stages.
- Tested as
- Multi-team case design.
- Trap
- Creating separate objects instead.
-
Assignment rules
Rule entries that assign new cases.
- Remember
- Only one rule is active at a time.
- Tested as
- Initial routing.
- Trap
- Expecting several active rules.
-
Escalation rules
Reassign or notify cases after time passes.
- Remember
- Respect business hours.
- Tested as
- Aging cases scenarios.
- Trap
- Using them for contractual SLAs.
-
Auto-response rules
Send acknowledgement emails on creation.
- Remember
- From Email-to-Case and Web-to-Case.
- Tested as
- Customer acknowledgement.
- Trap
- Building a Flow for basic replies.
-
Case teams
Groups of users with roles on one case.
- Remember
- Grant access and collaboration.
- Tested as
- Multi-expert cases.
- Trap
- Opening sharing defaults instead.
-
Entitlement process
Timeline of milestones applied to cases.
- Remember
- Can be versioned.
- Tested as
- SLA scenarios.
- Trap
- Expecting it to apply without an entitlement on the case.
-
Milestone actions
Success, warning and violation actions.
- Remember
- Trigger alerts, field updates and tasks.
- Tested as
- Breach prevention.
- Trap
- Only using violation actions.
-
Business hours
Working hours and holidays for time calculations.
- Remember
- Affect milestones and escalations.
- Tested as
- Global support scenarios.
- Trap
- Using 24/7 hours for a weekday SLA.
-
Service contract
Agreement holding several entitlements.
- Remember
- Contract line items link products.
- Tested as
- Contract-based support.
- Trap
- Linking entitlements only to accounts.
-
Contact Support form deflection
Suggests articles as customers type.
- Remember
- Reduces cases from sites.
- Tested as
- Deflection scenarios.
- Trap
- Removing the case option entirely.
-
Einstein Case Classification
Predicts case field values from history.
- Remember
- Needs enough closed cases.
- Tested as
- Classification automation.
- Trap
- Using it with little historical data.
-
Case merge
Combines duplicate cases.
- Remember
- Keeps related records and history.
- Tested as
- Duplicate email scenarios.
- Trap
- Deleting duplicates and losing history.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Escalation rules vs entitlement milestones
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Escalation rules | Act on case age | Reassign or notify | Used to track contractual SLAs |
| Milestones | Steps in an entitlement process | Track SLA targets per entitlement | Expected to apply without an entitlement |
Service automation tools
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Record-triggered Flow | Runs on record changes | Background logic | Used for rep click sequences |
| Macros | Rep-run action sequences | Repetitive console tasks | Expected to run automatically |
| Einstein Case Classification | Predicts field values | Learns from closed cases | Chosen with little history |
| Agentforce actions | Tasks an AI agent performs | Conversational automation | Used where a rule suffices |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Escalation equals SLA
- What candidates pick
- Use escalation rules for premium SLAs.
- Why it looks right
- Both deal with time.
- Why it's wrong
- Escalation rules act on case age; entitlement milestones track contractual steps per customer tier.
Clue to watch for Different tiers have different contracted times.
-
Milestones without entitlement
- What candidates pick
- Create milestones and expect them on all cases.
- Why it looks right
- Milestones look standalone.
- Why it's wrong
- Milestones run only through an entitlement process linked to the case's entitlement.
Clue to watch for Cases show no milestone tracker.
-
24/7 timers
- What candidates pick
- Leave default business hours.
- Why it looks right
- Defaults seem fine.
- Why it's wrong
- If the SLA is in business hours, wrong hours cause false breaches.
Clue to watch for SLA defined in business days.
-
Force self-service
- What candidates pick
- Hide the contact form behind several pages.
- Why it looks right
- Case numbers drop.
- Why it's wrong
- Customers grow frustrated and use costlier channels; deflection must leave an easy path to help.
Clue to watch for Satisfaction falls while cases drop.
-
AI for everything
- What candidates pick
- Use Einstein Case Classification for a simple rule.
- Why it looks right
- AI sounds advanced.
- Why it's wrong
- When the logic is fixed and known, a rule or Flow is cheaper and more predictable.
Clue to watch for Requirement maps one field value to another.
-
Delete duplicates
- What candidates pick
- Delete duplicate cases from repeated emails.
- Why it looks right
- It cleans the queue.
- Why it's wrong
- Deleting loses emails and history; case merge keeps related records.
Clue to watch for Customers send the same email twice.
Answer framework
Use these steps when a case design, SLA or automation scenario appears.
- Map the case lifecycle stage in the scenario, whether creation, assignment, working, escalation or closure, and note which KPI the client wants to move.
- Check whether the requirement is contractual; if so, use entitlements, entitlement processes, milestones and correct business hours.
- For volume reduction, use Knowledge suggestions on sites, community answers and Agentforce Service Agent, keeping an easy path to a case.
- Pick the simplest automation tool that fits: rules for routing and aging, Flow for logic, macros for rep clicks.
- Use AI features such as case classification or Agentforce actions when data and volume justify them, and confirm reporting fields support the KPIs.
Practice question
Want more like this? The Service-Con-201 practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Build the case lifecycle end to end in a Developer org. Create two case record types with different support processes, an assignment rule, an auto-response rule and an escalation rule, then submit test cases through Web-to-Case. Enable Entitlement Management, create business hours, an entitlement process with two milestones and success, warning and violation actions, and attach it to an entitlement on an account. Add the milestone tracker to the case page and watch the timers.
Next, set up an Experience Cloud help center with the Contact Support form and article suggestions, and read the Agentforce Service Agent overview for deflection use cases. Finally, write a table of ten manual service tasks and assign each the simplest suitable automation tool.
High-priority ideas are entitlements versus escalation rules and business hours. Underestimated is objective 6.4, which rewards choosing the plainest tool rather than the newest one. Practice explaining each choice in one sentence.
FAQ
How much of the exam is Case Management?
Case Management is 13% of the exam per third-party copies of the current guide, roughly eight scored questions as a planning estimate, across four objectives.
Why do some study guides split Case Management into two parts?
Some prep providers split the automation objective into a separate unit. The exam guide lists Case Management as one section with four objectives.
Do I need to memorize entitlement setup steps?
Know the components and their order: enable Entitlement Management, set business hours, build the process and milestones, then create entitlements and add them to cases.
Is Swarming tested?
It may appear as a collaboration option. Know that Swarming brings experts together on a case, often through Slack.
How is deflection measured?
Compare case creation against site and AI agent activity, and track whether customers who self-served later opened cases or called.
What does the automation objective mean by Agentforce Service automation?
It covers the service automation toolkit: rules, Flow, macros, Omni-Channel Flow, Einstein features and Agentforce actions, and when each fits.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 6 knowledge
You have covered case lifecycle design, deflection, entitlements and service automation. Check whether you can tell milestones from escalation rules under exam pressure.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Service-Con-201 AI tutor Get any concept explained your way