Dynamics 365 Contact Center - Use bullseye routing with user groups to orchestrate conversations
Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill FernandoRollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredWe are announcing the ability to Use bullseye routing with user groups to orchestrate conversations in Dynamics 365 Contact Center. This feature will reach general availability by November 6, 2026. How does this affect me? This feature introduces a tiered assignment strategy that automatically expands the pool of eligible customer service representatives as conversation wait times increase. Admins can configure a bullseye routing playbook, allowing them to associate user groups with a queue and define wait time thresholds for each tier they add to that queue. Once configured, conversation orchestration monitors each conversation's wait time and automatically expands the eligible pool when thresholds are reached. What action do I need to take? Admins can enable bullseye routing under conversation orchestration to start configuring bullseye playbooks. If you’re already using bullseye routing under conversation orchestration, you can continue using your existing configurations without additional action. Copilot credits are used only when an admin publishes a playbook, which makes the configured orchestration logic active for use. Once published, the playbook can process any number of customer conversations without consuming additional Copilot credits. Saving a playbook as a draft or simply enabling Conversation Orchestration does not consume Copilot credits. If you would like more information on this feature, please visit Use bullseye routing with user groups to orchestrate conversations.
What changed
Between the versions we saw, newest firstThis installation has seen one version of this notice, first on 4 Nov 2026. Later changes will show here.
Archive version history
Microsoft 365 Message Center Archive by Merill FernandoThese are the archive's capture times. They are separate from the versions returned by our reference tenants.
Read the archive's current copy
We are announcing the ability to Use bullseye routing with user groups to orchestrate conversations in Dynamics 365 Contact Center. This feature will reach general availability by November 6, 2026. How does this affect me? This feature introduces a tiered assignment strategy that automatically expands the pool of eligible customer service representatives as conversation wait times increase. Admins can configure a bullseye routing playbook, allowing them to associate user groups with a queue and define wait time thresholds for each tier they add to that queue. Once configured, conversation orchestration monitors each conversation's wait time and automatically expands the eligible pool when thresholds are reached. What action do I need to take? Admins can enable bullseye routing under conversation orchestration to start configuring bullseye playbooks. If you’re already using bullseye routing under conversation orchestration, you can continue using your existing configurations without additional action. Copilot credits are used only when an admin publishes a playbook, which makes the configured orchestration logic active for use. Once published, the playbook can process any number of customer conversations without consuming additional Copilot credits. Saving a playbook as a draft or simply enabling Conversation Orchestration does not consume Copilot credits. If you would like more information on this feature, please visit Use bullseye routing with user groups to orchestrate conversations.
- Dynamics 365 Contact Center - Use bullseye routing with user groups to orchestrate conversations Action date: Not supplied
Learn more
Links from the notice and their documentation checksRelated public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Some history or links were left out of the website export to keep it within its size limits.