WhatsApp Business API Pricing in 2026: Who Charges What

This guide is for finance leads, marketing managers and CX directors budgeting WhatsApp Business API for 2026 and comparing provider quotes. It explains who charges what, what changed on 1 October 2026, how to model costs without guessing rates, and what to ask every provider. It deliberately avoids per-country prices because Meta changes them several times a year; always use Meta's current rate card.

How does WhatsApp Business API pricing work in 2026?

Meta charges per delivered template message, priced by category and the recipient's country. This per-message model replaced conversation-based pricing on 1 July 2025, according to Meta's pricing documentation.

Three things set the Meta price of a message:

1. Category of the template: marketing, utility or authentication.
2. Recipient market, based on the country calling code of the recipient's number.
3. Volume tier, for utility and authentication templates, which get lower rates as monthly volume grows in a given market.

Meta publishes rate cards in several billing currencies, including USD, AED and SAR. Volume is aggregated across all WhatsApp Business Accounts in a business portfolio, per market and category, and resets monthly.

What the categories mean

Meta reviews template categories and can recategorise a template. You accept the charges for the category applied at the time of sending, so a "utility" template with promotional content can end up billed as marketing.

What changed on 1 October 2026?

According to Meta's pricing documentation, service messages are now free only up to 1,000 per business phone number per month, and utility templates sent inside the customer service window became billable. Before this change, Meta's documentation stated that both were free.

Points to confirm in Meta's current rate card and documentation:

• how many business phone numbers you run, since the 1,000-message allowance applies per number, resets monthly and does not roll over;
• the service message rate for each market you serve after the allowance;
• the utility rate that applies inside the window.

Meta also moved more markets out of regional "Rest of" pricing into standalone rate cards from 1 October 2026, including Kuwait and Oman according to its pricing documentation. If you message GCC customers outside the UAE and Saudi Arabia, recheck those rates.

What did not change: marketing and authentication templates remain charged per delivery, and messages sent inside a free entry point window, opened when a user messages you from a Click to WhatsApp ad on the mobile apps, are not charged, per Meta's documentation. That window may remain open for up to 7 days.

Who charges what: Meta, provider or platform?

There are up to three layers in any quote. Knowing which is which is the key to comparing offers.

Some vendors combine all three into one per-message price, others separate them. Neither is wrong, but you need the breakdown to compare.

How do you estimate costs? Three worked scenarios

Use symbolic rates so the model stays valid when Meta updates prices. Let R_marketing, R_utility, R_auth and R_service be Meta's rates for your recipient market, and F the provider's per-message fee where one applies. Replace them with figures from Meta's current rate card and your quote.

Scenario 1: UAE retailer running monthly promotions

"Souq Lamar" (synthetic) sends 4 marketing campaigns a month to 20,000 opted-in UAE customers, with an expected delivery of 18,000 per campaign. Customers reply with questions, generating about 3,000 service replies a month from one number.

• Marketing: 4 x 18,000 x (R_marketing + F)
• Service: (3,000 - 1,000 allowance) x R_service, per Meta's pricing documentation
• Platform: seats for the support team

Cost driver: marketing volume. Better segmentation reduces cost more than anything else.

Scenario 2: Saudi logistics company sending delivery updates

"Najd Express" (synthetic) sends 120,000 utility templates a month in Saudi Arabia: dispatch, out-for-delivery and delivered notices. About 30,000 of these go to customers who have messaged in the last 24 hours, inside the service window.

• Utility outside the window: 90,000 x (R_utility at tier + F)
• Utility inside the window: 30,000 x (R_utility at tier + F), billable per Meta's pricing documentation
• Service replies: allowance first, then R_service

Cost driver: utility volume, partly offset by volume tiers. Check whether any notices could be combined.

Scenario 3: Bank sending one-time passwords across the GCC

"Gulf Trust Bank" (synthetic) sends 200,000 authentication templates a month to customers in several GCC countries, with some customers roaming abroad.

• Authentication: sum per market of messages x (R_auth for that market at tier + F)
• Check authentication-international rates where Meta applies them
• SMS fallback for failures: operator SMS cost per segment

Cost driver: market mix. Model each country separately rather than using one average rate.

Checklist: how to compare WhatsApp API provider quotes

Ask every provider to answer these in writing.

1. Are Meta fees passed through at cost, or with a markup? If marked up, by how much?
2. Is the provider fee charged per submitted, sent or delivered message?
3. Which currency is used, and who carries exchange-rate risk?
4. How are Meta rate changes, such as the 1 October 2026 update, passed on, and with how much notice?
5. Is the service message allowance from October 2026 reflected, and how are service messages billed after it?
6. Are platform seats, features or minimum commitments charged separately?
7. Is billing prepaid or postpaid, and what happens when the balance runs out?
8. Can you see per-message delivery reports to reconcile invoices?
9. Who owns the WhatsApp Business Account and phone number if you leave?
10. Are onboarding, template support and migration included or extra?

Common pricing mistakes to avoid

• Budgeting from an old rate card. Meta changed rates in January, April, July and October 2026. Always download the current card.
• Using one blended rate for many countries. Rates vary widely by market.
• Mislabelled templates. Promotional content in a utility template can be recategorised as marketing.
• Ignoring service messages. High-volume support teams may now exceed the free allowance.
• Paying for undeliverable numbers. Clean and de-duplicate lists before sending.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, charges WhatsApp at Meta's rate with zero markup, has no setup fee and publishes indicative list rates in the cost estimator; the final quote confirms the cost. Billing runs on a prepaid wallet, so spending is visible before you send. Templates are created by category with phone preview and approval tracking, and campaigns use duplicate filtering to avoid paying twice for the same contact. Delivery reports with filters and CSV export help you reconcile costs per campaign. See pricing and the WhatsApp Business API page.