WhatsApp Guest Calls: WhatsApp Wants to Become a Service That Doesn't Need WhatsApp

WABetaInfo reports that WhatsApp is testing Guest Calls, a feature that would let people join WhatsApp voice and video calls without a WhatsApp account or installed app. The guest only needs a browser and a link that the host shares. This is not a beta release; the feature is still in development, has not reached beta testers, and has no announced launch date. For businesses that already treat WhatsApp as a primary customer channel, the shift is clear: WhatsApp is gradually ceasing to require the WhatsApp app itself for communication through WhatsApp.

WhatsApp calls are reaching beyond the installed app: a browser link is now enough for guests. WABetaInfo's discovery describes Guest Calls as a way for unregistered users to join voice and video calls by opening a Call Link in a browser.

The host still needs a WhatsApp account, but the guest does not.

Before Guest Calls, both sides needed the WhatsApp app installed and set up. A call to someone without the app was impossible. Guest Calls change that for the first time by letting the guest join through a browser link.

The shift is subtle but important for automation. The account has always been the gate: no account, no call. Guest Calls remove that gate for the receiving side, while the host still keeps one.

The business implication is reach. A clinic, a real-estate agent, or a tutoring service can invite a customer to a video call without asking them to install an app, create an account, or hand over a phone number to WhatsApp. That removes the drop-off point where a non-user opens a different meeting tool instead. It also keeps the interaction inside the same channel that already handles reminders, bookings, and support messages.

Call Links are not new. WhatsApp already lets users create links from the Calls tab, choose voice or video, and optionally require approval before someone joins. WhatsApp's FAQ states that these links expire after 30 days of inactivity. Guest Calls appear to reuse that existing infrastructure and simply remove the account requirement on the guest side.

Guest Calls run on a link-and-browser workflow. The host creates a Call Link from the Calls tab, chooses voice or video, and sends the link to the guest. The guest opens the link in a browser.

Before the guest joins, the host must manually approve the request. Approval is mandatory for unregistered guests; for registered WhatsApp users the waiting room is optional.

Once admitted, the guest participates in the call through the browser. The host keeps control: they can reject a request, remove a participant, or end the call. If a guest is removed, that same guest cannot rejoin the same call. This design mirrors the approval model used in meeting-link tools and in the event-reaction model of WhatsApp API integrations, where an event triggers a decision before the action proceeds.

End-to-end encryption is preserved through a unique browser-session identifier that generates a cryptographic key. WhatsApp Web creates this key for the guest session, so the call content remains encrypted even though the guest has no account. The technical details of how the key is rotated or stored have not been published, and the reported explanation stops at the browser-session identifier.

Guest Chats already showed that WhatsApp wanted to let non-users communicate through a link. Guest Calls extend the same idea to voice and video.

Discovered in August 2025 and rolling out to beta users in March 2026, those chats are text-only, expire after 10 days of inactivity, and explicitly exclude groups, media, stickers, and voice or video calls.

Guest Calls extend the same link idea from text to real-time audio and video. The table below compares the two.

The progression is deliberate: first text, then voice and video. The common thread is the link-based entry point: the account is no longer the gate. For teams building WhatsApp API integration workflows, this is a clear sign that the entry point is becoming link-based.

On July 28, 2026, Meta announced that WhatsApp Web now supports audio and video calls, screen sharing, reactions, and call history, with no app download required.

The announcement turned a browser tab into a real calling endpoint for registered users.

Guest Calls build on that same browser infrastructure. If a registered user can already place and receive calls through WhatsApp Web, opening those calls to unregistered guests is a smaller architectural leap than it would have been a year ago. The browser has moved from preview to peer: it is now a real endpoint and a potential programmatic endpoint for new integrations.

Screen sharing, reactions, and call history are part of the official WhatsApp Web calling package. It is not yet clear which of these will be available to guests, but the browser platform can now carry them.

Until now, WhatsApp competed with Telegram, Signal, and iMessage as an account-based messenger. Guest Calls change the comparison. The guest workflow looks like Zoom, Google Meet, or Microsoft Teams.

A host creates a link, shares it, admits participants, and controls the room.

You might still file Guest Calls under the same account-based messenger competition. That framing misses the actual failure mode. A customer without WhatsApp will not compare messengers. They will choose the easiest way to join the call: install an app or click a link. The business that keeps the old comparison will keep forcing customers to install an app and will lose the call to a meeting-link tool.

This matters because the original pain point is real. In practice, teams that run WhatsApp-based support workflows see the highest drop-off when the customer has to leave the channel to join a call. Businesses in healthcare, beauty, real estate, EdTech, and e-commerce already use WhatsApp for reminders and support. When they escalate to a call, they often have to switch to a separate meeting tool because the customer does not have WhatsApp installed or does not want to install it.

Industry benchmarks show why keeping the interaction inside WhatsApp matters. A Jeddah salon reduced no-shows by 70% with WhatsApp booking reminders. A wellness clinic cut no-shows by 60% and added roughly ₹40,000 in monthly revenue. In customer support, SICAR Solutions reported 20% faster case resolution, 35% higher first-contact resolution, and 20% higher customer satisfaction scores after integrating WhatsApp Business Calling into the same agent workflow. Link-based calling would let those same agents send a call link to a guest who has never installed WhatsApp, without switching tools.

The strategic shift is that WhatsApp is gradually ceasing to require the WhatsApp app itself for communication through WhatsApp. The account is still needed to host, but the guest side is becoming account-optional. That moves the product closer to meeting-link platforms than to traditional messengers.

As WhatsApp moves closer to meeting-link competitors, the security model shifts to the host. Manual approval is the main security gate. Because an unregistered guest cannot be verified by WhatsApp's registration system, the host becomes the identity check.

Manual host approval is mandatory before a guest joins, which makes the host the identity check for unregistered users. Link abuse is a real risk; scammers already use fake call invitations to trick users, so the waiting room is a necessary control. The same gating principle applies to account safety in WhatsApp automation: verify before you let traffic through.

What is missing is availability. WABetaInfo reports that Guest Calls are in development, not available to beta testers, and have no release date. The expiry rules, media permissions, and group-call limits for guests have not been published. Businesses should treat the feature as a signal to track; depending on it soon would be premature.

The programmable surface matters more than the release date. Once the security and availability gaps are clear, SaaS founders, product managers, and integrators should monitor three things while Guest Calls remain in development.

First, whether Guest Calls roll out to WhatsApp Business accounts or only to consumer accounts. Second, whether the browser API surface that powers Guest Calls becomes available to third-party developers. Third, how quickly the broader ecosystem can expose the same link-based workflow without breaking the account-host requirement.

For teams already running WhatsApp automation, the practical question is reach as well as calls. We have seen integrators route entire customer journeys through WhatsApp--reminders, bookings, confirmations, and support--because the channel has higher open rates than email and lower friction than phone calls. If WhatsApp becomes a link-based communication platform, every automated thread becomes a possible entry point to a voice or video call. Teams that rely on gateways exposing the full WhatsApp feature surface should watch whether native link-based calling becomes another programmable endpoint.

We won't cover WebRTC integration details or a step-by-step setup guide for an unreleased feature here. Those belong in a separate technical guide once the feature ships and its API surface is documented.

Whapi.Cloud provides a REST API for WhatsApp automation with support for messages, groups, channels, and status updates. If you want to test the current feature surface before Guest Calls arrive, you can create a free sandbox account in minutes.