What changed
Administrators can now configure, per queue, how far in advance a callback can be scheduled. Before this, callbacks could be scheduled up to 30 days ahead regardless of the queue's configured callback limit, except for agent-owned callbacks. The new limit applies to callbacks scheduled from the agent UI, the public Create Callback API, in-queue data actions and outbound campaigns. The default remains 30 days, so behavior doesn't change until you set a limit.
Vendor documentation (opens in a new tab)Why it matters
Callbacks booked weeks out often land after the customer's issue is resolved or after the data behind them should have been purged. A queue limit lets operations align scheduling with staffing horizons and data retention. Integrations that create callbacks through the API should be ready for requests beyond the limit to be refused once a limit is set.
CxCave practical context
Who should care
- Administrators
- Developers
- WFM teams
Implementation considerations
REVIEWDecide on a scheduling horizon per callback queue, then test the Create Callback API, in-queue data actions and campaigns against the new limit before lowering it in production.
CxCave recommendation, not a vendor mandate unless explicitly stated.
