Short answer
Enabling the WhatsApp Business Calling API requires a Cloud API phone number with a daily messaging limit of at least 2,000 unique recipients, active messaging permissions, and explicit call feature activation. While customers can initiate inbound calls freely, business‑initiated outbound calls strictly require prior user call permission and support either Graph API WebRTC webhooks or TLS‑secured SIP integration.
Mandatory Prerequisites Before Enabling Calling
Meta gates access to the WhatsApp Business Calling API behind strict account readiness checks. Before configuring webhooks or voice agents, verify five prerequisites:
- Cloud API Number – Your business phone number must operate on the WhatsApp Cloud API. Numbers restricted to the free WhatsApp Business mobile app are ineligible.
- Minimum 2,000 Daily Messaging Limit – Your business phone number must hold a daily messaging tier of at least 2,000 unique recipients per 24 hours. New unverified accounts starting at 250 must first scale their messaging limit (public test numbers and sandbox accounts waive this threshold for testing).
- App Subscription & Permissions – Your Meta app must be in Live mode with
whatsapp_business_messagingpermissions and active webhook subscriptions for the target WhatsApp Business Account (WABA). - Billing Method Attached – A valid payment method or credit line must be configured on the Meta Business Portfolio to cover outbound per‑minute calling charges.
- Explicit Feature Activation – Calling is disabled by default on Cloud API numbers and must be switched on via WhatsApp Manager (Phone Number Settings → Calls) or the
/settingsGraph API endpoint.
User‑Initiated vs Business‑Initiated Call Permission Rules
Meta separates inbound customer calls from outbound business calls to protect users from voice spam:
| Call Direction | User Consent Requirement | Rate & Retry Guardrails | Meta Billing Model |
|---|---|---|---|
| User‑Initiated (Inbound) | None; customers tap the call icon or call link directly | Controlled via business call hours & call icon visibility | Free for both the business and the customer |
| Business‑Initiated (Outbound) | Mandatory explicit user approval (7‑day or permanent) | Max 1 permission request per 24 h & 2 per 7 days; revoked after 4 unanswered calls | Charged per minute in 6‑second pulses by destination country |
How Business‑Initiated Call Permissions Work
- Requesting Consent – Send an interactive call permission request inside an open 24‑hour customer‑service window, or via an approved Utility or Marketing template outside the 24‑hour window.
- Permission Duration – Users can grant temporary permission (valid for 7 days / 168 hours) or permanent permission, which they can revoke anytime in chat settings.
- Automatic Revocation – If a business places 4 consecutive unanswered calls to a user, Meta automatically revokes the call permission, requiring fresh user consent.
Choosing Your Signaling Architecture: Graph API vs SIP Integration
Meta provides the raw VoIP media stream, leaving call routing, IVR, and AI voice orchestration to your backend or automation platform. Teams can connect via two primary signaling paths:
1. Graph API & WebRTC Webhooks
- How It Works – Subscribe your app to the
callswebhook field alongsidemessages. Meta sends call lifecycle events (connect, terminate) and SDP offers over webhooks so your WebRTC media server can bridge audio. - Best For – Cloud‑native voice AI platforms and browser‑based agent desks that do not rely on legacy telecom hardware.
2. Third‑Party SIP Trunking (wa.meta.vc)
- How It Works – Configure your standards‑compliant SIP server directly on the business phone number. Meta routes inbound calls via SIP INVITE over mandatory TLS transport and accepts outbound SIP INVITE requests to
wa.meta.vcusing RFC 3261 digest authentication. - Important Trade‑Off – When SIP signaling is enabled on a number, calling‑related Graph API endpoints are disabled, and call‑lifecycle webhooks must be explicitly opted into if your CRM still requires webhook event logging.
- Best For – Enterprises and contact centers connecting WhatsApp voice directly into an existing SIP‑based PBX or telephony stack.
Step‑by‑Step Production Configuration Checklist
Before opening WhatsApp voice lines to live traffic, configure four operational controls in Phone Number Call Settings:
- Business Call Hours & Holiday Overrides – Define weekly operating schedules in your local time zone (e.g.,
Asia/Kolkata) plus holiday exceptions so inbound callers outside shift hours are routed to voicemail or automated WhatsApp chat instead of ringing unanswered. - Call Button Visibility – Choose whether to display the profile call button globally or restrict calling to specific deep links and in‑thread prompts during initial rollout.
- Callback Request Prompts – Enable callback requests so users who reach your line after hours or during peak queues can grant one‑tap permission for an automated or agent callback.
- Mid‑Call Messaging Sync – Because WhatsApp voice calls share the exact same thread as chat, configure your AI agent or human desk to send payment links, PDF brochures, or order summaries via the Messages API while the call is still active.
Frequently Asked Questions
What messaging tier is required for the WhatsApp Business Calling API?
Meta requires your Cloud API business phone number to have a daily messaging limit of at least 2,000 unique recipients per 24 hours before enabling production calling features.
Can a business call any customer on WhatsApp without permission?
No. Business‑initiated outbound calls strictly require the customer to accept a call permission request first. Customers can grant consent for 7 days or permanently, and permission is automatically revoked after 4 consecutive unanswered calls.
Does Meta charge for inbound WhatsApp Business calls?
No. User‑initiated inbound calls are free of Meta calling fees. Meta charges per minute (billed in 6‑second increments) only for business‑initiated outbound calls, plus standard template fees when sending call permission requests.
Can I connect the WhatsApp Business Calling API to my existing SIP server?
Yes. Meta supports standards‑compliant third‑party SIP servers using mandatory TLS transport and digest authentication via
wa.meta.vc, allowing enterprises to route WhatsApp calls into existing contact‑center infrastructure.
Can you send WhatsApp messages while on a WhatsApp Business call?
Yes. Voice calls and chat messages share a single conversation thread, allowing businesses or AI agents to send links, images, and documents through the Messages API during an active call.
Go deeper
- Compare unified voice and chat architectures in One AI Agent for WhatsApp and Phone Calls: How Unified Business Automation Works.
- Review daily messaging tier scaling criteria in Managing WhatsApp API Messaging Tiers in 2026: Portfolio Limits, Scaling Rules, and Quality Score Recovery.
- Design modular voice call flows in Designing Graph-Based AI Voice Conversations: How to Split Complex Inbound Calls Into Single‑Job Nodes.
Call to Action
Ready to combine WhatsApp Business Calling, AI voice agents, and automated chat workflows on a single verified business number? Get started with NimbleBiz AI today to launch unified customer conversations.