What Changes on WhatsApp Calling Rate Cards on 1 October 2026?
On 1 October 2026, nine markets move out of their respective "Rest of" pricing regions and become standalone on WhatsApp Business Calling API rate cards: Bangladesh, Iraq, Kazakhstan, Kuwait, Morocco, Nepal, Oman, Sri Lanka and Ukraine. Meta published the rate cards effective that date across 16 currencies on 11 September 2026.
The sentence most coverage leaves out is the important one. Calling rates do not change on 1 October 2026. Each of the nine markets keeps the rate of the region it is leaving, and Meta states that no market's per-minute rate or volume tier thresholds increase or decrease. This is a structural change to how the rate card is laid out, not a price rise.
| What | Until 30 September 2026 | From 1 October 2026 |
|---|---|---|
| Rate card listing | Inside a "Rest of" pricing region | Standalone market on the calling rate card |
| Per-minute rate | The "Rest of" region rate | Unchanged: the same rate as the region it is leaving |
| Volume tier thresholds | The region's thresholds | Unchanged: no increase or decrease |
| Currencies on the rate cards | Published across the current currency set | Rate cards effective 1 October 2026 across 16 currencies |
Which Nine Markets Become Standalone in 2026?
The nine markets moving out of their "Rest of" regions on 1 October 2026 are listed below. Meta says the change aligns calling rate cards with the same nine markets becoming standalone for messaging, which it announced on 27 May 2026.
| Market | Calling rate on 1 October 2026 |
|---|---|
| Bangladesh | Keeps the rate of the region it is leaving |
| Iraq | Keeps the rate of the region it is leaving |
| Kazakhstan | Keeps the rate of the region it is leaving |
| Kuwait | Keeps the rate of the region it is leaving |
| Morocco | Keeps the rate of the region it is leaving |
| Nepal | Keeps the rate of the region it is leaving |
| Oman | Keeps the rate of the region it is leaving |
| Sri Lanka | Keeps the rate of the region it is leaving |
| Ukraine | Keeps the rate of the region it is leaving |
India is not on the list. Indian businesses calling Indian numbers see no change from this restructuring. Indian businesses that call customers in neighbouring markets, particularly Bangladesh, Nepal and Sri Lanka, should note that those markets become standalone, which matters for how future rate changes can be applied to them individually.
Why Does a Change That Does Not Change Prices Matter in 2026?
Because a standalone market can be repriced on its own. While a market sits inside a "Rest of" region, it moves only when the whole region moves. Once it is standalone, Meta can update that single market's rate at any of its regular pricing dates without touching the others. October 2026 changes nothing about today's bill and a great deal about how predictable the bill for those nine markets is from here on.
The messaging side of the same nine markets shows what that can look like. On the messaging rate cards for 1 October 2026, Meta lists utility and authentication rate increases for Kazakhstan, Kuwait, Morocco, Oman and Ukraine, decreases for Bangladesh, Iraq, Nepal and Sri Lanka, and new authentication-international rates in all nine. For calling, Meta has deliberately held the rates flat. For messaging, the same standalone status came with movement in both directions on day one.
If you call customers in any of these nine markets, stop budgeting them as part of a blended regional rate. Track them as individual lines from 1 October 2026, because the next time Meta updates calling rates it can move each of them independently.
How Is WhatsApp Calling Priced in 2026?
All user-initiated calls are free. Businesses are charged for the calls they place, and Meta prices those on three factors. A valid payment method is required to place calls at all.
- Duration, calculated in six-second pulses.
- The country code of the phone number being called.
- Volume tier, based on minutes called within the calendar month, using the same tiering accrual as messaging.
The six-second pulse rule
Meta counts fractional pulses as one full pulse. Its own example is a 56-second call, which is 9.33 pulses, billed as 10 pulses. Every call is therefore rounded up to the next six seconds.
| Illustrative call length | Exact pulses | Billed pulses | Billed duration |
|---|---|---|---|
| 6 seconds | 1.00 | 1 | 6 seconds |
| 7 seconds | 1.17 | 2 | 12 seconds |
| 56 seconds | 9.33 | 10 | 60 seconds |
| 2 minutes 1 second | 20.17 | 21 | 2 minutes 6 seconds |
Only the 56-second row is Meta's own example. The other rows apply the same published rule to invented call lengths to show how rounding works. Multiply billed duration by the per-minute rate for the destination market on your own currency's rate card to estimate cost.
Calls that cross a volume tier
Volume tiers reward monthly calling volume with lower rates. When a single call crosses from one pricing tier into the next, Meta prices the entire call at the lower rate, meaning the rate of the higher volume tier. A long call that tips you into a cheaper tier is therefore billed wholly at the cheaper rate, rather than split between the two.
What Does This Mean for Indian Businesses Using WhatsApp Calling in 2026?
For calls to Indian numbers, nothing changes on 1 October 2026. The practical work for an Indian team is not about this restructuring at all. It is about the pricing mechanics that apply every day, and about the accounts they sit on.
- User-initiated calls are free, which makes a call button on a WhatsApp message or profile a low-cost support channel.
- Business-initiated calls are rounded to six seconds, so short confirmation calls carry proportionally more rounding.
- Volume tiers accrue on calendar-month minutes, so concentrating calling on one account can lower the blended rate.
- A payment method is mandatory to place calls.
- Billing currency matters: eligible Indian customers must move all Messaging accounts to INR by 31 December 2026, as covered in our messaging_account_id and INR migration guide.
What Else Changed for WhatsApp Calling in September 2026?
Alongside the rate card notice, Meta made several calling-related documentation changes in the same weeks. They are not pricing changes, but each affects how a calling integration should be built.
| Date | Change | Why it matters |
|---|---|---|
| 16 September 2026 | Calling integration patterns and the Calling FAQ recommend the new WhatsApp account model for messaging and calling on one phone number, replacing legacy multi-partner approaches. | Calling and messaging can share a number under the new model. |
| 22 September 2026 | SIP security guidance clarified: Meta supports mutual TLS when it acts as the TLS client, not when it acts as the TLS server. | Relevant to anyone integrating calling over SIP. |
| 31 August 2026 | Known issue noted: when a user changes networks during a call, the recording and transcript can be cut short. A fix is rolling out. | Do not treat a truncated transcript as a complete record. |
The account model recommendation connects to our guide to the new business account model. If calling and messaging are handled by different partners on one number, also read the partner assignment readiness checklist, since call routing and webhook delivery are separate from messaging thread ownership.
What Should You Do Before or Shortly After 1 October 2026?
- List the destination markets your business calls, and check whether any are among the nine.
- Download the 1 October 2026 rate card in your billing currency from Meta's calling pricing page.
- Confirm the rate is unchanged for any of the nine you call, as Meta states it should be.
- Re-budget those markets as individual lines rather than as part of a regional blend.
- Confirm a payment method is attached, since one is required to place calls.
- Check call-length patterns, since six-second rounding weighs most on very short calls.
- Review transcripts and recordings with the network-change known issue in mind.
What Are the Common Mistakes in 2026?
- Reporting this as a price rise. Meta states calling rates do not change on 1 October 2026.
- Assuming India is affected. India is not one of the nine markets.
- Budgeting the nine as a blended region. They are standalone from 1 October 2026 and can be repriced individually.
- Billing call length to the second. Calls are charged in six-second pulses, rounded up.
- Splitting a tier-crossing call between two rates. The entire call is priced at the higher volume tier's lower rate.
- Charging customers for calling you. All user-initiated calls are free.
- Treating every transcript as complete. A network change mid-call can cut recordings and transcripts short.
Key Takeaways for 2026
The 1 October 2026 calling change is a restructuring that costs nothing today and makes nine markets individually priceable from here on.
- Bangladesh, Iraq, Kazakhstan, Kuwait, Morocco, Nepal, Oman, Sri Lanka and Ukraine become standalone on calling rate cards on 1 October 2026.
- Calling rates do not change on that date; each market keeps the rate of the region it leaves, and volume tier thresholds do not move.
- Meta published the 1 October 2026 rate cards across 16 currencies on 11 September 2026.
- India is not among the nine markets.
- All user-initiated calls are free, and business-initiated calls are charged in six-second pulses, with fractions rounded up.
- A call crossing into a higher volume tier is priced entirely at that tier's lower rate.
- A valid payment method is required to place calls.
Distk helps growth teams across India and internationally decide where WhatsApp calling belongs in a support and sales flow, budget it by market rather than by region, and keep calling and messaging working cleanly on one number. If calling is part of your WhatsApp plan for 2026, that design is where we start.
Sources
- Calling API Pricing, Meta for Developers, updated 11 September 2026.
- WhatsApp changelog, Meta for Developers, entries dated 31 August, 11, 16 and 22 September 2026.
- Pricing on the WhatsApp Business Platform, Meta for Developers, for the messaging rate card changes in the same nine markets.