The official Calling API adds internet-based voice calls to WhatsApp customer conversations. Businesses can receive calls and, with the user’s calling permission, place them. For Indian teams, the buying decision is whether their number, provider, agents and CRM can support a controlled handoff from messages to a useful human conversation.

Updated 15 September 2026. Platform rules below were checked against Meta’s current documentation. A customer enquiry, form submission or message opt-in is not, by itself, WhatsApp calling permission.

What is the WhatsApp Business Calling API?

It is the voice-calling capability of the WhatsApp Business Platform Cloud API. VoIP means the audio travels over an internet connection. The customer uses WhatsApp; the business needs a calling integration or a provider interface for its agents.

This is different from an employee making a call in the WhatsApp Business app. It is also different from buying generic voice calling features: a voice SDK alone does not establish WhatsApp Calling API compatibility. If you are comparing app and platform options, start with WhatsApp for business.

Meta’s Calling API overview is the source for the architecture and eligibility rules. A provider supplies the agent experience around that API. Routing, CRM screens, reports and implementation support need separate verification.

Is WhatsApp calling available in India?

India is within Meta’s supported availability for user-initiated and business-initiated calling, subject to the business meeting the setup requirements. This is not simply a future beta announcement.

• User-initiated calls: available wherever Cloud API is available.
• Business-initiated calls: available wherever Cloud API is available except for business numbers from the United States, Canada, Egypt, Vietnam and Nigeria.
• Which country matters? Meta applies that outbound exclusion to the business phone number’s country code. The customer’s number can be from any country where Cloud API is available. Do not confuse this with pricing, which depends on the called number’s country code.

Check the current availability section for the actual business number before contracting. A company registered in India may use a number with a different country code.

Prerequisites: API access is not enough

If messaging onboarding is still incomplete, use the WhatsApp API setup requirements guide first, then validate the separate calling prerequisites below.

Meta currently lists these prerequisites in its getting-started guide:

• A business number in use with Cloud API, rather than assuming app calling equals API calling.
• A business daily messaging limit of at least 2,000 unique recipients. This is an eligibility threshold, not a requirement to send that many messages.
• Calling enabled in the business number’s settings.
• An app subscribed to the business account, with the required messaging permission and the calls webhook subscription, unless using Meta’s SIP calling path.

The API and audio connection are separate parts of the implementation. Graph API plus webhooks handles call signalling by default; WebRTC handles the live media connection. SIP, a signalling protocol used by phone systems, is another supported integration path that needs explicit configuration.

Ask the implementation owner to demonstrate microphone access, network compatibility, business hours, missed-call handling and audio in both directions. Successful WhatsApp API messaging does not prove any of those checks passed. Sandbox restrictions are relaxed, so a test-number demo is not production eligibility proof.

Outbound permission: check the actual state before dialling

Meta’s permission guide requires the user’s permission before a business initiates a call. Keep marketing consent and calling permission as separate records.

1. Explain the reason. Ask to discuss the customer’s specific enquiry or support case, not an unspecified sales pitch.
2. Use the official permission flow. Send a free-form permission request inside an open customer service window, or an appropriate approved permission-request template. Template messages remain subject to messaging policy and charges.
3. Read the permission result. Temporary permission lasts seven calendar days from approval. Permanent permission is also supported, but the user can revoke it at any time. Callback permission can be granted through an inbound call when the callback setting is enabled.
4. Recheck before placing the call. Consult the current permission state and whether the start-call action is allowed. Do not rely on a stale CRM checkbox.

Meta’s production rules limit permission requests to one in 24 hours and two within seven days per business-number/user pair. A connected call resets these request limits. Two consecutive unanswered calls prompt the user to reconsider permission; four revoke it automatically. These are protection limits, not a recommended contact cadence. Stop earlier when the customer declines or no longer needs help.

Do not reuse old tutorials that describe every permission as a 72-hour, one-call allowance. Do not treat an email click, checkout event, lead score or ordinary WhatsApp reply as approval to call.

How much does WhatsApp Business Calling API cost?

According to Meta’s calling pricing documentation, user-initiated calls are free at the Meta layer. Business-initiated calling charges depend on duration, the called number’s country code and the applicable monthly volume tier. Duration is counted in six-second pulses, with fractional pulses rounded up. A valid payment method is required for placing calls.

Budget for separate items: Meta outbound calling, permission-request messaging where charged, the provider’s subscription or usage fees, and any integration, agent or recording costs. A free inbound Meta call does not mean the provider, internet connection or staffed service is free. Ask for the current rate card in your billing currency and a written explanation of every additional fee. There is no universal India price that covers every vendor’s package.

