There is an important availability caveat: an October roadmap target is not confirmation of general availability. Microsoft Learn still identifies the experience as a production-ready preview. That distinction matters for administrators planning deployment, support, and change approval.
October target, but preview documentation remains
Roadmap item 576605 lists Dynamics 365 Contact Center’s web experience as “In development,” with general availability estimated for October 2026 in the Worldwide Standard Multi-Tenant cloud. Microsoft explicitly warns that roadmap dates and descriptions are estimates and can change. The record therefore establishes a target, not a completed rollout.
Microsoft’s historical release-plan entry lists public preview beginning June 22, 2026, with no general-availability date. Combined with the operational documentation’s preview label, the evidence does not independently confirm GA as of October 27, 2026. Organizations should not translate “production-ready preview” into “generally available.”
“Real time” has more than one meaning
The most useful detail goes beyond the promise of a faster dashboard: Microsoft distinguishes live metrics from aggregated metrics.
- Live metrics describe current conditions, including queue backlog, active conversations, online representatives, and longest wait time.
- Aggregated metrics summarize a selected period, including service level, abandon rate, and average speed to answer.
The Period filter governs aggregated figures; it does not turn live measures into historical snapshots. Live values instead follow applicable filters such as business unit, channel, and queue.
The Wallboard adds another timing distinction: its trend indicators update every five minutes. Microsoft’s example of an abandon-rate increase displayed as “+0.4%” means 0.4 percentage points since the previous interval. That comparison cadence should not be confused with the continuously updated live operational values.
In practical terms, a supervisor can be looking at today’s immediate queue pressure beside performance calculated over the last hour. Those figures answer different questions. Treating them as interchangeable would make a faster dashboard no wiser than a slower one.
From wallboard warning to queue-level diagnosis
Microsoft’s Wallboard brings conversation demand, staffing presence, backlog, longest pending wait, service level, abandon rate, and average speed to answer onto one screen. The release plan also describes full-screen presentation for high-resolution displays across the contact-center floor.
The detailed definitions are worth understanding before turning a card red into an operational emergency:
| Measure | Documented meaning |
|---|---|
| Queue backlog | Open incoming conversations waiting for assignment, including direct arrivals, virtual-agent escalations, and transfers. |
| Longest wait | The longest current pending wait in the selected queue; transferred conversations are measured from entry into the destination queue. |
| Average speed to answer | Average elapsed time from queue entry through assignment and acceptance by a representative. |
| Service level (20s) | Conversations accepted within 20 seconds, as a share of conversations accepted by human representatives; virtual-agent answers are excluded. |
These definitions come from Microsoft Learn’s Queues documentation. They provide a concrete comparison baseline rather than relying on familiar-sounding KPI labels.
Percentage calculations also depend on which conversations entered the measurement window. Microsoft explains that a last-15-minutes answer rate includes conversations offered during those 15 minutes—not an older conversation merely because it was answered recently.
The practical lesson: compare definitions and measurement windows before comparing this dashboard with another reporting system.
Supervisors can act, not just observe
Microsoft documents operational controls in the Representatives grid. Supervisors can change queue membership and presence, update skills and proficiency, and modify capacity profiles or capacity units. The grid also exposes consumed versus total capacity and representative workload.
For queue membership, the documented procedure is straightforward:
- Open Representatives.
- Select the relevant representatives using their checkboxes.
- Select Update queues.
- Assign, modify, or remove queue memberships.
Microsoft’s release plan also describes viewing conversation details and assigning or transferring conversations within the analytics experience. That connects monitoring with intervention rather than leaving supervisors to diagnose a problem in one application and resolve it elsewhere.
As an operational example—not a measured customer result—a supervisor could investigate rising backlog, review available capacity, and adjust suitable representatives’ queue memberships. The value is the shorter decision path; reduced waiting time remains an outcome to measure, not a guarantee.
Thresholds, self-service, and deployment checks
The roadmap promises configurable custom thresholds. Microsoft Learn confirms visual warning states and threshold details, but the inspected guidance does not establish a custom-threshold configuration procedure. The documented Self Service view covers containment outcomes, escalation trends, engagement volumes, customer intents, and operational health.
Before evaluation, administrators need configured, active Omnichannel for Contact Center, interaction channels producing live data, and the Omnichannel Supervisor role. Access also depends on the organization’s region and environment type.
Representative-level visibility deserves equal attention. Microsoft says the feature should not be used for employment decisions affecting compensation, rewards, seniority, or other entitlements. Its guidance also places responsibility on customers for applicable monitoring notices and consent, while encouraging notification to representatives.
The strongest case for this update is not that more numbers automatically create efficiency. It is that clearly defined metrics and nearby operational controls can help supervisors respond with better context. For administrators, the sensible next step is a scoped evaluation: validate access, reconcile KPI definitions, test permitted actions, and confirm release status before making wider rollout commitments.