WhatsApp Business Calling
WhatsApp Business Calling: Voice Setup and Eligibility
Voice support needs an eligible WhatsApp account and an agent endpoint that can actually receive a call. Separate a customer-initiated call from a business-initiated call, and plan staffing, unanswered calls and messaging follow-up for each.
Confirm calling support for the number, account, API version, provider, country and plan before designing the integration. The workflow is illustrative; no fixed capacity, verification badge, trial entitlement, calling tariff or successful connection is established.
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Illustrative workflow
Check account support
Obtain current calling eligibility, permissions and settings for the actual number and market.
Handle the calling event
Agree the provider signaling/event contract, verification and failure responses.
Route to a digital endpoint
Confirm a supported VoIP/SIP/WebRTC integration and a staffed agent destination.
Resolve or hand off
Track answer/failure/missed states. Check permissions, window eligibility and pricing separately before a follow-up.
Choose voice for a question that needs a person
Illustrative uses include explaining an order exception, coordinating an appointment change or discussing a sales request. A call does not establish fraud prevention, regulatory suitability, a verification badge or better answer/conversion rates.
Inbound and outbound have different prerequisites
A customer-initiated call and a business-initiated call need their own availability, permissions and charge checks. Confirm whether the actual call or missed-call event creates an eligible messaging window. No universal permission-request quota or permanent free-call price is supplied.
On a narrow screen, scroll the table horizontally to read every column.
| Path | Confirm before use | Price here |
|---|---|---|
| Inbound call | Number/account/market support, receiving endpoint and routing | Unavailable |
| Outbound call | Permitted initiation and applicable customer permission rules | Unavailable |
| Messaging follow-up | Actual window trigger, category and effective tariff | Unavailable |
Separate event signaling from voice media
Agree the actual provider call-event/session contract and how the enabled integration negotiates media. Route an eligible call to the chosen agent endpoint and handle unanswered, failed and ended states. A webhook acknowledgement alone is not proof of an answered call or a working audio path.
VoIP endpoints and a reviewable setup
Preserve the voice distinction: the workflow discussed here is VoIP-to-VoIP using a supported digital endpoint, such as a softphone or SIP/WebRTC integration. Do not assume native forwarding to an ordinary mobile or landline/PSTN number. Confirm any contact-center bridge and provider support separately.
Account and event access
Obtain current settings, API/version support, credentials, event schemas and webhook verification instructions; no fixed messaging tier is asserted.
Agent routing
Confirm endpoint support, media negotiation, network/firewall requirements, staffing and routing/fallback. Signaling support alone does not provide an internal contact center.
Security and records
Review actual encryption scope, endpoint controls, access, recording permission, logs, retention and providers. No end-to-end encryption or banking/healthcare certification is inferred here.
Define a bounded support task
Hypothetical examples: clarify a property enquiry; coordinate an appointment change; discuss an order exception; route a delivery-access question to a staffed operations team. Do not use this illustration as emergency/clinical advice, payment verification or proof of live delivery tracking.
Measure answered calls and resolved work
Define the cohort and period, then record attempted, answered, missed and failed calls separately. Specify the denominator for missed-call rate and the method for linking a resolved issue or verified order. Duration alone does not prove resolution quality. No conversion lift or savings result is supplied.
Troubleshoot the actual integration contract
Check credentials and their actual lifetime/permissions, webhook verification, subscribed event types, endpoint reachability, negotiated media and routing. Do not assume a “permanent” token cannot expire or that a specific webhook path is universal. Obtain the account capacity, provider quotas and failure codes; no 1,000-call limit or automatic increase is established.
Messaging and setup conditions
A customer message opens or resets the 24-hour reply window. Outside it, an approved template is needed. Permission to use a message format does not determine its price; confirm the effective category, allowance and account conditions separately.
Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
Onboarding, verification, template review and integration timing depend on the account, provider, workflow and outstanding approvals. Confirm the scope and schedule with the team; no instant approval, fixed waiting period or go-live deadline is promised.
Questions about WhatsApp Business Calling
Can I forward directly to a mobile or landline?
The scoped workflow uses a supported digital VoIP endpoint. Do not assume native PSTN forwarding. Confirm any contact-center bridge and its permitted provider contract separately.
How much do calling and follow-up messages cost?
Current numerical charges are unavailable here. Confirm direction, market, effective tariff, currency and units. Keep platform/infrastructure costs and follow-up message charges separate.
Does a missed call make later messages free?
Do not assume that. Confirm the current window trigger and eligibility for the actual event and account, then apply effective pricing, category and permission conditions.
How many calls can the account handle?
Obtain the actual number/account/provider capacity, concurrency limits and escalation process. No universal 1,000-call allowance or infrastructure capacity is promised.
Is calling automatically included in a plan or trial?
Confirm current account/region eligibility, enabled integration and written commercial terms. This page does not activate a trial, provide a badge or connect a call.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support in your signed service agreement.
Discuss your WhatsApp Business Calling setup
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Send an enquiry