That is a planned release window, not a shipping announcement. The item’s individual details were not exposed in the public roadmap page’s readable content during verification; its schedule and scope come from the roadmap record accompanying the announcement. Microsoft also cautions that roadmap dates are estimates and can change.
What changes—and what already works on mobile
The important distinction is that Queues itself is already available on Teams mobile. Microsoft Support documents mobile access to assigned queues, queue membership details, participation controls and queue-related call history. Representatives can opt themselves in or out, while supervisor leads can manage participation for multiple team members. The upcoming feature adds live operational visibility to that existing mobile experience; it is not the app’s mobile debut.
That combination could be useful for a lead moving between locations or a representative deciding whether to rejoin a busy queue. Participation controls answer “Can I take calls?” Live metrics could help answer “Where am I needed?” This is a practical interpretation of the planned change, not evidence of measured improvements in answering times.
Which metrics will appear?
The roadmap description does not enumerate the mobile counters, so it would be premature to promise a miniature version of every desktop dashboard.
For context, Microsoft’s existing Queues analytics documentation describes these real-time call-queue measures:
| Existing measure | What it tells users |
|---|---|
| Waiting calls | How many callers are currently queued |
| Average answering time | The average delay between entering the queue and being answered |
| Longest current wait | How long the longest-waiting caller has been queued |
| Abandoned percentage | The share of offered calls that callers abandoned |
| Total offered calls | The volume offered to the queue |
| Unanswered calls | Calls not answered, including abandonment, timeout, overflow and no-agent outcomes |
These are documented existing metrics, not a confirmed mobile feature list. Microsoft’s analytics guidance also distinguishes real-time reporting, which covers the current day from midnight local time, from historical reporting, which uses UTC. The mobile announcement does not establish identical time handling, historical analytics support or agent-level reporting parity.
The takeaway: “real-time” should not automatically be read as “only this instant.” Existing reporting includes both current conditions and accumulated activity for the day.
Licensing and permissions still matter
A new mobile view does not make reporting universally accessible. Microsoft Learn currently requires Teams Phone and Teams Premium licenses for Queues app users, along with voice enablement and membership in at least one call queue. Microsoft says the app can take up to 48 hours to appear after Teams Premium licensing. These are existing app requirements; the roadmap record does not announce a separate licensing arrangement for mobile metrics.
Reporting access is also policy-controlled. Microsoft documents separate settings for real-time queue metrics and real-time representative metrics: RealTimeQueueMetricsPermission and RealTimeAgentMetricsPermission. Its guidance says the tenant-wide All value is no longer supported for these real-time permissions; authorized reporting access is scoped to the queues and associated representatives the user is authorized to view.
For administrators, that makes an access review a sensible preparation step. Confirming that a supervisor can open Queues is not the same as confirming that the supervisor has the intended reporting permissions.
What teams can check now
Organizations can validate the existing mobile workflow before the planned metrics release:
- Open Teams on Android or iOS.
- Tap More in the tab bar and locate Queues, swiping through the app tray if necessary.
- Confirm that assigned queues appear.
- Check the queue’s participation toggle and call history.
- For authorized supervisor leads, open a queue’s People tab to review the existing bulk participation controls.
These steps validate today’s documented app access—not the unreleased analytics interface. If Queues is missing, administrators should first check licensing, voice enablement and queue membership rather than assume the December feature has failed to arrive.
A focused upgrade, with details still to come
The proposed improvement is straightforward: put current queue conditions within reach of the people already managing participation from their phones. It could reduce unnecessary trips back to a desktop, but a dashboard does not create extra staffing capacity.
The unresolved details are the exact mobile metric selection, role-specific visibility, minimum client versions and rollout timing within December. Until those are documented, the sound approach is to prepare existing access and permissions while treating December 2026 as a target—not a guarantee.