WhatsApp Calling API Providers: Best Options for US Support Teams

Short answer: if your WhatsApp Business number is registered in the United States, every provider on this list gives you exactly the same calling capability, because the limit is set by Meta and not by the vendor. You can receive WhatsApp calls for free. You cannot place them. So the real choice for a US team is not who "supports WhatsApp calling" (they all do), it is what happens to the call once it arrives: where it rings, who picks it up, and whether it can reach your existing phone system.

That is worth saying plainly because most vendor pages selling the WhatsApp Business Calling API to American businesses do not mention the restriction at all, and a few imply outbound is available everywhere. It is not.

The restriction every US buyer needs to see first

Meta's Cloud API calling documentation lists the countries where business-initiated calling is unavailable as the United States, Canada, Egypt, Vietnam and Nigeria. The test runs against your business phone number's country code, not the customer's, so a +1 number cannot place an outbound WhatsApp call even to a customer sitting in a supported country.

Two BSPs publish the same restriction in their own docs and both add Türkiye. Twilio's WhatsApp Business Calling documentation states that business-initiated calling is available "in all Meta Cloud API supported countries except for the following countries: USA, Canada, Egypt, Nigeria, Turkiye, Vietnam." Respond.io words it as "business-initiated calls are currently not allowed in the following locations: United States, Canada, Turkey, Egypt, Vietnam, Nigeria." Three independent sources, one answer.

User-initiated calling is the opposite story. It works in every location the Cloud API is available, and Meta charges nothing for it. There is no per-minute rate on an inbound WhatsApp call and no monthly cap on how many you answer.

What you are actually buying

Since Meta sets the capability, a provider can only compete on four things: whether inbound calls land in an agent inbox alongside the chat thread, whether calls can be transferred or routed, whether they support SIP so calls can terminate in your existing contact center, and what they charge on top of Meta's per-minute rate for the outbound calls you may not even be allowed to make.

Respond.io is worth calling out for honesty: it publishes the country restriction on its own product page rather than burying it, and states that "incoming calls are completely free" while "outgoing calls are billed per minute, with rates depending on the destination region," adding no setup fee or markup for the feature itself. That is the disclosure standard the rest of the category should be held to.

How to choose if you are a US support team

Work backwards from where the call has to ring.

You have no phone system and want the simplest thing that works. Pick a platform with a native inbox, so an inbound WhatsApp call arrives in the same place as the customer's messages and any agent can pick it up with the history in front of them. Respond.io and Infobip's Conversations both do this. The value here is context, not telephony.

You already run a contact center. Go SIP. Infobip supports SIP trunks and WebRTC, 360dialog documents business-initiated calls over SIP with a TLS request URI, and Twilio exposes the plumbing directly. SIP is also the only realistic route if you need call recording, because the WhatsApp Business Calling API does not expose recordings or transcriptions at all. If compliance requires recorded calls, you have to capture the audio at your own media endpoint.

You mainly need someone to answer. Meta's business call hours feature exists precisely because unanswered calls are the failure mode: it lets you direct users to message instead when your call center is closed. If coverage outside business hours is the real gap, the fix is not a different WhatsApp vendor, it is having something that answers the calls that come in after hours and books the follow up rather than letting them ring out.

The eligibility gate everyone forgets

Before any of this matters, your number has to qualify. Calling requires a messaging limit of at least 2,000 business-initiated conversations in a rolling 24 hour period. New WhatsApp Business accounts start at 250, and the way up is completing Meta's free Business Verification and then sending real template traffic with a healthy quality rating. Calling is also enabled per phone number, not per account, so switching it on for one number does nothing for the others in your portfolio.

This trips up more evaluations than the country restriction does. A team signs a contract, tries to enable calling, and finds the toggle inert because the account never got past the starting tier. Check your limit before you shortlist anyone. Our messaging limits calculator shows where a number sits and what moves it up.

What outbound would cost, if you could use it

Incoming calls are free. Outgoing calls are billed per minute against the customer's country code, calculated in six-second pulses and rounded up. Meta's own worked example is a 56 second call: 9.33 pulses, billed as 10. Ringing does not bill, only connected calls do, and monthly volume tiers lower the rate as you send more, with a call crossing a tier boundary priced at the cheaper rate.

Voice is billed separately from messaging, so call minutes do not touch your per message costs. Meta publishes the actual per-minute numbers as a country by country rate card rather than one global price, with rates effective April 1, 2026 based on your WhatsApp Business account timezone and a further update effective July 1, 2026 across 16 currencies. Be sceptical of any article quoting you a flat "US WhatsApp calling rate," since business-initiated calling is not sold on US numbers.

Outbound is capped even where it is allowed

If you operate a non-US number and outbound calling is genuinely on the table, the permission rules will still shape your plan more than pricing does. A customer has to grant call permission before you can call them. That permission expires seven days after it is approved, rejected or ignored. You can send one permission request every 24 hours and no more than two in seven days. Once granted, you get five connected calls per 24 hours for up to seven days, and four consecutive unanswered calls revokes the permission automatically.

Those numbers describe a scheduled callback product, not a dialer. Nobody is working a cold list through this, which is consistent with how Meta treats the rest of the platform: the opt-in rules for messaging land in the same place, and the platform terms have always prohibited bulk auto-dialing.

The realistic US playbook

Publish a click to chat entry point so customers can reach you in one tap, answer the WhatsApp calls that come in, and use the 24 hour customer service window that a call opens to follow up in writing while the context is fresh. A call starts or refreshes that window whether the customer calls you or accepts your call, and free form replies inside it are free today, though they become chargeable on October 1, 2026.

For everything you would have wanted outbound calling to do, use messaging. Utility and authentication templates deliver to US numbers normally, only marketing templates are paused. A well built utility template with a callback link does the job of a cold call without touching a restriction, and if you need structured information before the conversation starts, a form inside the chat collects it without a phone call at all.

The full breakdown of rates, eligibility and permission limits lives on our WhatsApp Business Calling API guide.