Recorded 16 Oct 2026 at 20:17 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.
Dynamics 365 Contact Center: Omnichannel customer experiences - Handle duplicate callback requests in overflowing queues
In the in-queue and pre-queue overflow settings within the Copilot Service admin center, administrators can define the following settings: Prevent duplicate callback requests from the same phone number. Define deduplication logic using combinations of caller phone number, channel phone number, and queue ID. Configure caller experiences when a duplicate is detected. An option to end the call or play a custom message in a loop is available. For example: “You are already in queue to receive a callback when a customer service representative is available. Your latest wait time is 12 minutes. You can choose to continue waiting on this call if needed or disconnect and receive the callback.” Specify the phone number to initiate the callback from. Business Value: This feature delivers significant benefits by enhancing customer experience, operational efficiency, and administrative control. It prevents redundant callback requests from the same phone number, reducing unnecessary loads on representatives and systems. Administrators gain flexibility to configure deduplication logic and tailor the caller experience, including custom messaging when duplicates are detected. Enabled for: Enabled b…
What it said
- Roadmap ID
- 576772
- Status
- Launched
- General availability target
- August CY2026
- Preview target
- Not stated
- Products
- Dynamics 365 Contact Center
- Clouds
- Worldwide (Standard Multi-Tenant)
- Release phases
- General Availability
- Platforms
- Web
- Added to the roadmap
- 16 Oct 2026 19:08 UTC
- Last changed
- 16 Oct 2026 19:08 UTC
Recorded links
Source evidence when recorded
- Microsoft 365 roadmap
- Complete at observationRead 16 Oct 2026 at 20:16 UTC
Coverage describes the sources at this observation. A complete read then does not establish their current position.
What changed
First observed 16 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.