Case, Checkout
Case Checkout in Salesforce Service Cloud is the workflow pattern where an agent explicitly claims a Case (or a record from a queue) by taking ownership before working on it.
Definition
Case Checkout in Salesforce Service Cloud is the workflow pattern where an agent explicitly claims a Case (or a record from a queue) by taking ownership before working on it. The behaviour signals to the rest of the team that this case is being handled, prevents two agents from picking up the same case, and starts the work clock from the moment of checkout. Salesforce surfaces the pattern through Take Ownership buttons on Queue list views, through Omni-Channel routing (which automatically assigns work and prevents double-claim), and through custom Apex or Flow that updates the case Owner field on user action.
Case Checkout matters because customer service teams often share a pool of incoming work. Without checkout, two agents can independently work the same case, duplicating effort and confusing the customer. With checkout, ownership becomes an explicit, visible state. Modern Service Cloud increasingly automates checkout through Omni-Channel rather than relying on manual Take Ownership. Either approach works; both produce the same operational outcome of one Owner per Case at any given time. The phrase Case Checkout appears most in legacy Service Cloud documentation and partner blogs; modern documentation uses Take Ownership or Omni-Channel Routing as the more specific terms.
How Case Checkout works across Service Cloud surfaces
Take Ownership on Queue list views
Cases assigned to a Queue (rather than a specific user) appear in the Queue's list view. Agents who are members of the Queue see the list. Clicking Take Ownership reassigns the Case to the current user, removing it from the Queue and making the user the Owner. Take Ownership is the manual checkout pattern.
Omni-Channel as automated checkout
Omni-Channel routes work items (cases, chats, calls) to the next available Agent based on configured rules. The routing assigns the work item directly to the Agent without manual selection. From the customer's perspective and the org's reporting perspective, the effect is identical to manual checkout; the Agent is the owner the moment work arrives.
Custom checkout patterns
Some orgs build custom checkout buttons or Flows that update the Owner field with side effects (start a clock, log a Task, notify the previous Owner). These extensions are useful when the standard Take Ownership lacks needed business logic; they should still produce the same end state of one Owner per Case.
Preventing double-checkout
Omni-Channel guarantees one Agent per work item by routing. Manual Take Ownership relies on standard record-locking; the second user to click sees an error. Custom checkout patterns need explicit locking (FOR UPDATE in SOQL or Apex queueable serialisation) to prevent two simultaneous claims.
Returning ownership to the Queue
After checkout, an Agent may need to return the case to the Queue (case is more complex than expected, agent skill mismatch, end of shift). Standard pattern is to change the Owner field back to the Queue. Some orgs surface this as a Return to Queue button to make the action visible.
Reporting on checkout time
Reports on the time between Case Created and Case Checkout (or Case Assigned) show queue dwell time. The metric reveals whether the Queue is staffed adequately. Low dwell times indicate responsive service; high ones indicate bottlenecks worth investigating.
Case Checkout in field service
Field Service uses a similar concept for Service Appointments. Technicians check out an appointment when they accept the assignment, with the resulting status changes tracked in Service Appointment History. The mechanics differ (mobile-first acceptance through the Field Service Mobile app) but the operational outcome is the same.
Common pitfalls
Three patterns recur. Manual Take Ownership without enforced uniqueness produces occasional double-checkout. Omni-Channel without capacity tuning routes too many cases to one Agent. And custom checkout patterns that update Owner without firing the normal record-change events leave automation silent on what should be a triggering action.
How to configure Case Checkout
Most modern Service Cloud orgs run automated checkout through Omni-Channel. Manual Take Ownership stays available as a fallback or for queues outside Omni-Channel routing.
- Decide between Omni-Channel and manual Take Ownership
Omni-Channel works best for high-volume case routing. Manual works for low-volume queues or roles where Agents pick their own work.
- Configure Queues with the right membership
Setup, Queues. Add the right user list to each Queue. Confirm agents see the Queue list view and have Take Ownership permission.
- For Omni-Channel: configure Routing Configurations and Service Channels
Setup, Omni-Channel, Routing Configurations. Define how the platform routes work (capacity-based, skills-based). Pair with Service Channels for each work item type.
- Train agents on Take Ownership and Return to Queue
Even with Omni-Channel, manual fallback patterns matter for edge cases. Document the workflow so agents know when to use which.
- Build queue dwell-time reports
Report on time between Case Created and Owner Changed. Persistent high dwell times signal queue staffing or routing issues.
- Manual Take Ownership without enforced uniqueness can produce occasional double-checkout. Test the locking behaviour in sandbox.
- Omni-Channel routing without capacity tuning overloads individual Agents. Right-size capacity per Agent role.
- Custom checkout patterns that bypass standard events leave downstream automation silent. Trigger the normal Owner-changed events on custom updates.
- Field Service appointment checkout has its own mobile-first patterns. Documentation that applies to Case Cases may not apply to Field Service.
Trust & references
Cross-checked against the following references.
- Manage CasesSalesforce Help
- Omni-Channel OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Case, Checkout.
- Set Up QueuesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does a Case linked to a Checkout provide?
Q2. What is a common use case for Case-to-Checkout linking?
Q3. What benefit does the bidirectional integration provide?
Discussion
Loading discussion…