Dynamics 365 Contact Center integrates workforce engagement management
Contact center staff scheduling often takes place outside the interaction management tool. It’s done in a spreadsheet or in specialized software purchased separately and connected in a makeshift manner. Our take: Forecasts are then based on volumes exported the previous week, and scheduling decisions lag behind actual demand.
Workforce engagement management(WEM) is being integrated into Dynamics 365 Contact Center to bridge this gap. The idea is not to add a module, but to base planning on the service demand as observed by the platform.
What the field covers
WEM comprises two components currently documented for Dynamics 365 Contact Center: workforce management and quality management, supported by the Quality Management Agent. Microsoft describes WEM more broadly as also encompassing performance, engagement, and training.
| Shutter | What it covers |
|---|---|
| Workforce Management | Demand forecasting, capacity planning, schedules, monitoring of schedule adherence |
| Quality Management | Evaluation of Completed Conversations, Compliance with Standards |
The prediction is based on the history of interactions already stored in the platform, and the quality assessment focuses on the conversations the platform has already recorded.
Quality assessment is changing in nature
Traditionally, quality is measured through manual sampling, and feedback is provided to the sales team several weeks after the interaction—our take: it is this delay that diminishes its educational value.
The proposed model is based on evaluation criteria and evaluation plans defined by the organization, as well as an assisted evaluation that focuses on closed conversations—in Dynamics 365 Contact Center, case evaluation remains specific to Dynamics 365 Customer Service. The evaluation results are then used for coaching, based on the defined criteria. As of May 1, 2026, multiple closed conversations can be selected at once from the conversation list, rather than having to be opened one by one.
Our take: The evaluation rubric becomes a configurable tool, which means someone has to write it—and that’s what’s most costly to address after the fact: Writing explicit criteria forces us to resolve disagreements that had previously remained implicit.
Licenses—check them before you project anything
Two prerequisites are documented for quality assessment: enabling quality assessment itself, and setting up credits Microsoft Copilot. The licensing terms for each edition can be verified in the current licensing guide Dynamics 365 before estimating a scope. The WEM features listed in the release plan will be delivered in phases throughout 2026, with general availability dates specific to each feature rather than a single date for the entire domain.
Checking the licenses before the scoping workshop prevents the need to redefine the scope later on.
The release plan states that deadlines are subject to change and that an announced feature may not be released. An internal roadmap based on a release plan date should take this into account.
What It Replaces, and What It Doesn't Replace
What it can replace: a separate planning tool, an evaluation grid in a spreadsheet, or productivity tracking that is compiled manually each month.
What it doesn't replace: the decision about what constitutes a good interaction. The tool applies criteria; it doesn't define them. An organization that has never formalized its definition of quality will not find the answer in the configuration.
What remains to be done in any case: align the forecast with actual business performance. Our take: a forecast based on observed volumes is only valuable if those volumes are representative, which requires some perspective—during the first year of operations, or following a change in scope, manual adjustments are to be expected.
Where to start
- Verify the license status of the relevant population in the current guide, and fulfill the two documented prerequisites: the quality assessment and the credits Microsoft Copilot.
- Write down the quality criteria before configuring anything. Three to five clear criteria are better than a twenty-line checklist that no one follows the same way.
- Measure current coverage: How many interactions are actually being evaluated today, out of the total volume? This is the figure that will make the change visible.
- Address the forecast second. It requires its own historical data, and that data is built up as the rest of the system is set up.
These trade-offs between tools, processes, and organization are common to any contact center project; our page Dynamics 365 Contact Center outlines the framework.
Microsoft Sources
- Dynamics 365 Contact Center — Workforce Engagement Management, Wave 1 of 2026 — Microsoft Learn
- Upcoming Features and Updates for Dynamics 365 Contact Center — Microsoft Learn
- Workforce Management Overview — Microsoft Learn
- Overview of the Quality Management Agent — Microsoft Learn
- Create and Manage Assessment Plans — Microsoft Learn
What an article Can't Know
An article describes what applies to everyone. What varies from one organization to another is the inventory: which applications, which accounts, and which pieces of equipment are actually involved in your organization. The inventory determines the scope of the effort, and it cannot be summarized on a single page.
You'll be speaking directly with the engineers who will be doing the work, not with a middleman. We'll respond within 24 business hours.
Check what is still true
Announced dates are sometimes postponed, products are renamed, and conditions change. The blog tracks these topics over time: when a rule changes, a new post announces it.
Search for a topic in the blogIn the same issue
Three articles on the same topic. The blog has 149 articles, all of which are freely accessible.