May 1, 2026

Microsoft Adds Teams Call Delegation and Consecutive Interpretation, Bringing Copilot Closer to Real Conversations

Product Updates | April 30, 2026 | Microsoft Community Hub

Microsoft’s April 30, 2026 Copilot update for Teams is less about flashy AI and more about putting automation into the moments people actually struggle with: incoming calls, multilingual meetings, and live scheduling. The latest additions make Copilot more useful as an active participant in conversations, not just a post-meeting summary tool.

That matters because a lot of day-to-day work still happens in real time. If AI can screen a call, gather context, book a follow-up, or keep a two-language meeting moving without forcing everyone into a single-language script, it starts to change how teams handle interviews, customer calls, and cross-border collaboration.

What Microsoft announced on April 30, 2026

In its April 30, 2026 “What’s New in Microsoft 365 Copilot” update, Microsoft highlighted two Teams-specific additions tied to Copilot: call delegation and consecutive interpretation. Call delegation lets Teams handle incoming calls on a user’s behalf, gather context, and, where needed, schedule follow-up appointments through Microsoft Bookings. The practical point is that Teams is moving beyond simple message assistance and into call handling workflows that can reduce the number of live interruptions a user has to personally absorb.

Microsoft also said consecutive interpretation is now available in Teams Interpreter Public Preview. This creates a turn-based flow for meetings that involve two languages, making it easier for participants to speak, pause, and receive interpretation before the conversation continues. Microsoft positioned these changes as part of a broader April Copilot release wave rather than a one-off feature announcement, which is consistent with the company’s recent cadence across Microsoft 365 Copilot, Teams, and developer-facing updates from April 2026.

Why this matters for meetings, interviews, and live conversations

For professionals, call delegation can function as a lightweight front line for screening unknown or low-priority calls. Instead of forcing every incoming call to interrupt the user immediately, Teams can collect context and help route the next step, including a follow-up appointment when appropriate. That makes the feature useful for busy schedules, intake processes, and situations where the first contact is more about triage than immediate conversation.

Consecutive interpretation is equally practical in live settings where language friction usually slows things down. In multilingual interviews, classes, and cross-border meetings, a turn-based format makes back-and-forth dialogue easier to follow without requiring everyone to speak over one another or rely on a separate translation layer after the fact. Taken together, these updates move Teams Copilot call delegation and interpretation closer to real-time assistance, where the value comes from helping people stay in the conversation while it is happening.

What changed in the AI assistant playbook

Microsoft’s April 30, 2026 Copilot update for Teams pushes the assistant closer to the center of live work. Instead of acting only as a recap engine after a meeting or call, Copilot is now positioned as part of the communication layer itself: it can answer incoming calls on a user’s behalf and support consecutive interpretation in multilingual meetings. That is a meaningful shift in product design, because it treats AI as something that can sit in the flow of a conversation, not just clean up the transcript afterward.

The combination of call handling and live interpretation also says something about where enterprise demand is heading. Organizations do not just want AI to summarize activity; they want it to help manage access, routing, and participation in real time. In practical terms, that makes Teams Copilot call delegation and interpretation more than a feature bundle. It is a signal that Microsoft is trying to make Copilot useful at the point where work actually happens: when someone is deciding whether to answer, how to route a call, or how to keep a multilingual discussion moving.

For readers evaluating these tools, the important question is not whether the features sound impressive, but whether they can stay helpful without creating control or trust problems. A live assistant that screens calls or translates speaking turns needs to be understandable to the organization using it, with clear rules around who can delegate, how meetings are configured, and what participants can expect from the experience.

How readers should interpret it now

Teams users should assume rollout details will matter as much as the feature announcement itself. Call delegation, Bookings integration, and interpreter settings are the kinds of controls that determine how broadly these capabilities are actually used inside an organization. Before treating the update as universally available, teams should check how their admins plan to configure access and what policies apply to delegated calls and multilingual meetings.

For interview prep, study workflows, and everyday collaboration, the key signal is that mainstream copilots are moving toward live, spoken interaction rather than staying limited to text generation. That matters because it widens the range of situations where AI can help: screening calls, supporting scheduled conversations, and smoothing back-and-forth in meetings where multiple languages are involved. The practical value is less about novelty and more about reducing friction in work that used to require constant human coordination.

This is a meaningful product-direction update because it changes how AI can participate in work conversations, not just document them. If Microsoft can make these features reliable and governable, Teams Copilot call delegation and interpretation could become part of how enterprises think about communication workflows, not just a convenience layer on top of them.

What This Means In Practice

  • Check whether your organization has enabled call delegation in Teams and how that setting is governed.
  • Review whether Bookings workflows are connected to the new call-handling experience before planning any rollout.
  • Confirm how interpreter settings are configured for multilingual meetings, including who can use them.
  • Test the feature in a controlled internal scenario before relying on it for customer-facing or interview workflows.
  • Update meeting and call etiquette so participants know when Copilot may be answering, routing, or interpreting live conversations.
  • Track whether the feature changes how your team handles scheduling, screening, and cross-language collaboration day to day

    Sources