Dynamics 365 Customer Service WEM Intraday Performance Report: Forecast vs. Actual Setup

While the roadmap entry—published on October 16, 2026—still carries an "In development" status label, it lists an estimated public preview target of August 2026 (which M365 Admin reporting pegged to August 28, 2026 ) and a targeted General Availability window of October 2026 for Worldwide (Standard Multi-Tenant) web environments. Microsoft's 2026 release wave 1 plan for Dynamics 365 Customer Service independently corroborates those August preview and October general availability milestones. As always with Microsoft roadmap listings, those dates represent planned delivery windows rather than confirmation that rollout has completed across every tenant, and administrators, makers, or business analysts must explicitly configure and enable the capability before end users can see it.

Why Intraday Visibility Matters More Than Post-Mortem Reports​

Why do contact center managers spend so much time fighting fires that started two hours ago? Because traditional workforce reporting separates the planning tools from the operational telemetry. Forecasts and shift plans are typically built days or weeks in advance, locking in assumptions about interaction volume, handle time, and representative availability. When real-world demand deviates from those assumptions, two expensive problems compound quietly in the background:

1. Under-forecasted or under-staffed intervals: Customer wait times climb, service level agreements (SLAs) slip, abandonment rates rise, and management ends up paying premium overtime rates in a frantic bid to dig out of the backlog.
2. Over-forecasted or over-staffed intervals: Representatives sit waiting for interactions that never arrive, leaving organizations paying for idle capacity that could have been redirected to back-office queues, coaching, or scheduled training.

By placing forecast-versus-actual metrics into a unified intraday view, Microsoft aims to give supervisors visibility while an interval is still actionable. However, it is important for IT leaders and operations managers to separate the software's reporting mechanics from operational execution. The intraday performance report is a diagnostic and monitoring dashboard—it does not automatically reroute queues, cancel training blocks, or authorize overtime on its own. Instead, it hands human supervisors the empirical evidence needed to make those tactical calls—such as shifting representatives between queues, rescheduling break or training windows, or opening targeted overtime—before the rest of the shift unravels.

Inside the Intraday Performance Report: Metrics, Intervals, and Filters​

