WhatsApp Business Calling API in India: Complete 2026 Guide

Nobody answers unknown numbers any more. Your agent dials, the customer's phone shows a ten-digit stranger, the call rings out, and your contact rate slides another two points. Teams tell us that is the most frustrating figure in their sales and support reporting, because everything upstream works — the ads, the qualification, the CRM hygiene — and the last mile fails at a caller ID the customer does not recognise.

The WhatsApp Business Calling API is Meta's answer to that problem. It puts VoIP voice and video calling on the same business number that already carries your WhatsApp chat, through the Cloud API, so the call arrives inside a thread the customer already recognises. It is generally available rather than beta, India is supported for business-initiated calls, and Meta raised the daily business-initiated call limit from 10 to 100 between October and December 2025.

That does not make it a call-centre replacement. This guide covers what the API actually does, where it works, the design pattern that makes it useful instead of intrusive, the arithmetic of moving outbound volume onto it, and the limits worth knowing before you commit a team to it.

Key points

• The WhatsApp Business Calling API is a Cloud API capability that lets a business and a user place VoIP voice or video calls on the business's existing WhatsApp number, with screen sharing supported.
• User-initiated WhatsApp calling is available wherever the Cloud API operates, so any market you already message in can receive inbound calls.
• Business-initiated WhatsApp calling is available everywhere except the USA, Canada, Egypt, Vietnam and Nigeria, which means India is supported and a US-facing programme is not.
• Meta raised the daily business-initiated call limit from 10 per day in October 2025 to 100 per day in December 2025, so outbound calling is still a targeted tool rather than a dialler replacement.
• Meta added SIP health status and context propagation in September 2025 and G.711 audio codec support in March 2026, which matters for teams bridging WhatsApp calls into existing telephony.
• WhatsApp calling is priced separately from WhatsApp messaging, so call minutes sit outside the marketing, utility, authentication and service message categories entirely.

What the WhatsApp Business Calling API is

The WhatsApp Business Calling API is a Cloud API capability that lets a business and a WhatsApp user place VoIP voice and video calls to each other on the business's WhatsApp number, with screen sharing supported, so messaging and calling share one identity and one thread. Per Meta's WhatsApp Calling documentation, it is generally available rather than a closed beta, and it covers calls in both directions: the user can call you, and your system can call the user.

The unification is the point. Most Indian businesses currently run two disconnected stacks: WhatsApp for messaging through a platform layered on the official WhatsApp Business API, and a separate cloud-telephony number for voice. The customer experiences those as two different companies. They chat with you on one number, then get a call from another, with an agent who cannot see the chat and a customer who has to explain the problem twice.

One number, two modalities

Running the WhatsApp voice call API on your messaging number changes three things in practice.

Identity travels with the call. The customer sees the business they were already talking to, not an unrecognised series of digits, which is the whole reason contact rates fall on ordinary outbound dialling.

Context travels with the call. Meta added context propagation in September 2025, so the chat that preceded the call can be carried through to the agent rather than reconstructed from a CRM tab. The practical effect is that your agent opens the call already knowing which order, policy or application is in question.

Data travels during the call. Because the thread is live, an agent can send a document, a payment link, a template or a WhatsApp Flow mid-conversation instead of saying "check your email". Screen sharing extends the same idea for anything visual — a form, a statement, a portal walkthrough.

WhatsApp Calling API in India: where it works and where it does not

Availability splits by who starts the call, and this is the distinction that decides whether the WhatsApp business call feature fits your programme.

User-initiated calling is a call the user places to your business number from inside the chat, and it is available wherever the Cloud API operates. Business-initiated calling is a call your system places to a user through the API, and it is available everywhere except the USA, Canada, Egypt, Vietnam and Nigeria.

India sits in the supported set for both directions. A Mumbai NBFC, a Bengaluru D2C brand or a Kota coaching institute can place business-initiated WhatsApp calls today. A business whose primary market is the United States cannot, and no amount of platform configuration changes that — the restriction is Meta's, not your provider's.

That last row is the one teams underestimate. Turning on inbound calling means your WhatsApp number becomes a phone number people expect to be answered, at times you did not schedule. If your support desk runs 10am to 7pm IST, decide now what happens to a call at 11pm — an announcement, a routing rule, a message asking them to reply in chat — rather than discovering it in a review three months later.

