Quick Summary: The Indian Express reported on October 21 that WhatsApp is developing an Android call-screening feature that could let users review why an unknown caller is calling before deciding whether to answer. The feature was found in beta code and was not yet available for beta testing.
How the three reported screening options would work
The report describes three possible settings: allow all calls, silence calls from unknown numbers, or let WhatsApp ask an unknown caller for a reason and show a transcript. The transcript is reportedly intended to be generated on the device using language packs.
WhatsApp already provides Silence Unknown Callers, which reduces ringing from unsaved numbers. The reported work would add a more selective option: instead of only silencing a call, users could see context before deciding whether it deserves attention.
On-device transcripts and privacy questions
Why this is still a feature in development
The next meaningful update would be a WhatsApp release note or a beta release that confirms the feature, supported languages, whether transcription is entirely on-device, and how the feature interacts with end-to-end encrypted calls.
Guest-call invitations and participant controls
Call screening for unknown numbers addresses a common problem: users cannot always distinguish a legitimate providey, school, medical or business call from spam. A screening feature may ask an unknown caller to identify themselves or state a reason before the phone rings normally. That could help users decide whether to answer, but the exact prompts, caller experience and handling of missed calls will determine how useful it is.
The feature would need to avoid blocking important calls simply because the caller is unfamiliar. A hospital, providey driver or small business may use a number that has never contacted the recipient before. Clear caller prompts, an option to accept the call quickly and reliable missed-call information would be important safeguards. A screening system should reduce interruptions without turning unfamiliar contacts into silent failures.
Privacy also matters because screening introduces an additional step in the call flow. Users need to know what information the caller is asked to provide, whether any audio or transcript is processed, and whether screening data is stored. Until WhatsApp publishes the implementation details, the responsible description is that the company is developing a feature, not that it has launched a working spam-filtering service.
The key question for WhatsApp is whether screening can identify the caller’s intent without collecting more information than necessary. A short caller-provided reason may help a recipient decide whether to answer, but it can also be spoofed or used to send misleading content. The app should give recipients a clear choice to accept, reject or report a call, and should not imply that a caller’s explanation has been independently verified. Until the company publishes implementation details, those are design questions rather than confirmed features.
For users, the safest approach is to wait for WhatsApp’s official release notes and test the feature with non-urgent calls first if it becomes available. They should verify whether unknown callers are told that screening is active, whether missed calls are recorded correctly, and how the option interacts with blocked contacts. A new screening layer should be easy to disable if it delays important calls or behaves unpredictably. These details will determine whether it is a useful convenience or simply another step in answering the phone.
Call screening can also create accessibility and reliability issues if the caller is asked to speak before the recipient knows who is calling. People with speech impairments, callers in noisy environments or those who cannot safely speak may struggle with such a flow. WhatsApp should explain whether a text-based alternative exists and how emergency or business calls are handled. These are not confirmed implementation details; they are necessary questions for evaluating the feature if it launches.
A transcript can help a recipient decide whether to answer, but it introduces a new failure mode: a caller’s spoken reason may be misrecognised or deliberately misleading. The interface should make clear that the text is caller-provided context, not a verified identity or a guarantee that the call is safe. It should also let users report abuse and correct a false classification without forcing them to expose more personal data. These are important design tests if the feature reaches a public release.