Dynamics 365 Contact Center - Run voice outbound campaigns with proactive engagement
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
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 run voice outbound campaigns with proactive engagement in Dynamics 365 Contact Center. This feature will reach general availability on March 31, 2026. How does this affect me? This feature allows administrators to configure proactive engagements in voice outbound campaigns to reach more customers efficiently and compliantly while optimizing operational resources. Key capabilities of this feature include:
- File upload and API options: Upload files containing customer data to onboard contacts for proactive engagements or use API integration to directly submit proactive engagement requests with attributes.
- Reattempts configuration: Administrators have granular control over retry logic for proactive engagements by setting up the following options:
- Outcome-based retries
- Maximum attempts and wait times
- Number selection and stacking
- Contact chaining
- Communication preferences: Controls to honor customer communication preferences include:
- Contactable hours and days
- Holiday restrictions
- Consent management
What action do I need to take? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Run voice outbound campaigns with proactive engagement..
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Learn more
Links from the notice and their documentation checksRelated public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
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.