What the mobile feature promises
The roadmap description outlines a post-call workflow: open shared call history, ask Copilot about a past conversation, and retrieve relevant information to help decide what to do next without reviewing the entire call. Its stated audience is agents and supervisors handling customer conversations, rather than everyone using Teams chat or meetings. The listing identifies Worldwide (Standard Multi-Tenant) as its cloud scope; its General Availability release designation should not be confused with an announcement that the feature has already shipped.
The practical appeal is straightforward: catching up on a customer conversation from a phone could make a handoff less cumbersome. That is an interpretation of the proposed workflow, not a measured productivity result. Asking for context is also different from having software perform the follow-up automatically; the description promises information and insights, not autonomous case resolution.
Mobile Queues support already exists
An important distinction comes from Microsoft Learn: the Queues app itself already supports iOS and Android. The December roadmap item concerns the additional Copilot experience, not the arrival of the underlying app on mobile. Microsoft describes Queues as a Teams-native tool for Teams Phone call queues and auto attendants, with queue-management, reporting and supervisor capabilities.
For administrators, that separates two deployment questions: can staff access Queues today, and will they qualify for this particular Copilot capability when it arrives?
Microsoft’s documented requirements for the existing Queues app include:
- A Teams Phone license and a Teams Premium license.
- A voice-enabled user account.
- Membership in at least one call queue.
Microsoft also warns that Queues can take up to 48 hours to appear after Teams Premium licensing is assigned. These are baseline app requirements, not a confirmed licensing checklist for the forthcoming Copilot feature.
What administrators should wait to confirm
The feature description does not specify additional Copilot licensing, recording or transcription requirements, minimum mobile app versions, language support, or how access to earlier conversations will be controlled. Those omissions should remain open deployment questions—not be converted into assumed requirements.
Before scheduling a pilot, administrators should seek confirmation of those details and establish how staff will validate important information before acting on it. There is no evidence here for changing recording policies or purchasing additional licenses specifically for this feature yet.
The takeaway: Microsoft’s plan targets a useful, narrow task—recovering customer-call context on a mobile device. Existing Queues access can be assessed now, but the new Copilot workflow remains a roadmap commitment with a December estimate, not a feature users should expect to find in their app today.