Gemini Integrates With WhatsApp Enabling Calls and Messages

Android Police's Parth reports that using the Gemini mobile app on Android lets him ask the assistant, via text or quick voice prompts, to send messages and initiate calls through WhatsApp (Android Police). Google's official support page documents that users can ask the Gemini mobile app to make calls and send messages with WhatsApp, and it notes the tip that including @WhatsApp in a prompt will tell Gemini to specifically use WhatsApp (Google Support). Google also states that Gemini cannot read or summarize a user's WhatsApp message history, and that it can read and reply to messages visible in notifications by using the Utilities app (Google Support).

Google's May 19 blog post lists new agentic and performance upgrades in the Gemini ecosystem, including Gemini 3.5 Flash, the Gemni Omni capability, and a new 24/7 agent called Gemini Spark (Google Blog). The support documentation adds product-level operational constraints: WhatsApp integration currently works on Android devices with the Gemini mobile app and is not supported in the Gemini web app or Google Messages, and users can disconnect WhatsApp through Gemini's Connected Apps settings (Google Support).

Editorial analysis: Public reporting frames this integration as part of a broader push to make assistant experiences more agentic and action-oriented, moving beyond passive Q&A into performing tasks inside third-party apps (Google Blog; Android Police). Industry coverage also flagged privacy tradeoffs: TechRadar reported that, starting July 7, 2025, Google rolled out behavior allowing Gemini to interact with some third-party apps on Android and that the change may apply even when certain Gemini activity settings are switched off (TechRadar). Cybernews likewise reported that the update led to concerns about default access and noted claims that some data could be retained for up to 72 hours and that human reviewers may process accessed data, citing communications or leaked messages it had seen (Cybernews).

For practitioners: monitor the support documentation and Connected Apps setting flows for changes to scope and permissions, and audit notification-mediated workflows if your app surface exposes actionable notifications. Also watch for further clarification from Google on data retention and human review practices, and for platform updates that change where integrations are permitted (Google Support; TechRadar; Cybernews).

Editorial analysis: Developers building Android apps should treat notification-based assistant actions and explicit assistant-to-app triggers like @WhatsApp as distinct integration surfaces, each with different privacy and UX considerations. Security and privacy teams should validate whether automated assistant interactions are enabled by default in target Android builds and update consent and disclosure language accordingly.