Service operations teams have spent the past two years keeping two separate capacity plans, one for people and one for AI, and Microsoft has now merged them into a single forecast. Workforce engagement management became generally available inside Dynamics 365 Customer Service and Dynamics 365 Contact Center on 30 June 2026, and the August updates extended it with real-time coaching and a supervisor view that shows human representatives and AI agents in the same plan.
The most valuable part of this release is the part that is easiest to overlook. Workforce engagement management is included with Dynamics 365 Customer Service Enterprise, Customer Service Premium, and Contact Center Voice and Digital. For a large number of organisations, that means a full forecasting, scheduling, adherence and quality suite is already sitting in the tenant they pay for, with no separate workforce management contract to negotiate and no new integration to build. Teams that have been running schedules in a spreadsheet, or paying for a bolt-on that never quite saw the case data, suddenly have a credible native option to evaluate on their own timetable.
What is workforce engagement management in Dynamics 365?
Workforce engagement management in Dynamics 365 is a native set of capabilities for forecasting service demand, scheduling representatives against that demand, monitoring adherence in real time, and evaluating quality. It became generally available on 30 June 2026 inside Dynamics 365 Customer Service and Dynamics 365 Contact Center. Unlike a bolt-on workforce management tool, it forecasts from live service signals such as cases, conversations and channel activity rather than from historical interaction volume alone, and it plans human representatives and AI agents in the same model. It is included with Customer Service Enterprise, Customer Service Premium and Contact Center Voice and Digital licences.
That last detail changes who gets to run the evaluation. Specialist workforce management platforms have historically been a procurement exercise with a business case attached, which put them out of reach for mid-sized service organisations and for regional teams inside larger groups. When the capability arrives with the licence, a service operations lead can model a single queue, compare the output against the roster they build by hand today, and form a view in a fortnight rather than a quarter. Low-cost evaluation is its own kind of advantage.
Why does one forecast for people and AI change the maths?
Until now, AI capacity has mostly been reconciled after the fact. Teams deployed agents, watched consumption accrue, and found out at the end of the month what the automation had cost. The AI Agent Estimator moves that conversation forward in time. Planners can project AI agent capacity and consumption alongside human staffing, broken down by time interval, queue and channel, which means finance and IT can see the shape of AI spend before operations feel it.
The reason this matters is not cost control on its own. It is that AI capacity finally behaves like every other input in a capacity plan. Once you can express automation as a projected volume against a queue, you can trade it against headcount deliberately: absorb a seasonal peak with agents instead of overtime, hold human capacity for the queues where judgement earns its keep, or model what a new channel would cost in both currencies before committing to it. Service leaders have wanted that trade to be explicit for a long time, and now the planning tool supports it natively rather than through a side calculation in a spreadsheet.
Flagstar Bank’s chief technology officer described the ability to unify human and AI workforce planning, real-time operations and quality management in one system as a clear differentiator. That framing is right. The differentiator is not any single feature, it is that the three activities finally share one set of numbers.
Is your service data good enough to forecast on?
For most organisations running Dynamics 365 Customer Service, the honest answer is that it is closer than they assume. Forecast quality depends on a narrow set of fields rather than a pristine database: accurate queue assignment, consistent case categorisation, reliable timestamps on creation and resolution, and channel recorded correctly. Those are the fields service teams already rely on for routing and service-level reporting, so they tend to be the healthiest data in the system. CRM data quality matters here because the model reads live service signals, and a queue that receives misrouted cases will produce a forecast that plans for the wrong work.
The practical move is to check those four fields on your two or three highest-volume queues before extending the forecast across the whole contact centre. That is a short piece of work with a useful side effect: the same tidy-up improves routing accuracy and makes existing service-level reporting more trustworthy, whether or not you go on to adopt the full workforce engagement suite. It is the rare data exercise that pays for itself twice.
Which number proves the blended model is working?
The measure worth building the business case on is cost per successful resolution, not cost per containment. Containment counts the interactions an AI agent handled without escalation, which tells you what was deflected but not what was solved. Cost per successful resolution combines the credit and labour cost of an interaction with whether the customer actually got an answer, read alongside repeat-contact rate and customer effort. Measuring CRM ROI on that basis rewards automation that genuinely closes cases and quickly exposes automation that simply moves work somewhere less visible.
This is where the unified forecast earns its place a second time. Because AI consumption and human hours now sit in the same plan against the same queues, the numerator and denominator of that metric come from one system rather than two. Teams that instrument this early tend to find that their strongest automation is narrower than they expected and performs better than they expected, which is a good position to argue from when the next round of investment is discussed. One caution worth stating once: a forecast will not tell you on its own whether a representative received sufficient context after an AI handoff. Pair the numbers with a handful of reviewed transcripts each week and that blind spot closes quickly.
How does quality evaluation improve CRM adoption?
Adoption improves fastest when feedback is specific, frequent and clearly tied to something the representative can change. The quality tooling in this release is built for exactly that. A Quality Evaluation Agent assesses interactions at scale against defined criteria, screen recording captures how work was actually executed across systems, and coaching skills turn those signals into improvement plans and playbooks. Instead of a supervisor sampling a handful of cases a month, teams get consistent coverage and can direct coaching at the moments that genuinely move handling quality.
The August updates strengthened this further with real-time coaching and a rebuilt supervisor experience. Microsoft is also developing agentic capabilities for the administrative side of workforce management, letting supervisors and representatives check schedules, request time off, swap shifts and clock in or out through natural language in Teams, Copilot or on mobile without opening the full application. Removing that friction is a small thing that compounds, because scheduling tools fail on adoption far more often than they fail on forecasting accuracy.
What does a strong first ninety days look like?
Start narrow and let the results argue for the expansion. In the first month, confirm your licence entitlement, pick two high-volume queues with clean categorisation, and run a forecast scenario in parallel with the roster your planners build today. Comparing the two is the fastest way to build confidence in the model, and any gap between them usually points at a specific data issue rather than a flaw in the forecast.
In the second month, bring the AI Agent Estimator into the same scenario and model your existing automation as projected capacity rather than as a monthly invoice. Give finance a view of the output early, because a projected consumption curve tends to unlock support that a retrospective cost report never does. By the third month, turn on adherence tracking and quality evaluation on one team, agree what good looks like with the supervisors who will use it, and set your baseline for cost per successful resolution. Teams that follow roughly this sequence get to a defensible business case in a quarter, without a migration and without disrupting live service.
The Sirocco perspective
We work across Salesforce, HubSpot and Dynamics 365, so we look at releases like this one through the question our clients actually ask: does this reduce the number of systems we have to reconcile? Here it does. Bringing forecasting, scheduling, real-time operations and quality onto the same data as the cases themselves removes a genuine integration burden, and doing it inside licences most Dynamics 365 service organisations already hold makes the evaluation cheap to run. That is the kind of release we like seeing ship as standard.
An independent CRM partner is a consultancy that implements and advises across multiple CRM platforms without reselling any single vendor’s licences, which means the recommendation is shaped by the client’s operating model rather than by a quota. In this case, independence points in a clear direction. For organisations already standardised on Dynamics 365 Customer Service, the native suite is worth a serious evaluation before renewing a specialist workforce management contract. Organisations with deeply mature workforce management practices may still prefer their incumbent, and that is a legitimate outcome. The valuable part is that the comparison is now genuinely open, and buyers are the ones who benefit from that.
The wider shift is the one to plan around. Service capacity is becoming a single blended number rather than two, and the organisations that get there first will be the ones making deliberate trades between people and automation while everyone else is still reconciling them after the month closes. The tooling to do that is now standard equipment, and the work to take advantage of it is measured in weeks.
If you would like a second opinion on whether the native suite fits your service operation, schedule a consultation and we will walk through it with you.
Get in Touch
If you are weighing the native Dynamics 365 workforce engagement suite against a specialist workforce management contract, we are happy to talk through how your service data and queue structure would hold up.