The capability timeline: September 2025 to March 2026

The WhatsApp Business Calling API has moved quickly, and the version of it that people evaluated in mid-2025 is not the version available now. Four changes matter.

Read that timeline as a direction of travel rather than a finished product. The limit went 10, then 100, in roughly two months. Codec support arrived when interoperability became the blocker. If the 100-per-day ceiling is the only thing standing between you and a deployment, design for it now and check Meta's release notes quarterly rather than shelving the project.

The G.711 addition deserves a note for anyone with an existing contact centre. G.711 is an uncompressed narrowband codec that virtually all legacy telephony equipment supports natively, so a WhatsApp call bridged into a SIP trunk no longer needs a transcoding step that adds latency and degrades audio. Combined with SIP health status, that is what makes the "WhatsApp as another queue in our existing ACD" architecture plausible instead of theoretical.

WhatsApp calling versus a traditional IVR or cloud-telephony call

Both channels can complete the same job — a human speaking to a customer — and they fail in completely different ways. This is the comparison to bring to an internal review.

Nothing in that table says replace your telephony. It says the two channels have inverted strengths. WhatsApp calling wins where the customer already knows you and the conversation needs shared context. Telephony wins on reach, scale and maturity. The teams getting value from the WhatsApp voice call API in 2026 are running it as a high-intent lane in front of their existing stack, not as a rip-and-replace.

The design pattern that works: chat first, call second, always with context

There is one pattern that works and one anti-pattern that will cost you the channel.

The pattern: the conversation starts in chat, the customer signals that text is not enough, and the call happens with their agreement and your context attached. Concretely, a five-step sequence.

1. The thread opens in text, either from the customer messaging you or from a utility template you had a reason to send.
2. Automation handles what it can — status lookups, rescheduling, document collection — ideally through a structured form rather than twenty questions, which is what the WhatsApp Flows implementation guide covers.
3. The escalation is offered, not imposed. A button or a clear line: "Would you like our loan officer to call you now, or shall we continue here?"
4. The call is placed with context. The agent opens with the case already loaded, not with "how may I help you today".
5. The outcome returns to the thread. A written summary, the document, the next step. The chat remains the record.

The anti-pattern is the cold call. Placing a business-initiated WhatsApp call to someone who has not asked for one is the fastest way to destroy the channel, and the damage is not confined to calling. Your calling number is your messaging number. Quality rating on the WhatsApp Business Platform is driven by user feedback — blocks and report taps — so a customer who is annoyed by an unexpected call and blocks the number has just degraded the same asset that carries your order updates and OTPs. The WhatsApp quality rating guide covers how quickly that compounds: ratings run GREEN, YELLOW, RED and UNKNOWN, and Meta's own wording for RED is that the number is "in danger of being paused or disabled soon".

What most teams get wrong about WhatsApp calling

They treat it as a cheaper dialler. It is not built for volume outbound, and the 100-per-day business-initiated ceiling is Meta telling you so. If your plan needs 4,000 dials a day, this is the wrong instrument for 3,900 of them.

They forget the number is shared. Enthusiasm for calling gets budgeted separately from messaging risk, but there is one number, one quality rating, and one block button. Route the calling programme through the same governance as your broadcast programme.

They skip the fallback. A WhatsApp call needs a data connection on both ends. In tier-2 and tier-3 India, on a low-end Android on a congested cell, that connection is not a given. Every critical journey needs a PSTN number to fall back to, and your agents need to know when to switch.

They do not instrument audio. Message delivery either happens or does not. A call can connect and still be unusable at 300ms of jitter. If you are not watching call quality metrics, your customers are experiencing something you cannot see.

They assume contact-centre features exist. Queueing, whisper coaching, call recording with consent capture, wrap-up codes, workforce scheduling: none of that is a given. Ask your provider what is exposed, in writing, before you promise it to an operations head.

Where WhatsApp calling earns its place, by vertical

Business-initiated calling at 100 a day is a scalpel. That points it at conversations where a single call carries real value, not at mass outreach.

