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 Contact Center: Unified routing - Use average wait-time diagnostics for wait-time predictions
This feature introduces comprehensive event logging in Application Insights that captures exactly how average wait time is computed, evaluated, and shown to customers. End-to-end average wait-time diagnostic events The system logs detailed AWT diagnostic events in Application Insights at two key moments: When a conversation begins and the system evaluates whether average wait time should be shown. When the availability APIs return the average wait-time value (if applicable). Each event includes standard metadata (channel type, organization ID, conversation ID, scenario, and subscenario) and feature-specific fields such as calculated average wait time in seconds, whether average wait time was shared with customers, and reason. This allows administrators to pinpoint the exact cause when average wait time is missing or is an unexpected value. Historical analytics for average wait-time accuracy Supervisors can compare: Average wait-time values shown to customers. Actual wait times experienced by conversations. This helps teams validate prediction quality, identify discrepancies, and tune overflow thresholds. Business Value: Average wait time (AWT) is one of the most visible and impact…
What it said
- Roadmap ID
- 576779
- Status
- Launched
- General availability target
- August CY2026
- Preview target
- Not stated
- Products
- Dynamics 365 Contact Center
- Clouds
- Worldwide (Standard Multi-Tenant)
- Release phases
- General Availability
- 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.