Conversation Orchestration uses natural-language playbooks to replace static routing rules with live, context-aware decisions
Microsoft has released Conversation Orchestration for Dynamics 365 Contact Center in public preview. The feature dynamically manages contact center interactions using real-time prioritization and intelligent automation. It marks a shift away from static routing logic. The system continues making decisions throughout the entire conversation lifecycle.
What is Conversation Orchestration?
Conversation Orchestration is a new tool within the Service Operations Agent. It extends traditional routing to support dynamic responses as conditions change. Administrators define business policies in natural language. The model operates around events, conditions, and actions. Rather than setting routing rules once, the system monitors live signals throughout the conversation. It evaluates those signals against a configured playbook. Then it triggers the appropriate response. The result is a more adaptive operating model for managing real-time change.
Natural language playbooks replace complex rule trees
One of the more significant aspects is how administrators author policies. Rule trees can take weeks to build. They also require IT involvement to modify. Instead, administrators write natural-language instructions called playbooks. These define what should happen at each stage of the conversation.
For example, an admin might write: “If a premium customer is waiting in the queue and no support reps are available, increase their priority over time.”
Conversation Orchestration handles the rest. It reads conversation context in real time and evaluates conditions against CRM data. It executes the action with consistent results. Guided templates speed up common scenarios. Built-in validation catches conflicts before anything goes live.
The first two capabilities: available now in public preview
Microsoft is launching Conversation Orchestration with its first set of capabilities in public preview. These address two of the most common failures in contact center queue management.
Dynamic prioritization
Priority set at queue entry and never revisited is a costly operational problem. A customer waiting ten minutes competes for the same agent as someone who just arrived. A mid-journey transfer resets priority as if the conversation just started.
Dynamic Prioritization keeps priority evaluation active throughout the conversation. It applies to voice and live chat channels only. Two events can trigger a priority change: increasing wait time and queue transfers.
Each conversation holds a priority score between 0 and 100,000. The score increases at a minimum interval of every 30 seconds. When scores are equal, the system applies first-in, first-out ordering as a tiebreaker. Administrators configure the increment logic through prompt templates in the conversation orchestration playbook.
For example, a VIP customer’s score might increase by 20 every 30 seconds. A standard customer’s score might increase by 5. The longer any customer waits, the more their priority climbs — regardless of tier.
Overflow based on CSR availability
When no agents are available, every customer waits in silence. Some systems have overflow rules. But those rules wait for a fixed timer before acting. Every customer endures the same minimum wait, regardless of whether help is coming.
Overflow based on CSR availability acts immediately. As soon as a conversation enters a queue with no eligible agents, the overflow playbook fires. Context variables determine the outcome. The actions available differ by channel type:
Every customer gets a response. None of them wait in silence.
How to access Conversation Orchestration
Conversation Orchestration is now available in public preview for voice and live chat channels. Find it in the Copilot Service admin center. Navigate to: Get started > Contact Center Agents > Service Operations Agent (preview) > Conversation Orchestration (Preview).
Microsoft has also published supporting documentation on Microsoft Learn — Configure Conversation Orchestration (preview).
What this means for Dynamics 365 Contact Center customers
Microsoft positions Conversation Orchestration as the beginning of a broader platform. The company has confirmed it will expand the capability over time. Each addition will target a specific, high-impact contact center use case.
For organizations running Dynamics 365 Contact Center, the opportunity is immediate. Dynamic Prioritization and overflow management address two of the most common queue management pain points. Neither capability requires specialist configuration or change management cycles.
Organizations should evaluate this public preview against their existing routing setup. As with any preview capability, exercise caution with production deployments until Microsoft confirms general availability.
Conclusion
Conversation Orchestration closes a genuine gap in contact center management. Most platforms cannot respond to changing conditions once a conversation starts. This feature changes that. The natural-language playbook model lowers the configuration barrier significantly. With two capabilities in public preview and more on the roadmap, contact center administrators should take note. Ready to explore this capability? Work with a Dynamics 365 Contact Center partner to assess it for your organization.