Healthcare and financial services are the two verticals where the upside and the caution are both highest. Voice is genuinely better than text for a patient who has just received a worrying report, and it is genuinely riskier, because the same conversation carries sensitive information over a channel your compliance team has not signed off on. The WhatsApp for healthcare playbook and the WhatsApp for BFSI in India guide go into the data-minimisation practice each one needs; neither is legal advice, and both sectors should route the design past their own counsel.

Worked example: a hypothetical NBFC in Mumbai

Take a hypothetical Mumbai NBFC servicing 60,000 active loan accounts, with a 40-seat outbound desk. The numbers below are illustrative, and the point is the shape of the constraint, not the rupees.

Today. The desk places 18,000 outbound dials a month from a cloud-telephony number. Suppose its own dashboard shows a 22% connect rate. That is 3,960 conversations for 18,000 dial attempts, and roughly 14,000 wasted agent actions.

Redesigned as chat-first. The same 18,000 contacts receive a utility template on WhatsApp instead — a payment-due notice with a clear reply path.

• Suppose 30% reply: 18,000 × 0.30 = 5,400 conversations open inside the 24-hour customer service window, at no dialling cost and no ring-out.
• Of those, suppose 25% need a voice conversation, and either ask for a call or accept an offered one: 5,400 × 0.25 = 1,350 calls a month.
• Against 22 working days, that averages 1,350 ÷ 22 = 61 business-initiated calls a day, comfortably inside the 100-per-day ceiling.

Then check the peak, which is where this design usually breaks. Collections volume is not flat; it clusters at month-end. If 35% of the month's calls land in the last four working days, that is 1,350 × 0.35 = 472 calls over 4 days, or 118 calls a day — above the 100-per-day business-initiated limit. The programme works on the monthly average and fails in the week that matters.

The fixes are all design choices, not platform upgrades. Smooth the template send schedule so replies arrive across the month instead of bunching. Push more of the peak toward user-initiated calls, which are not governed by the business-initiated daily cap, by making "call us now" the visible action in the reminder thread. And keep telephony live for the residual. If you want that arithmetic run against your own three months of dialler and WhatsApp data, InfiQ's solutions team will model it with you before you commit a headcount plan.

Two costs sit alongside each other in that model, and they are billed on different logics. The 18,000 utility template messages are priced per message under Meta's per-message model, which replaced conversation-based pricing on 1 July 2025 — and note that from 1 October 2026 Meta resumes charging for service messages and for utility messages sent inside an open customer service window, both currently free, which the 2026 WhatsApp Business API pricing guide sets out in full. The 1,350 calls, at say 3.5 minutes average, are 4,725 minutes billed separately under Meta's calling rates. Pull the current figures from Meta's downloadable rate card or run them through InfiQ's WhatsApp cost calculator rather than reusing a number from a vendor blog.

How to set up the WhatsApp Business Calling API

1. Confirm your number is on the Cloud API. Calling is a Cloud API capability. If you are still on On-Premises, migration comes first, and it preserves your display name, quality rating, templates and messaging limits while changing media IDs, error codes and webhook payloads.
2. Check availability for your actual markets. Business-initiated calling is unavailable in the USA, Canada, Egypt, Vietnam and Nigeria. If your customer base spans those, plan two architectures from the start.
3. Enable the calling capability on the phone number. This is a per-number setting exposed through WhatsApp Manager or your provider's console, not something that switches on with the messaging integration.
4. Subscribe to call webhooks alongside your message webhooks, and handle every state — ringing, connected, ended, failed, rejected — as a distinct event. The WhatsApp webhooks guide covers signature verification and retry behaviour.
5. Decide the media path. Either agents take calls in a browser or app client your platform provides, or you bridge into existing telephony over SIP, where G.711 support since March 2026 and SIP health status since September 2025 do the heavy lifting.
6. Build the invitation handshake before the dialler. The mechanism that asks the customer whether they want a call, records the answer, and honours a refusal is the part that protects the number. Build it first.
7. Wire context propagation through to the agent view so the chat, the order or account reference, and any Flow submission are on screen at pickup.
8. Test on the hardware your customers actually own. One low-end Android on a congested 4G cell, one iOS device, one call over hotel wifi. Test the failure path: what the customer sees, and what your system logs, when the call drops at 40 seconds.
9. Pilot on one intent and 200 to 500 contacts. Pick something with an unambiguous outcome — documentation completion, disruption rebooking — and compare against your existing telephony baseline for the same intent.
10. Set the daily counter and the alert before you scale, not after the first day you hit the ceiling.

