Dynamics 365 Workforce Alerts: Configure Intraday Volume Spike Notifications

Tracked under Microsoft's AI at Work Roadmap ID 576761 (and previously surfaced to administrators via Microsoft 365 Message Center notice MC1455051), the capability lets supervisors configure automated rules that compare real-time conversation volume against the forecast tied to an active shift plan. When actual demand exceeds the forecasted baseline by a defined percentage across a specified number of consecutive time intervals, the system dispatches an in-app notification directly inside the Copilot Service workspace.

Roadmap Status and Rollout Reality​

According to Microsoft's AI at Work Roadmap entry 576761, intraday volume spike alerts entered public preview in August 2026 and are slated for General Availability in October 2026 across Worldwide (Standard Multi-Tenant) cloud instances on the web platform. However, enterprise administrators should note two important caveats when planning their deployment:

• Roadmap Status: As of mid-October 2026, Roadmap ID 576761 still carries an "In development" status marker, and Microsoft explicitly notes that roadmap dates are estimates subject to change.
• Documentation Labeling: Microsoft Learn's official technical documentation for the feature—last updated in August 2026—still designates the capability as "Use workforce alerts for volume spikes (preview)" and reminds administrators that preview functionality is subject to supplemental terms and not intended for unvetted production reliance.

In short, while the capability is actively arriving in tenants with the October 2026 window underway, IT administrators should verify its state in their specific environment and treat its current preview limitations with appropriate operational caution.

Section Summary​

• Feature: Automated intraday volume spike alerts for Dynamics 365 Customer Service and Contact Center.
• Tracking IDs: AI at Work Roadmap ID 576761 and Message Center ID MC1455051.
• Availability: Preview began August 2026; General Availability is targeted for October 2026 for Worldwide multi-tenant web environments, though Microsoft Learn documentation still reflects preview status and limitations.

How Intraday Volume Spike Alerts Work Under the Hood​

At its core, Workforce Management in Dynamics 365 connects three sequential stages of the planning lifecycle: Forecasting (predicting conversation volume and average handle time), Capacity Planning (calculating how many representatives are needed to meet demand), and Scheduling (publishing the actual shift plans).

Volume spike alerts sit directly on top of this connected data model. Rather than monitoring arbitrary, standalone queues in a vacuum, every volume spike alert must reference a published shift plan that has a linked capacity plan and forecast. Because those records are linked, the alert automatically knows which queues belong to the shift plan and what the forecasted volume baseline should be for every interval of the day.

Once an alert is active and unexpired, a background evaluation engine runs every five minutes. According to Microsoft Learn documentation, each five-minute cycle performs a five-step check:

1. It identifies all queues included in the shift plan referenced by the alert.
2. It pulls the actual conversation volume for each recently completed interval across those queues.
3. It retrieves the expected conversation volume for the exact same interval from the linked forecast plan.
4. It calculates the percentage deviation above the forecast. If the actual volume exceeds the forecast by at least the configured threshold percentage, that interval is marked as meeting the threshold.
5. It checks whether the required number of consecutive intervals have met the threshold. When that consecutive count reaches the supervisor's configured duration, the engine sends an in-app notification to the designated recipients.

What happens if volume spikes for one interval and then dips back below the threshold on the next? The consecutive counter resets to zero. Microsoft's design intentionally filters out brief, one-off blips so supervisors are only interrupted when a sustained demand shift threatens queue health.

What the Feature Does Not Do​

It is equally important to understand what workforce alerts do not do. Per Microsoft Learn documentation, volume spike alerts are strictly informational. They do not automatically reroute conversations, summon backup agents, modify published schedules, or adjust capacity plans. When an alert fires, human supervisors remain entirely in the driver's seat to decide whether to move representatives from lower-priority queues, offer overtime, postpone offline administrative work, or reschedule training sessions.

Section Summary​

• Data Dependency: Alerts require a published shift plan linked to both a capacity plan and a forecast.
• Evaluation Cadence: A background monitor checks recently completed intervals every five minutes.
• Consecutive Logic: Threshold breaches must occur across consecutive intervals; a single normal interval resets the count.
• Informational Scope: The system notifies supervisors but never alters routing or schedules automatically.

Prerequisites and Administrator Enablement Guide​

Because workforce alerts are turned off by default, contact center supervisors will not see the alerting tools in their workspace until an administrator completes the backend setup.

Technical Prerequisites​

Before flipping the switch, administrators and workforce planners must verify four requirements outlined in the Microsoft 365 roadmap and Microsoft Learn documentation:

