MC1323940 High
Dynamics 365 Contact Center - Protect customer experience on direct inward dialing lines with overflow actions
Summary AI-generated
Dynamics 365 Contact Center adds overflow actions for direct inward dialing lines, letting admins define fallback responses when calls aren't completed, available June 20, 2026.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1411146 Dynamics 365 Contact Center - Use enhanced customer-first direct callbacks
- MC1265701 Dynamics 365 Contact Center - Use callback insights to optimize contact center operations
- MC1323827 Dynamics 365 Contact Center - Automatically handle waiting conversations when queues close or become unstaffed
- MC1391926 Dynamics 365 Contact Center - Boost contact center efficiency with real-time streaming analytics
- MC1214118 Dynamics 365 Contact Center - Handle duplicate callback requests gracefully when queues are overflowing
- MC1324991 Dynamics 365 Contact Center - Consult, transfer securely for PSTN numbers, and IVR
Original post from Microsoft
We are announcing the ability to protect the customer experience on direct inward dialing lines with overflow actions in Dynamics 365 Contact Center. This feature will reach general availability on June 20, 2026.
How does this affect me?
This feature leverages Conversation Orchestration to detect key related events such as the user being busy, offline, rejecting the call, or failing to answer to apply administrator-defined fallback actions.
Administrators can configure natural language playbooks using Conversation Orchestration at the global or profile level to specify what should happen when a direct inward dialing call cannot be completed.
Supported actions include offering a direct callback, sending callers to voicemail, transferring to another queue or external number, or ending the call.
What action do I need to take?
This message is for awareness, and no action is required.
How does this affect me?
This feature leverages Conversation Orchestration to detect key related events such as the user being busy, offline, rejecting the call, or failing to answer to apply administrator-defined fallback actions.
Administrators can configure natural language playbooks using Conversation Orchestration at the global or profile level to specify what should happen when a direct inward dialing call cannot be completed.
Supported actions include offering a direct callback, sending callers to voicemail, transferring to another queue or external number, or ending the call.
What action do I need to take?
This message is for awareness, and no action is required.