Practical CRM workflows: what should happen around the call?

Start with a customer problem that needs a conversation. The examples below are proposed operating patterns, not claims of measured results or prebuilt CampaignHQ connectors.

Sales enquiry to a permission-led callback

A prospect asks about a product configuration in WhatsApp. Match the conversation to the CRM lead, assign a salesperson and capture the question. The salesperson requests calling permission, checks approval and availability, then calls. Save the outcome as a concrete next step: quotation requested, demo booked, unsuitable requirement or follow-up declined. Send detailed documents by email or WhatsApp as appropriate.

If you are considering Salesforce CTI integration, establish whether the specific product supports this WhatsApp API, rather than assuming that generic telephony or an AI voice agent does. Require a demo using your CRM record and actual permission flow.

Support escalation without losing the ticket

An agent helping customers via WhatsApp reaches a problem that is easier to discuss. Keep the ticket open, show the previous messages to the call agent, and either receive the customer’s call or obtain permission for an outbound call. Record the resolution and responsible owner. Do not mark a ticket resolved just because a call connected.

Delivery exception with a stop rule

An order system reports an address problem. Send the appropriate message, then offer a call if clarification is needed. Recheck calling permission and the order’s current status before dialling. If the address has already been corrected, cancel the pending task. After resolution, suppress duplicate recovery reminders across email and WhatsApp.

The minimum data handoff

• Identity: CRM contact or ticket ID, WhatsApp identity and business number.
• Context: trigger, case summary, assigned agent, customer language and preferred time.
• Permission: state, source, expiry where applicable, and when it was last checked.
• Call result: call ID, direction, timestamps, connected or missed status, agent disposition and next action.
• Controls: opt-out, complaint, resolved-case and duplicate-event suppression.

A webhook is an event notification, not a complete CRM integration. Meta’s technical FAQ says webhook delivery can be duplicated and arrive out of order. Your integration should deduplicate by event/call identifiers and avoid allowing a late event to reopen a closed task.

What the platform supports, and what to verify with a vendor

• Voice is not a video promise. Meta’s overview marks video and screen sharing as planned or in development. Do not sell those as enabled production features based on app behaviour.
• Customer devices matter. Meta’s FAQ does not support business calls from the customer’s WhatsApp Web or Desktop app. Test the supported mobile experience separately from the agent’s web-based console.
• Recording is not always on. Meta now documents opt-in call recording, with an announcement and a recording-available webhook. Recording and transcription are separate features. Confirm whether your provider exposes them, where data is stored, retention, access and your legal obligations. Calling permission alone is not a complete recording-consent policy.
• Capacity needs account-specific proof. Do not promise unlimited concurrent calls. Check the current API rules and provider limits, then test peak demand and unavailable-agent handling.
• CRM and support are vendor scope. A connector logo does not prove two-way call logging, error recovery or a support commitment.

For example, WATI’s CRM calling guide documents an integration path and describes it as beta/on request, with implementation support for Business Plan customers on a need basis. Those are WATI-specific conditions, not Meta rules or CampaignHQ promises.

Where CampaignHQ fits

CampaignHQ is a Meta Tech Partner focused on customer retention automation across email and WhatsApp, with AWS as supporting infrastructure. Its public voice-calling page describes inbound and permission-led outbound calling alongside the team inbox.

Bring your business number, CRM, desired call workflow and agent requirements for a scoped assessment. Ask the team to demonstrate eligibility, permission handling and the exact integration before committing. For the broader messaging foundation, see CampaignHQ’s WhatsApp marketing features.

Ready to organise the rollout? Use the separate India calling pilot checklist for owners, acceptance tests and a go/no-go decision. This guide remains the reference for platform facts, permissions and pricing.

Frequently asked questions

Can I turn on API calling in the WhatsApp Business app?

App calling and Cloud API calling are different products. Validate your number’s Cloud API configuration and any coexistence restrictions with the provider; an app call working does not prove API eligibility.

Can my sales team call everyone who opted into messages?

No. Message opt-in is not calling permission. Use Meta’s calling-permission flow and check the current state before a business-initiated call.

Are all WhatsApp business calls free?

No. Meta does not charge for user-initiated calls, but outbound calling and relevant permission messages can be charged. Providers may charge separately.

Does the API automatically record every call?

No. Meta documents optional recording configured per call. Provider availability, consent, storage and retention must be checked before enabling it.

Can I keep my existing CRM?

Potentially, if the provider or implementation partner supports the required integration. Verify identity matching, permission state, call events, agent outcomes and failure handling in your CRM. API access alone does not guarantee those workflows.

Written by CampaignHQ Team