Queues app for call queue agents and supervisors

What it does

A Microsoft app inside the Teams client that gives call queue agents and their leads a queue-focused view: real-time and historical stats, agent opt-in/out, queue settings changes, shared call history and monitor/whisper/barge/takeover. It's the closest native Teams gets to a supervisor desktop.

Key facts

Every Queues app user needs both Teams Phone and Teams Premium. That's agents as well as supervisors, not just the leads. Users must be voice-enabled.
It's enabled by default for anyone licensed for both; allow up to 48 hours after licensing before it appears.
Agents must be members of at least one call queue. Leads get their powers as authorized users on the AA/CQ, controlled by a Teams voice applications policy — you can have several policies (e.g. supervisor vs shift lead) with different rights.
Real-time metrics: calls waiting, average wait, longest wait — shown in the signed-in user's local time zone from midnight.
Historical reporting: up to 45 days, reported in UTC.
Monitor, whisper, barge and takeover need conference mode on the queue and the Teams desktop client. Shared call history also needs the app and is desktop-only.
Supported on Teams desktop (Windows and Mac), VDI, iOS/Android and touch Teams phones. Not on the web client.
Limits: up to 200 agents per queue; recommended no more than 100 queues per user, hard limit 200.
AAs and CQs nested without a resource account can't be edited by authorized users in the app.
Available in Commercial, GCC, GCC High and DoD, in regions where Teams Phone is sold.
Disabling it means turning off Microsoft apps org-wide, which also takes out other Microsoft apps such as Tasks and Insights. Use app permission/setup policies to target instead.

When to use / skip

Use it when a team lead needs to see the queue and act on it without raising an admin ticket — moving agents in and out at lunch, changing the greeting for a snow day, listening in on new starters. For a service desk or a small customer service team that's already on native queues, it closes most of the "we can't see anything" complaint.

Skip it when the numbers don't work. The Premium-for-every-agent requirement is the deal-breaker: forty agents who only need to answer calls now need Premium so their supervisor can whisper to them. Clients often already have Premium for meetings features and that changes the maths, so check before ruling it out. If the requirement is genuine contact centre reporting — SLA by interval, abandon rate trends, WFM — the Queues app isn't that, and a certified solution or Power BI on the call queue historical reports is the honest answer.

Configuration decisions

Who gets Premium: all agents on the queues where you want supervisor features, or none. Partial licensing creates a split experience on the same queue.
How many voice applications policies, and what each allows — greeting and music changes, agent membership, call flow edits, monitoring.
Which queues need resource accounts so leads can manage them in the app, rather than being nested purely as voice apps.
Whether to pin the app through a Teams app setup policy for agents and leads or leave it to "View more apps".
Whether to hide some authorized users from the app (Set-CsCallQueue -HideAuthorizedUsers) — useful for IT admins who are authorized but shouldn't appear to agents.
Who reads historical reports in UTC and whether that's acceptable for a UK team during BST.

Gotchas

Licensing a user doesn't make the app appear immediately. Up to 48 hours — don't schedule supervisor training the morning after licences land.
Historical data is UTC and real-time is local time. In summer, a UK supervisor's 09:00–10:00 is 08:00–09:00 in the history view. Expect a ticket.
Monitor/whisper/barge are desktop-only. Supervisors who live on a Teams phone or mobile can see stats but not coach live.
Authorized user without a voice applications policy, or a policy without being an authorized user, gives you nothing — and no error saying why.
Service level metrics aren't in historical reporting, and changing the service level threshold mid-day skews that day.
Turning the app off via org-wide Microsoft apps settings also kills unrelated apps.

Consultant notes

Confirm the licensing position in the client's own tenant (Microsoft 365 admin center > Licenses) before scoping. Many already own Premium.
Build voice applications policies by role, not by person, and document what each one can change. Supervisors will try to edit the call flow sooner or later.
Train leads on opt-in/out and greeting changes first — that's 80% of the value.
For a Dynamics 365 Contact Center or certified-vendor project, the Queues app is irrelevant to those agents. Don't buy Premium for it by accident.
Set expectations: this is a supervisor view on native queues, not a contact centre reporting suite.

Worth revisiting if Microsoft relaxes the Premium requirement for agents, or brings monitor/whisper to Teams phones