Section 5 · Service and Support Applications · 10% of exam
5.1 Case management, queues, and case assignment
Exam objective
Describe case management capabilities, including cases, case assignment rules, and queues.
Cases represent customer issues or service requests. Case fields, status, priority, and ownership help teams track work from intake to resolution. Case assignment rules route new cases based on criteria to users or queues. Queues provide a shared work pool that eligible members can access and take ownership of.
Assignment rules support automatic routing at case creation or when invoked through supported intake paths. A queue is a destination that lets a group share work; it is not itself the criteria engine. Select rules and queues based on the routing logic, team ownership, and how agents claim or distribute cases.
Additional concepts
A queue is a shared work destination
Case assignment rules evaluate routing criteria and can assign qualifying cases to users or queues. A queue lets a group of eligible users access and take ownership of shared work. Queue membership and supported objects determine who can work those records.
Separate intake from resolution
Case fields and statuses help teams track a case from intake through resolution. Assignment is about routing ownership; a queue is about shared work; support processes determine available status values for a record type. Identify which stage of service work the scenario is asking you to improve.
Cases submitted from a product support form should route by product family. Configure criteria in the case assignment rule and assign each category to the appropriate support queue, then test which rule entry applies to sample cases.
Key takeaways
- Cases track service work; assignment rules determine routing.
- Queues hold work for a group rather than one named owner.
- Validate routing criteria and ownership behavior with representative cases.