• Package Installation: An administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.
• Configured Planning Pipeline: Forecasting and scheduling must be configured, with a published shift plan linked to an associated capacity plan and forecast. Manually created shift plans that lack a linked capacity plan cannot be used for volume spike alerts.
• Queue Assignment: The specific queues you intend to monitor must be included inside the capacity plan linked to the target shift plan.
• Live Telemetry: Real-time conversation data must be actively flowing and available for those monitored queues. (Note: Microsoft Learn's forecasting documentation specifies that forecasts measure conversations handled by human representatives and exclude conversations resolved entirely by AI agents without a representative joining.)

Step-by-Step Admin Enablement​

Once the prerequisites are in place, an administrator can enable the capability in the Copilot Service admin center:

1. Open the Copilot Service admin center site map and navigate to Operations > Workforce management.
2. On the Workforce management page, expand the Intraday management section.
3. Locate Workforce alerts (preview) and select Manage.
4. Toggle Enable workforce alerts to On.

Supervisors who are already logged in will need to refresh their Copilot Service workspace browser tab for the Workforce alerts entry to appear in their site map. If an administrator later turns this toggle off, Microsoft Learn notes that existing alert definitions are preserved in the database, but notifications stop firing and supervisors lose the ability to create or edit alerts.

Supervisor Configuration: Setting Up Volume Spike Alerts​

Once enabled, supervisors can build and manage rules directly from the Copilot Service workspace by selecting Workforce alerts from the site map and clicking New > Volume spike alert.

Understanding Interval Math​

A critical detail in the table above is how interval duration works. Supervisors do not pick minutes directly when configuring an alert; they pick a number of intervals (such as 1, 2, or 3). The length of an interval—whether 15, 30, or 60 minutes—is dictated entirely by the underlying forecast linked to the shift plan.

For example, Microsoft Learn notes that standard short-term and weighted-average intraday forecast scenarios operate on 15-minute intervals. If your shift plan uses a 15-minute forecast and you configure an alert with Above forecast (%): 25 and For duration (intervals): 2, actual conversation volume must stay at least 25 percent above forecast for two back-to-back 15-minute blocks—30 minutes in total—before the alert triggers. If volume surges by 30 percent for the first 15 minutes and drops back to +10 percent in the second 15 minutes, no notification is sent.

Reading and Resolving Alerts​

When an alert triggers, selected recipients who are signed into the Copilot Service workspace receive an in-app notification and can also access the alert via the Workforce Alert icon in the workspace side panel. Opening the alert reveals:

• Title and Status: The specific queue that triggered the alert, the alert name, and whether the state is currently Active or Resolved.
• Spike Metrics: Detection timestamp, current actual volume versus forecast volume for the latest evaluated interval, and the exact spike percentage.
• Interval Breakdown Table: A row-by-row chronological table showing each interval's start time, forecast volume, actual volume, percentage above forecast, and whether the threshold was met.

This breakdown table is where the real operational value lives. By scanning the progression across intervals, a supervisor can immediately tell whether a spike is plateauing on its own or accelerating into a full-blown crisis. An alert automatically transitions to Resolved once conversation volume stays below the configured deviation threshold for the configured number of intervals.

Real-World Edge Cases, Limitations, and Best Practices​

While automated volume spike detection is a welcome addition to Dynamics 365's native Workforce Engagement Management suite—helping organizations rely less on bolting on external third-party workforce tools for basic intraday awareness —it comes with mathematical quirks and architectural boundaries that teams must plan around.

The Zero-Forecast Trap (+100% Spikes)​

How do you calculate a percentage increase when the starting baseline is zero? In standard arithmetic, dividing by zero is undefined, so Microsoft's evaluation engine uses a fallback rule: whenever forecast volume for an interval is zero and even a single conversation arrives, the system reports the deviation as +100 percent.

Similarly, on low-volume queues—say, a specialized escalation queue forecasted for just two conversations per 15-minute interval—receiving four conversations represents a 100 percent spike. If a supervisor leaves the default Above forecast (%) threshold at 5 percent and For duration at 1 interval on a quiet or after-hours queue, recipients will be pelted with nuisance alerts. For low-volume queues, Microsoft Learn explicitly recommends raising the percentage threshold significantly or requiring a longer consecutive duration (two or more intervals).

Crucial Preview Limitations​

Administrators evaluating this tool need to weigh three documented preview constraints:

1. In-App Delivery Only: Notifications are delivered exclusively inside the Copilot Service workspace web interface. There is no native email, SMS, or Microsoft Teams webhook push documented for this feature; recipients must be actively signed into the workspace to see them.
2. Volume Only (No AHT or Staffing Telemetry): The monitor strictly counts incoming conversation volume. If conversation arrivals match the forecast perfectly, but a tricky product bug doubles your Average Handle Time (AHT) or three agents call in sick, a volume spike alert will not fire. Supervisors still need real-time adherence trackers and queue dashboards to spot handle-time bloat or staffing shortfalls.
3. Five-Minute Evaluation Lag: Because the background job runs on a five-minute timer and evaluates recently completed intervals, notifications can arrive up to one full monitor cycle after the triggering interval finishes. It is built for 15-to-60-minute intraday course correction, not sub-minute emergency intervention.

Operational Best Practices​

To get the cleanest signal-to-noise ratio out of Dynamics 365 workforce alerts, consider following Microsoft's operational guidance:

• Abandon the 5% / 1-Interval Defaults: A 5 percent variance over a single interval is normal contact center noise. Start conservatively with a higher percentage (such as 20 to 25 percent) and a duration of at least 2 consecutive intervals, then tune downward as your historical forecast accuracy matures.
• Isolate Temporary Events: Rather than weakening a permanent alert rule to accommodate a holiday sale or product launch, create a dedicated alert for the campaign and set its Alert expiration date to the end of the event. If you want to pause an alert without losing its configuration, simply deactivate it or set its expiration date to the past in the Intraday volume spike alerts view.
• Audit Alerts After Plan Edits: Because an alert inherits its monitored queues and baseline numbers directly from its linked shift and forecast plans, always review your active alerts whenever workforce planners modify shift plans or swap forecast snapshots.

Section Summary​

• Zero-Forecast Math: Any incoming conversation during a zero-forecast interval registers as a +100% spike, requiring higher thresholds or durations on quiet queues.
• Current Boundaries: Alerts only track conversation volume (ignoring AHT and agent absenteeism), run on a 5-minute polling cycle, and require recipients to be signed into the Copilot Service workspace.
• Tuning Advice: Replace the sensitive defaults (5% / 1 interval) with multi-interval rules, use expiration dates for seasonal events, and re-verify alerts whenever underlying shift plans change.