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: Administrator experiences - Support average wait time in messaging API channels
Average wait time (AWT) is now supported for custom messaging channels built using the messaging APIs, apart from live chat and voice channels. The system computes the average wait time using an exponential moving average algorithm, giving more weight to recently connected conversations and automatically excluding abandoned ones. Administrators and supervisors can retrieve the wait-time metric through the representative availability APIs, enabling Copilot Studio agents or custom logic to decide whether to escalate, defer, or route conversations based on real‑time queue conditions. This enhancement ensures consistent wait‑time visibility across all supported channels, improving experience management and routing strategies. Business Value: Organizations using custom messaging channels built on messaging APIs can now provide customers with transparent and accurate wait‑time expectations. By surfacing estimated wait times directly through the availability APIs, contact centers can offer consistent experiences across voice, live chat, and custom channels. This helps reduce customer frustration, enables proactive decision‑making for AI agents and service representatives, and drives oper…
What it said
- Roadmap ID
- 576780
- Status
- Launched
- General availability target
- June 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.