Skip to main content
Back to blog

WhatsApp Business Calling API Is Now Generally Available — What It Changes for Business Voice

Meta's WhatsApp Business Calling API reached general availability in July 2025, bringing user-initiated and business-initiated VoIP calls into the WhatsApp Business Platform. This analysis covers what shipped, why it retires the 'WhatsApp is text-only' objection on telephony shortlists, and how to choose between WhatsApp calling and PSTN voice.

Orbit Editorial Team

Meta made the WhatsApp Business Calling API generally available in July 2025, extending the WhatsApp Business Platform from messaging into voice. The API adds two call paths to the same Cloud API a business already uses for WhatsApp messages: a customer can start a VoIP call to a business from the WhatsApp app, and a business can place a VoIP call to a customer after requesting permission in the chat. Both directions land in a business system rather than a consumer phone — with webhooks, call-state events, and the same programmatic access model as WhatsApp messaging.

This is the industry's second channel taking that step. Apple's RCS rollout moved business messaging into the carrier SMS inbox; WhatsApp calling moves the telephone call itself into the messaging app where roughly 2 billion people already answer businesses. The questions worth settling are narrower than the announcement: what exactly shipped, which buying objections it removes, and when the answer is PSTN voice anyway.

What Meta shipped

Four components define the GA surface:

  • User-initiated calling. A customer opens a chat with a business and taps the call icon; the business answers in its own system — an operator console, a contact center, or an AI voice agent — not on a personal handset. User-initiated calling is available wherever the Cloud API operates.
  • Business-initiated calling. The business requests calling permission inside the existing WhatsApp conversation; once the customer grants it, the business can place the outbound VoIP call on the same thread. Production accounts carry per-user-per-day limits on business-initiated calls, and the capability excludes a short list of country codes documented in Meta's developer docs — a national dial-tone replacement it is not.
  • Standard WebRTC media. The default transport is the same WebRTC media stack browser calling uses (ICE, DTLS, SRTP, and the Opus codec), with signaling over the Cloud API's Graph endpoints and calls webhooks. Meta also documents SIP interworking with G.711 codecs, which matters for contact-center and PBX estates that terminate SIP trunks.
  • Business call controls. Inbound call restrictions, defined calling hours, and callback requests are part of the phone-number settings a business owns — the controls a compliance-conscious operation sets for its own account, decided per tenant rather than globally.

Business-initiated calling requires the business number to live on the Cloud API rather than the consumer-style WhatsApp Business app, and Meta gates it on the account's messaging tier — the same quality guardrails that govern template messaging.

Why it removes the 'WhatsApp is text-only' objection

Communications-platform shortlists have carried one stock objection for the last several years: WhatsApp handles the conversation, but the moment a customer wants to talk, the thread breaks into a phone call on a separate system. Meta's GA closes that objection at the channel level, and the comparison matrices buyers use are already reflecting it. Orbit's own comparison pages against Twilio and Infobip record WhatsApp Business calling as shipped parity for both; older UCaaS incumbents such as RingCentral and 8x8 do not expose the WhatsApp voice row from their telephony suite at all.

That single matrix row changes shortlist math. A business that previously scoped "cloud phone system, plus a WhatsApp messaging vendor, plus an integration that reconciles the two" can now evaluate one account where the customer-facing number carries chat and voice together and the agent-side experience is one console.

How Orbit exposes it

Orbit ships WhatsApp calling on the same operator softphone as every other channel: an agent answering a PSTN call, an AI voice agent call, or a WhatsApp call works in one interface, with one call log and one recording policy. A business turns the capability on per WhatsApp number in Settings → Channels — the toggle carries the same eligibility state Meta enforces (Cloud-API registration, account tier, and per-number permission), so enabling it is a tenant-owned, per-number decision with the registration status visible in place. Inbound WhatsApp calls arrive in the same queues and routing rules as telephony calls; outbound calls start from the conversation thread, where the customer granted permission.

Room to operate, cost, coverage, and the messaging relationship on that number are the business's own parameters — Orbit surfaces the eligibility and usage signals; the tenant sets the policy.

When calls belong on WhatsApp, and when on PSTN

The two paths are complementary, not substitutes:

  1. Reach and numbering. PSTN voice reaches any telephone number on earth. WhatsApp calling reaches the customer's WhatsApp identity — powerful inside markets where customers already message businesses there, irrelevant where they do not. Keep the public PSTN number; add WhatsApp calling where the customer base lives in the app.
  2. Initiation rules. Inbound PSTN calling needs no relationship. Business-initiated WhatsApp calling needs a granted per-user permission and stays within Meta's per-day limits — designed for "the delivery driver is outside" or "your bank needs to verify this conversation," not for cold outbound dialing.
  3. Context continuity. A WhatsApp call inherits the thread: the customer texts, the call happens, the transcript and the call record sit in one conversation — the deflection pattern contact centers pay integrations to fake on PSTN. Where the conversation starts in chat, letting it turn into a call in the same thread removes the context handoff.
  4. Compliance surface. Recordings, retention, and consent logic are tenant-owned policies the business carries across both paths; WhatsApp calling adds a second voice surface to the same governance, not an exemption from it.

A pragmatic 2026 posture: keep PSTN for first contact and universal reach, and let WhatsApp carry the calls that grow out of WhatsApp conversations — where the relationship, the transcript, and now the voice live in one place.

Where to read next

The buyer's-guide surfaces for this query cluster:

Frequently asked questions

What is the WhatsApp Business Calling API?

Meta's voice extension to the WhatsApp Business Platform: it lets a business place and receive VoIP calls with WhatsApp users over the same Cloud API it already uses for messages, with calls webhooks, WebRTC media, and business-owned call controls. It reached general availability in July 2025.

Can a business call a customer on WhatsApp?

Yes, with permission. The business requests calling access inside the existing WhatsApp conversation; once the customer grants it, the business can place the outbound call on the same thread, subject to Meta's per-user-per-day limits and a short list of excluded country codes.

Is WhatsApp calling a replacement for a phone system?

No. PSTN still covers universal first-contact reach; WhatsApp calling covers the voice continuation of conversations that already live in WhatsApp. The two run side by side on one account rather than one replacing the other.

How do I turn on WhatsApp calling on Orbit?

Per number, in Settings → Channels: the toggle shows the number's registration and eligibility state, and eligible numbers enable in place. Inbound WhatsApp calls then arrive in the same queues, softphone, and call log as every other channel.

Resources

Published 25 August 2026.

WhatsApp Business Calling API Is Now Generally Available — What It Changes for Business Voice — Orbit by Devotel