iOS 26 call screening and your outbound calls: detect it, then answer it
iPhone's Ask Reason for Calling, Google Call Screen and carrier call blockers now answer a meaningful share of outbound calls before a person does. VM Hunter recognises the screening prompt in the first two seconds, so your dialer can respond instead of hanging up.
Since iOS 26, an iPhone can answer a call from an unknown number itself. The caller hears "Hi, if you record your name and reason for calling, I'll see if this person is available", and the owner reads a transcript before deciding to pick up. Google has offered the same on Pixel phones for years, and handset and carrier call blockers ask similar questions.
For an outbound dialer this is a new kind of answer. It is not a person, so an agent should not be connected yet. It is not voicemail, so hanging up throws away someone who is sitting there deciding whether to take the call. And because the dialer plays silence while its AMD runs, the screener hears nothing and the call dies. On one customer's traffic, 15% of answered calls hit a screening prompt, more than three times the number of live answers.
What the screening prompts sound like
| Screener | What the caller hears |
|---|---|
| iPhone, iOS 26 Ask Reason for Calling | "Hi, if you record your name and reason for calling, I'll see if this person is available." |
| Google Call Screen (Pixel) | "Hi, I'm Call Assist by Google, recording this call..." or "...the person you're calling is using a screening service from Google. Go ahead and say why you're calling." |
| Handset and carrier blockers | "Call blocker. Please say your name after the tone." / "Calls to this number are being screened." |
Timing-based AMD hears a sentence of continuous speech and calls it a machine. VM Hunter matches the wording and labels the call CALLGUARD_PHRASE:<phrase>, with the phrase that matched.
What your dialer should do with a screened call
- Say who is calling. Play a short recorded intro the moment the screening prompt is detected: your company name and the reason for the call, in one sentence. The screener transcribes it and the owner sees it.
- Then connect an agent, as if a person had answered. If the owner picks up, the agent is there; if not, the call ends like any other no-answer.
- Give it a disposition. A screened call is not a voicemail. Keeping it separate in your reports tells you how much of your list is behind screening.
The Asterisk/VICIdial and FreeSWITCH clients include that branch: they check AMDCAUSE for the CALLGUARD prefix, play an intro and transfer to the agent queue. Pre-recorded messages are regulated in many places; check the rules for your campaigns before enabling it.
How VM Hunter detects it
The engine transcribes the first two seconds after answer. A list of screening phrases, built from real call transcripts and updated as new prompts appear, is checked before any other rule. A match wins over everything else, so a screening prompt is never mistaken for a voicemail greeting or a person.
Every screened call is logged with its transcript and audio in your call logs, filterable by cause, so you can see the share of your list that is behind screening and listen to any verdict you doubt.
Questions
What is iOS 26 call screening?
How does call screening affect outbound campaigns?
Can VM Hunter detect call screening?
What should my dialer do with a screened call?
Is a screened call billed?
See how much of your list is behind screening
Run one campaign through VM Hunter and filter your call logs by cause. The free plan covers 5,000 calls.