Microsoft recently rolled out Intelligent Call Delegation for Teams Phone, an AI-powered voice agent that can answer your calls, figure out why someone’s calling, and decide what happens next: screen it, escalate it, or schedule a follow-up. Microsoft’s own support article covers the full rundown of how it works and how to configure it, and it’s worth a read if you’re on Teams Phone and haven’t seen it yet (https://support.microsoft.com/en-us/teams/copilot/use-copilot-call-delegation-in-microsoft-teams).
The short version, straight from Microsoft’s documentation, is that when it’s turned on, Intelligent Call Delegation can:
- Screen calls before they reach you, helping block spam and fraudulent callers.
- Collect caller context, meaning the reason for the call, so you can decide how to respond.
- Route urgent calls to you directly, or schedule callbacks and meetings when you’re unavailable.
- Detect when you’re out of office and automatically schedule time after you’re back.
- Notify you transparently every time it takes an action, with settings you can adjust anytime.
A few things worth calling out before you flip this feature on. It’s currently rolling out through the Microsoft Copilot Frontier program, which means you need a Microsoft Copilot license during this early access period. It’s also only supported on Windows desktop, Mac desktop, and web, not on iOS or Android. In addition, it also only works when your Teams app language is set to English for now.
There are some service limits too. Calls top out at 4 minutes, and there’s a 15,000 minute monthly cap per tenant, after which calls fall back to your normal routing or voicemail until utilization resets the following month. It’s worth knowing about these limits before you’re relying on it for something important.
Why I actually use it, and where I draw the line
I take a lot of calls in my role from both clients and vendors. I turned this on the day it showed up in my Teams settings. But I only screen external calls. I leave internal calls alone entirely.
Here’s why: internally, if someone’s going to call me, they can see my status, and may be pinging me on Teams chat as well. Having an AI voice answer a colleague who already knows I’m about to pick up can add an unnecessary layer. For how my team communicates, screening internal calls would add friction with no benefit.
How it handles external calls
External calls are a different story, and this is where the feature earns its keep.
Within external calls, there’s also a choice in how it’s applied. You can let it automatically screen every external call the moment it comes in, or you can set it to ring you first and only screen the call if you choose to. I went with the second option. When an external call comes in, it rings like normal and I can see who it is. If I recognize the number, I can pick up. If I don’t recognize it, or I’m in the middle of something, there’s a button to send the call to screening instead. That way, this service is not answering every single client call before I get a chance to see who’s on the line. It only kicks in when I actually want it to.
Spam calls
Utilizing this service with spam calls is the obvious win. My work number ends up on plenty of vendor call lists just from creating tickets and working with outside partners. Teams already filters some spam, but plenty gets through. Having something screen those calls before they hit my phone means I’m not interrupted by calls I never wanted in the first place.
Prioritizing calls
The bigger win is prioritization. My week is usually a mix of multiple client projects and open tickets running in parallel. Being able to see the call, decide in the moment whether I recognize it or want to screen it, and then get the context for why someone’s calling before I commit to picking up changes how I work. It’s not just about filtering noise; it allows me to be more responsive to the calls that matter. If a client says it’s urgent, I know immediately and can reprioritize instead of finding out after the fact from a voicemail.
Phones have had spam and call screening for a while now, iPhone and Android both do it, so it’s genuinely nice to see something equivalent land in Teams. Out of office scheduling and post call summaries push it further than a basic screening service. It’s not just blocking calls. It’s doing some of the follow-up work for you.
If you’re on Teams Phone and have Copilot access through Frontier, this call screening feature is worth turning on. Think about whether you want it screening internal calls too, and whether you want every external call screened automatically, or only when you choose to send the call to the screening service.
This publication contains general information only and Sikich is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or any other professional advice or services. This publication is not a substitute for such professional advice or services, nor should you use it as a basis for any decision, action or omission that may affect you or your business. Before making any decision, taking any action or omitting an action that may affect you or your business, you should consult a qualified professional advisor. In addition, this publication may contain certain content generated by an artificial intelligence (AI) language model. You acknowledge that Sikich shall not be responsible for any loss sustained by you or any person who relies on this publication.