Microsoft Teams Desk Phones - AI Features and Roadmap

Who should listen: Microsoft 365 service owners, Teams Phone administrators and UC consultants running desk phone estates — particularly those supporting contact centres, retail, healthcare or common area deployments, and anyone planning line key standards or migrations from legacy PBX handsets.

Guest: Prashi Badkur — Senior Product Manager Lead, Teams Phone Devices, Microsoft

Prashi Badkur leads product management for Teams Phone devices at Microsoft, owning the user experiences on desk phones and working with the OEM and deployment teams. She sets out why demand for physical phones persists, what Copilot and voice control will bring to small-screen devices, and the near-term roadmap for line keys, the Queues app, common area phone contacts and MDEP.

Many thanks to Ribbon, sponsor of this episode.

Key insights

• Desk phones are positioned as a companion to soft clients rather than a replacement. The persistent buyers are receptionists, contact centre agents and frontline workers who transfer calls at high volume — Badkur cites scenarios of roughly 30 transfers an hour where tactile line keys beat a mouse — plus finance, healthcare and emergency services needing dedicated 24/7 lines.
• Agents often pair a headset with a desk phone rather than a PC softphone, because it gives consistent audio and removes desktop pop-ups and distractions during calls.
• Copilot-generated call summaries now travel with a transfer, so the receiving person gets instant context instead of the caller repeating themselves — and this works on the physical phone, not just the desktop client, so common area and reception users aren't left out of the AI features.
• Voice is the next interaction model for small-screen phones: speaking a search instead of typing it, issuing a context-aware forward or transfer command, and using Copilot to help discover features on first use, alongside a start-of-day recap when a user signs in to their device.
• Roadmap prioritisation runs on three buckets — fundamentals (reliability, performance, touch responsiveness), closing telephony feature gaps that block customers, and intelligence/AI — and the balance is reviewed roughly monthly rather than per semester.
• Line keys keep expanding: speed dials, shared lines with LED states showing boss availability and incoming calls (delegates can resume a held call with one key press), per-line custom ringtones so a multi-store site can tell which store is calling without looking at the screen, and dedicated call-control keys such as a one-press transfer.
• Line key configuration is moving into Teams Admin Center via device templates — define the key layout for a model such as the CCX 400 and apply it at scale — which removes the need to touch every handset at every site. In preview now, with general availability expected shortly.
• The Queues app on desk phones is deliberately agent-only: opt in and out of queues and view call history on the handset, while supervisors with analytics needs stay on the desktop experience.
• Contact management for common area phones lets admins preload speed dials, such as internal security or a building front desk, from Teams Admin Center rather than signing in on each device; it came through preview with strong feedback and is close to release. Real-time text is also now supported on devices for users with speech disabilities.
• MDEP support on phones brings the devices into the Microsoft security stack, and is expected to simplify provisioning and management as well as enable on-device AI services such as translation and speech-to-text with lower latency.

Insights summarised by AI from the episode transcript, reviewed by the Empowering.Cloud team.

Listen: Apple Podcasts · Spotify · Other platforms