Accessed in the Copilot Service workspace site map under Workforce management (and also surfaced under the Monitoring -> Intraday performance node in Microsoft's standalone Workforce Engagement Management app currently in preview), the report consolidates three major operational dimensions into a single pane of glass:

• Volume and Handle Time Variances: Supervisors can compare forecasted contact volume and average handle time (AHT) directly against actual incoming volume and actual handling durations. Crucially, the report calculates and displays variances as both raw values and percentages, making it much faster to spot statistical outliers without doing mental math across columns.
• Three-Tier Staffing Comparisons: Rather than simply showing how many people are logged in, the report lines up forecasted, required, and scheduled staffing levels side by side. This distinction is vital for root-cause analysis: it tells a supervisor whether an understaffed interval is failing because demand exceeded the original forecast (requiring more staff than planned) or because the schedule itself failed to cover the original requirement.
• Operational Health Metrics: Alongside volume and headcount, the report displays service level, occupancy, and schedule adherence in the same view.

To accommodate different operational rhythms across industries, supervisors can toggle the report granularity between 15-minute, 30-minute, or 60-minute intervals, and filter the entire view by planning group and shift plan to isolate the exact teams and queues under their jurisdiction.

Note on technical boundaries: While Microsoft Learn's release plan descriptions refer broadly to real-time optimization within Workforce Engagement Management, the roadmap specification for item 576748 does not publish a specific data refresh cadence, telemetry latency figure, variance calculation formula, or data export specification for this report. Administrators should evaluate the exact refresh behavior in their environment once enabled.

How the WEM Data Pipeline Powers the Report​

To get accurate numbers out of the intraday performance report, administrators and workforce planners need to understand how Microsoft's Workforce Engagement Management architecture connects the underlying data. According to Microsoft Learn documentation, the metrics appearing in the intraday view are not standalone numbers; they are the downstream product of a tightly linked configuration chain:

1. Planning Groups as the Foundational Boundary: In Dynamics 365 WEM, a planning group is far more than a display filter. Microsoft Learn defines it as the foundational planning unit that binds specific queue and channel combinations (such as Voice, Chat, or Email) into a single demand scope, governed by a unified time zone and a shared set of service objectives. To prevent double-counting interaction volumes across forecasts, a specific queue-and-channel combination can belong to only one planning group at a time.
2. Service Objectives: Each planning group carries configured targets that drive capacity math, including Service Level (%) and Target Answer Time (seconds) (for example, answering 80 percent of interactions within 20 seconds), Shrinkage (%) (planned and unplanned unavailable time for breaks, training, coaching, or absences), Concurrency (how many simultaneous interactions a representative handles, such as 1 for voice), and Occupancy (%) (the share of logged-in time spent actively handling interactions and related after-call wrap-up work).
3. Forecast Scenarios to Capacity Plans to Shift Plans: Forecasting models expected volume and AHT per channel and queue (and notably excludes conversations handled entirely by AI agents without a human representative joining). Short-term linear forecast scenarios and preview weighted-average scenarios generate projections in 15-minute intraday intervals. Capacity planning then ingests that forecast snapshot alongside the planning group's service objectives to calculate required staffing, and shift plans convert those requirements into actual representative schedules.

Because the intraday performance report filters by planning group and shift plan, any inconsistency in how an admin structures planning groups or service objectives will directly affect what supervisors see during the day. If a multi-channel team requires separate service-level targets for voice versus asynchronous chat, Microsoft recommends building separate planning groups for those channel scopes so capacity targets and intraday reporting remain mathematically consistent.

Critical Timeline Context: Legacy Forecasting Deprecation on October 30, 2026​

The October 2026 general availability window for this intraday performance report is not happening in a vacuum. According to Microsoft Learn's documentation for Dynamics 365 Customer Service and Dynamics 365 Contact Center, Microsoft is officially deprecating the legacy forecasting for case and conversation volumes and for customer service representatives for conversations effective October 30, 2026. Support for those older forecast reports ends on that date, after which the legacy feature will be removed entirely.

For organizations still relying on those older reports—which were limited to monthly data refreshes and basic 15-minute or daily volume grids—Microsoft explicitly directs administrators to migrate to forecast scenarios in Workforce Engagement Management. Pairing modern WEM forecast scenarios with the new intraday performance report (and sibling WEM features reaching general availability in October 2026, such as intraday volume spike workforce alerts under Roadmap ID 576761 ) represents the modern replacement path for contact center demand management.

Prerequisites and Step-by-Step Admin Setup Guide​

Because this capability is classified as Enabled by admins, makers, or analysts for end users, it will not appear in Copilot Service workspace out of the box without prerequisite setup. Below is the verified administrative workflow documented by Microsoft Learn to get the underlying Workforce Management architecture in place.

Step 1: Install the Workforce Management Package​

Before any WEM features—including planning groups, forecast scenarios, or intraday reporting—can be configured, a System Administrator (or user with equivalent permissions) must deploy the solution package:

1. Sign in to the Power Platform admin center.
2. In the left site map, select Environments, and choose your target Dynamics 365 environment.
3. On the top toolbar, select Resources > Dynamics 365 Apps.
4. Select Install App from the command bar.
5. Locate and select Workforce Management for Customer Service from the list of available applications, then click Next.
6. Review and accept the terms of service, and click Install.

Step 2: Assign Appropriate Security Roles​

Access to workforce management nodes depends on which application experience your organization uses:

• In Copilot Service workspace (Generally Available): The Omnichannel supervisor role grants access to workforce management capabilities as a bundled supervisory experience. (Note that underlying forecast data access also requires a security role with Read privileges on the msdyn_dataanalyticsreport_forecast table).
• In the standalone Workforce Engagement Management app (Preview): Microsoft offers granular, function-specific preview roles—including WFM Administrator, WFM Forecaster, WFM Scheduler, WFM Intraday Analyst, and WFM Service Rep—allowing admins to give an intraday analyst read-only monitoring access to plans and performance without granting broad permission to alter or publish schedules. Note that during preview, the standalone WEM app runs solely as a single-session app and does not support multisession experiences.

Step 3: Verify Planning Groups and Shift Plans​

To ensure supervisors can actually filter and compare data in the intraday performance report:

1. Open Copilot Service workspace and navigate to Workforce Management > Planning Groups.
2. Confirm that active planning groups have been created with an accurate Time Zone, a defined Demand Scope (queue and channel combinations configured in Customer Service admin center or Copilot Service admin center), and associated Service Objectives.
3. Ensure that an active Forecast Scenario, Capacity Plan, and Shift Plan are linked to each planning group via the Planning Group lookup field.
4. Once enabled in your tenant, supervisors can navigate to Copilot Service workspace > Workforce management to open the intraday performance report, select their Planning Group and Shift Plan, choose a 15-, 30-, or 60-minute interval, and begin monitoring live operational execution against the forecast.

Governance and Compliance Considerations​

Finally, as organizations roll out deeper interval-level monitoring of occupancy, handle times, and schedule adherence, IT and legal teams should keep Microsoft's compliance guidance in mind. In its Workforce Management forecasting documentation, Microsoft explicitly states that these analytics features are designed to help supervisors improve team performance and customer satisfaction—and must not be used to make decisions affecting employee compensation, rewards, seniority, or other employment rights and entitlements. Administrators remain solely responsible for configuring Dynamics 365 Customer Service and Copilot Service workspace in compliance with local labor and privacy regulations, including employee notification and end-user consent requirements for monitored communications.