iOS 26 Call Screening: What It Does to Outbound Calls, and What Your Dialer Can Do About It

Since September 2025, an iPhone can answer a call before its owner does. The feature is called Call Screening, the setting is Ask Reason for Calling, and it changes what "answered" means for every outbound campaign that dials consumers.

This post covers what the feature does, what it does to a dialer, what we see in our own call logs, and what a dialer can do about it.

What iOS 26 call screening does

When a call arrives from a number that is not in the owner's contacts, the iPhone answers it silently and plays a prompt to the caller:

"Hi, if you record your name and reason for calling, I'll see if this person is available."

Whatever the caller says is transcribed and shown on the owner's screen, where they can pick up, decline, or ignore it. The owner's phone rings only after the caller has spoken. If the caller says nothing, the call never reaches a person.

Google has done something similar on Pixel phones for years with Call Screen ("Hi, I'm Call Assist by Google, recording this call..."), and handset and carrier call blockers ask the same kind of question ("Call blocker. Please say your name after the tone."). What is new with iOS 26 is scale: iPhones are more than half of US smartphones, and the setting is one tap away for everyone who finds unknown calls annoying.

What it does to an outbound dialer

A predictive dialer treats the moment of answer as the start of detection. For about two seconds it plays silence to the callee while its answering machine detection listens, then it either connects an agent or hangs up.

With call screening in the way, that sequence breaks in two places:

1. The screener hears silence. The dialer says nothing during the detection window, so there is nothing to transcribe. The owner's phone never rings.
2. The detector hears a sentence. "Hi, if you record your name and reason for calling..." is continuous speech, which timing-based AMD reads as a machine greeting. The call is dropped as voicemail.

Either way the person behind the screen, who was about to see a transcript and decide, is lost. The disposition says "answering machine". The lead gets recycled, and the next attempt meets the same screen.

What we see in the logs

VM Hunter transcribes the first two seconds of every call it analyses, so screening prompts show up in the data as what they are.

On one customer's outbound traffic in September 2026, about 19,000 answered calls over four days:

• 15.1% of answered calls were a call-screening prompt. The large majority were the iOS 26 wording.
• 4.5% were live people.

That is more than three times as many screened calls as live answers. Every one of those screened calls had a person on the other end who was, at that moment, deciding whether to take the call.

The share varies by list. Consumer lists in the US run high; business lists run low. But it is no longer a rounding error on any consumer campaign, and it is growing as more owners find the setting.

Why timing-based AMD cannot handle it

Classic AMD, including Asterisk's app_amd that VICIdial uses by default, decides from the shape of the audio: how long the initial silence was, how long the first burst of speech ran, how many words it counted. A screening prompt is a sentence of fluent speech with no pause, so it scores as a long greeting. There is no setting in amd.conf that makes a tone-and-silence detector recognise a sentence.

Recognising it needs the words. "Record your name and reason for calling" means one thing. "You've reached the voicemail of" means another. "Hello?" followed by silence means a third.

How VM Hunter detects it

VM Hunter sends the first two seconds of audio to a speech engine and matches the transcript against rules. Call-screening phrases are checked before anything else, so a match cannot be mistaken for voicemail or a person. The call comes back with:

AMDCAUSE = CALLGUARD_PHRASE:<the phrase that matched>

The list covers the iOS 26 prompt in the forms the speech engine produces (including the shortened ones that appear when the prompt is cut at two seconds), Google Call Screen and Call Assist, AT&T and VTech call blockers, and the generic "calls to this number are being screened" wording. It is updated from real transcripts as new prompts appear.

Every screened call is logged with its transcript and audio, filterable by cause, so you can see your own share rather than take ours.

What a dialer should do with a screened call

Treat it as a person who is listening, because that is what it is.

1. Say who is calling. The moment the screening prompt is detected, play a short recorded intro: your company name and the reason for the call, in one sentence. The screener transcribes it and the owner sees it.
2. Then connect an agent, exactly as if a person had answered. If the owner picks up, the agent is there. If they decline, the call ends like any other no-answer.
3. Give it its own disposition. A screened call is not a voicemail. Counting it separately tells you how much of your list is behind screening, and stops the lead being recycled as "machine".

The VM Hunter clients for Asterisk/VICIdial and FreeSWITCH include this branch: they check AMDCAUSE for the CALLGUARD prefix, play an intro file, and transfer to the agent queue. It is a few dialplan lines.

Two cautions:

• Pre-recorded messages are regulated. In the US the TCPA and state rules apply to pre-recorded voice; other countries have their own. Check the rules for your campaigns before enabling an intro, and keep it to what the screener needs: who you are and why you are calling.
• The intro has to be true. The owner reads it before deciding. A vague or misleading intro gets declined, and gets your number reported.

What to measure

Three numbers from your call logs tell you whether this matters for your campaigns:

• Screening share: screened calls as a percentage of answered calls. Above a few percent, it is worth routing them.
• Pickup rate after intro: of screened calls where you played an intro, how many the owner picked up. This is the number that justifies the dialplan work.
• Recycle waste: how many leads were marked "answering machine" by your old AMD that were in fact screens. Those leads were never voicemail; they were people who were never told who was calling.

If your dialer does not label screened calls, you cannot measure any of this. That, more than the routing, is the reason to detect them.

Summary

iOS 26 call screening answers a growing share of outbound calls with a prompt that a person then reads. Timing-based AMD treats it as voicemail and drops the call. Detecting the prompt from its words, in the first two seconds, turns those calls into a routing choice: say who you are, then connect an agent. On the traffic we see, that is a bigger pool of reachable people than the live answers.

VM Hunter labels screened calls on every integration. The call screening page has the detail, and the VICIdial integration includes the routing branch.