Recorded 16 Oct 2026 at 20:17 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.
Dynamics 365 Customer Service: Workforce engagement management - Detect intraday volume spikes with workforce alerts
Supervisors can create volume spike alerts that compare real-time conversation volume with the forecast linked to a shift plan. When volume remains above forecast for the configured number of intervals, selected recipients receive an in-app notification. The capability includes the following features: Administrators can enable workforce alerts in Copilot Service admin center by going to Workforce management > Intraday management > Workforce alerts . Supervisors can create and manage alerts from Workforce alerts in the Copilot Service workspace site map. Each alert references a shift plan and monitors the queues associated with its linked capacity plan. Supervisors can specify the percentage by which actual volume must exceed forecast volume. Supervisors can specify the number of consecutive intervals during which the deviation must continue before an alert is raised. The forecast determines whether an interval is 15, 30, or 60 minutes. Supervisors can set an expiration date to limit an alert to a campaign, season, or known event. Supervisors can select one or more notification recipients for each alert. Active alerts are evaluated on a recurring schedule. Notifications are sent wh…
What it said
- Roadmap ID
- 576761
- Status
- In development
- General availability target
- October CY2026
- Preview target
- August CY2026
- Products
- Dynamics 365 Customer Service
- Clouds
- Worldwide (Standard Multi-Tenant)
- Release phases
- General Availability, Preview
- Platforms
- Web
- Added to the roadmap
- 16 Oct 2026 19:08 UTC
- Last changed
- 16 Oct 2026 19:08 UTC
Recorded links
Source evidence when recorded
- Microsoft 365 roadmap
- Complete at observationRead 16 Oct 2026 at 20:16 UTC
Coverage describes the sources at this observation. A complete read then does not establish their current position.
What changed
First observed 16 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.