What to instrument

• Call setup success rate, separated from connect rate. A call that never rings is a platform problem; a call that rings and is not answered is a permission problem.
• Audio quality metrics — jitter, packet loss, and a mean opinion score if your stack produces one. Alert on degradation, not only on failure.
• SIP health status, if you are bridging into telephony. It exists so you can see session health as a signal rather than inferring it from complaints.
• Business-initiated calls per day, with an alert at 80 of the 100 ceiling and a projection for the rest of the month's peak days.
• Block and report rate on the number, plotted against your calling volume. If the two move together, stop calling and re-read your invitation logic.
• Quality rating trend on the phone number, pulled the same way you monitor it for broadcast campaigns.
• Outcome codes back into the CRM, so a call has a result your funnel can read, not just a duration.

The honest limitations

This section exists because the enthusiastic version of this post would skip it.

No data, no call. A WhatsApp video call or voice call needs a working data connection at both ends. For a lender chasing a customer in a low-coverage district, or a hospital calling an elderly patient on a basic connection, ordinary telephony still reaches people this channel cannot. Keep a PSTN path.

Business-initiated calling is geographically restricted. USA, Canada, Egypt, Vietnam and Nigeria are excluded. India is supported, which is the reason this post exists, but a global programme needs a fallback for those five markets.

100 calls a day is a real ceiling. It went from 10 to 100 between October and December 2025, so it may rise again, but design against today's number. Averages hide peaks, as the worked example shows.

It is not a contact-centre platform. Meta ships a calling capability. Queue management, skills-based routing, recording with lawful consent capture, quality monitoring, workforce management and reporting either come from your platform provider or come from you. Establishing which is a procurement question, and it belongs in the provider evaluation checklist for Indian WhatsApp Business API platforms.

Trust is borrowed, not owned. The customer answers because they recognise the business. That recognition is built on your approved display name and, for many brands, Official Business Account status — which Meta calls a blue checkmark and the Indian market calls the green tick. OBA status attaches to a phone number and display name, and non-OBA numbers do not appear in WhatsApp's in-app search at all, so discoverability and answer rates share a root cause. The green tick verification guide covers eligibility, including the 30-day registration minimum and the reapply-after-30-days rule.

The regulatory position needs your own counsel, not ours. TRAI's DLT and TCCCPR framework governs commercial SMS and voice communications carried over telecom operator networks. WhatsApp calls travel over Meta's platform rather than those telecom voice routes, and in practice Meta's own Business Messaging Policy and consent requirements are the standard teams are held to. That is not a regulatory exemption and should not be treated as one. Separately, India's Digital Personal Data Protection (DPDP) regime bears directly on whether you may record a call and how long you keep it — treat consent and retention as design constraints, not afterthoughts. The WhatsApp opt-in and DPDP guide covers the consent mechanics; take independent legal advice on your specific design.

Pricing is separate and you should verify it yourself. Calling is priced separately from messaging, so your WhatsApp bill gains a second line item with its own logic. Meta publishes rates per market, and rates change only on 1 January, 1 April, 1 July or 1 October with defined notice periods. Do not budget from a figure you found in a blog post, including this one.

Get started with InfiQ

Calling is the first WhatsApp capability where the wrong deployment costs you more than it earns. Done well, it removes the worst part of outbound — the unrecognised number — and lets an agent open a conversation already knowing the case. Done as a cheap dialler, it converts a working messaging channel into blocks on the number that also sends your OTPs.

Ready to escalate the right conversations to a call instead of dialling everyone? Start your 7-day free trial — InfiQ gets you live on the official WhatsApp Business API in about 2 hours, with a shared team inbox where chat and escalation sit in one place and InfiQ Flows to qualify before anyone picks up a headset. Or book a walkthrough if you want to see it mapped to your own call volumes first, and the developer documentation if you would rather read the API surface before you talk to anyone.