Acceptance Due Date: The Omni-Channel SLA Sensation You Need
Summary
Managing workloads with mixed SLA durations in Service Cloud is tricky because static priorities fail to dynamically prioritize urgency. The Acceptance Due Date feature in Winter ’26 release enables routing based on how close an item is to its SLA expiry, rather than fixed priority values. By calculating and using dynamic due dates in Omni-Channel Flows, teams can ensure the most urgent cases or tasks are handled first. Integrating this with existing Salesforce SLAs and adjusting priority levels creates a more flexible and effective routing system that balances automation with manual overrides.
Takeaways
- Calculate acceptance due dates dynamically in Omni-Channel Flows using date/time formulas.
- Set uniform Primary and Secondary Priorities to enable routing by Acceptance Due Date.
- Use a default Primary Priority (e.g., 5) to reserve lower numbers for manual priority overrides.
- Integrate Acceptance Due Date routing with Salesforce Entitlements and Milestones for Cases.
- Report SLA compliance using AgentWork fields like Accept Date and Target Accept Date Time.
One of the oldest challenges in Service Cloud is ensuring your urgent work gets handled first—not just the old work, but the work that is truly closest to violating its Service Level Agreement (SLA) . You might have a customer who paid for a 2-hour response time, and another who is on a standard 8-hour agreement. Prioritizing items that enter the queue at the same time is relatively straightforward today, just using priorities. The real challenge arises over time, when your longer SLAs are approaching expiry, and new shorter ones are still entering your backlog. Historically, we’ve relied on clever, but ultimately limited & complex uses of Primary and Secondary Priority to try to solve for this – or a lot of manual assignment by supervisors. Now, with the Winter ’26 release , we’re proving a dedicated tool for this: Acceptance Due Date This feature is a game-changer for any service center dealing with mixed-length SLAs or simply needing to prioritize work by true urgency.