We cover the same change for business owners in full on WABB. You can open What’s new on WhatsApp for business in 2026 and read the whole guide there, including the ad window and Meta Business Agent pricing.

The Cloud API is Meta's hosted version of the WhatsApp Business API: your software sends and receives messages by calling Meta's servers. Every fact below comes from Meta for Developers. Each section ends with the page and the date it was checked, because Meta changes these pages often.

1. What is free now, and what is not

Meta bills per delivered message, not per sent one. It charges only for messages from a business to a user. Messages from users to a business are free.

Each business message belongs to one of five categories: Marketing, Utility, Authentication, Service and Meta Business Agent messages. A Service message is any non-template message that the Meta Business Agent platform did not produce, for example a reply written by a person or by a third-party AI. You can send such messages only while the customer service window is open. That window lasts 24 hours and restarts every time the user writes to you.

Meta's five message categories; only Service messages count toward the 1,000 free messages per number.

From 1 October 2026, Meta gives each business phone number a free tier of 1,000 delivered Service messages per month. Meta starts charging with the 1,001st one. Unused messages do not roll over to the next month. The counter resets at 00:00 in the time zone of the messaging account.

Source: Meta for Developers, "Pricing on the WhatsApp Business Platform" (updated 30 Sep 2026), checked 6 Nov 2026. Same topic on WABB: What’s new on WhatsApp for business in 2026.

2. The allowance is per number, not per account

The 1,000 messages belong to each business phone number. A business with three numbers has three allowances. One number that answers a busy support line can run through its allowance in a few days, while a quiet number never gets near it.

The monthly allowance as Meta describes it: free up to 1,000, charged from the 1,001st, reset every month.

Two things follow for your code:

• Count Service messages per phone number, not per account.
• Reset your own counter by the time zone of the messaging account, not by UTC and not by your server clock.

Source: Meta for Developers, "Pricing on the WhatsApp Business Platform" (updated 30 Sep 2026), checked 6 Nov 2026. Same topic on WABB: What’s new on WhatsApp for business in 2026.

3. The webhook field that shows it

Meta marks every message status webhook with a pricing object. For a Service message, the type field tells you whether it fell inside the allowance. Before 1 October 2026, every Service message in an open window had the type free_customer_service. The figure shows how the field reads now.

How pricing.type reads for a service message before 1 October 2026, inside the free tier, and after it.

Inside the allowance:

"pricing": {
  "billable": false,
  "pricing_model": "PMP",
  "type": "free_customer_service",
  "category": "service"
}

After the allowance is used up, the same category arrives like this:

"pricing": {
  "billable": true,
  "pricing_model": "PMP",
  "type": "regular",
  "category": "service"
}

The type changes to regular from the 1,001st message. If your code or your reports treat free_customer_service as "this message is free forever", they are now wrong for busy numbers.

Source: Meta for Developers, "Pricing on the WhatsApp Business Platform" (updated 30 Sep 2026), checked 6 Nov 2026. Same topic on WABB: What’s new on WhatsApp for business in 2026.

4. A missing payment method now has a cost

If a business has no payment method on its messaging account, Meta still delivers Service messages inside the free tier. It stops delivering them once the free tier is used up. Meta's page asks you to make sure a payment method exists in Billing Hub so Service messages keep flowing from 1 October 2026.

What Meta delivers without a payment method: Service messages inside the free tier, none after it.

For a bot, that means a failure tied to the calendar, not to the code: once a number has used its free tier, its replies would stop. Check the payment method before you debug the sending code.

Source: Meta for Developers, "Pricing on the WhatsApp Business Platform" (updated 30 Sep 2026), checked 6 Nov 2026. Same topic on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

5. Exceptions worth knowing

• Free entry point window. When a user writes to you from an ad that clicks to WhatsApp (Android and iOS apps only), your reply opens a free window of up to 7 days. Inside it, Meta does not charge Marketing, Utility, Authentication or Service messages. Meta Business Agent messages are still charged.
• Government and non-profit organizations that Meta treats as eligible keep Service messages free after the monthly allowance, under a policy that runs to 31 December 2027.
• AI providers that build on the platform follow their own pricing policy, so the October change does not apply to them.

The three cases that follow their own rules: the free entry point window, eligible governments and non-profits, and AI providers.

Source: Meta for Developers, "Pricing on the WhatsApp Business Platform" (updated 30 Sep 2026), checked 6 Nov 2026. Same topic on WABB: How to Set Up Click-to-WhatsApp Ads and Answer Every Lead.

6. A note on the marketing page

Meta also publishes a pricing page for businesses. When we checked it on 6 November 2026, it still described Service messages as free and the ad window as 72 hours. The developer documentation above describes the 1,000-message allowance and a window of up to 7 days. When the two disagree, we trust the documentation, which carries the date of its last update. Meta changes prices only on the first day of a quarter and gives at least one month of notice for rate card changes, so the next possible dates are 1 January and 1 April.

What the two Meta pages said on 6 November 2026.

Sources: Meta for Developers, "Pricing on the WhatsApp Business Platform" (updated 30 Sep 2026); WhatsApp Business Platform pricing page for businesses; both checked 6 Nov 2026. Same topic on WABB: What’s new on WhatsApp for business in 2026.

Checklist

• Count delivered Service messages per phone number, by the messaging account's time zone.
• Read pricing.type and pricing.billable from message status webhooks instead of assuming a category is free.
• Make sure every messaging account has a payment method in Billing Hub.
• Check the date on the developer page before you copy a number from a pricing page.

More from the same team: WhatsApp Business Broadcast: Lists, Limits & Cost, How to Set Up Click-to-WhatsApp Ads and Answer Every Lead and WhatsApp Business API Requirements: Checklist for India (2026).

We build WABB (https://wabb.in), a WhatsApp Business API platform. This post is not a pricing guarantee: rates and rules are Meta's and can change on the dates above.

The Cloud API is Meta's hosted version of the WhatsApp Business API: your software sends and receives messages by calling Meta's servers. Every fact below comes from Meta for Developers. Each section ends with the page it comes from and the date it was checked, because Meta changes these pages often.

I work at WABB, which builds on the WhatsApp Business Platform.

1. Check the number before you buy or move anything

A business phone number must meet four conditions:

• you own it;
• it has a country code and an area code (short codes are not supported);
• it can receive voice calls or SMS;
• it has "scaled capabilities" (the page links to Meta's own definition of the term).

Meta's eligibility rules as a checklist: four conditions to meet and two blockers to clear first.

Two blockers are written in the same section. A number that is already in use with WhatsApp cannot be registered until that WhatsApp account is deleted. A number banned on WhatsApp must be unbanned through the appeal process first. Meta also says a registered number can still be used for calls and texts, but not with WhatsApp itself.

Source: Meta for Developers, "Phone numbers" (updated 21 May 2026), checked 4 Nov 2026. Related guide on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

2. Pick a number type that can receive the code

Meta rates each number type for receiving the one-time code, by SMS and by voice call.

Meta's ratings by number type. Only a mobile number is "Standard" on both channels.

A fixed line, VoIP or freephone number relies on the voice code. Meta's advice differs by type. For a fixed line it says to enable international calls and SMS, make sure the line can take incoming calls, and switch off call forwarding and IVR. For VoIP it says to confirm that the VoIP provider supports international calls and SMS.

Source: Meta for Developers, "Phone numbers" (updated 21 May 2026), checked 4 Nov 2026. Related guide on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

3. Adding a number is not registering it

The dashboard flows (App Dashboard, WhatsApp Manager, Meta Business Suite) add the number to your account and verify that you own it. They do not register it for Cloud API. Meta states that you can register a number only through the API: a POST to PHONE_NUMBER_ID/register. Partners that use Embedded Signup follow a separate page of the documentation.

Add and verify happen in the dashboard, registration is API-only, and the status check closes the loop.

The call itself:

curl -X POST 'https://graph.facebook.com/v26.0/<PHONE_NUMBER_ID>/register' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{
    "messaging_product": "whatsapp",
    "pin": "<6_DIGIT_PIN>"
  }'

The registration call with placeholders only. The version in the path (v26.0) is the one used on Meta's phone-number page.

Two details cost time:

• The PIN is required. If the number has no two-step verification yet, the six digits you send become its PIN. If it already has one, you must send the existing PIN. Meta's page says the PIN is needed to change it or to delete the number, so store it. If it is lost, the API can set a new one.
• There is a cap. Meta allows 10 registration requests per number in a 72-hour moving window.

The eleventh request in the window returns error 133016, and the number cannot be registered for the next 72 hours.

Register in two cases: when you create the account, and after a display-name change is approved. Re-registering before approval has no effect, so wait for the phone_number_name_update webhook (a callback Meta sends to your server when the name change is decided).

Source: Meta for Developers, "Register a business phone number" (updated 27 Oct 2026), checked 4 Nov 2026. Related guide on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

4. Confirm the status is CONNECTED

A number can be added and verified and still not be usable. Meta says a number must have the status CONNECTED to send and receive through the API. Ask for it directly:

curl 'https://graph.facebook.com/v26.0/<PHONE_NUMBER_ID>?fields=status' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>'

{ "status": "CONNECTED", "id": "<PHONE_NUMBER_ID>" }

The status check and the response shape from Meta's documentation. The same status appears in WhatsApp Manager under Account tools, then Phone numbers.

Source: Meta for Developers, "Phone numbers" (updated 21 May 2026), checked 4 Nov 2026. Related guide on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

5. Know your messaging limit on day one

The limit is the number of unique WhatsApp users you can message outside a customer service window (the 24 hours that open when a user writes to you) within a moving 24 hours. Three facts matter for planning:

• A new Meta business portfolio, the account that holds your business assets, starts at 250.
• The limit belongs to the portfolio, not to a number. If one portfolio has several numbers, one number can use up the whole allowance.
• You reach 2,000 through one of three paths. After a path is completed, Meta checks message quality and approves or denies the increase.

The limit steps and what moves a portfolio up. Bar heights show the order, not the scale.

You can read the limit from the API with the whatsapp_business_manager_messaging_limit field. The older messaging_limit_tier field is deprecated.

{ "whatsapp_business_manager_messaging_limit": "TIER_250", "id": "<PHONE_NUMBER_ID>" }

A new portfolio's limit as the API returns it, from Meta's example.

Source: Meta for Developers, "Messaging limits" (updated 21 May 2026), checked 4 Nov 2026. Related guide on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

6. Use the test number first, and do not ship the temporary token

When you follow Meta's Get Started guide, a test business number is created and registered for you, so you can send a first message before touching a real number. The access token on that screen expires quickly. For anything that stays running, the guide has you create a system user and generate a token with three permissions.

What the Get Started guide gives you, and what to replace before you go live.

Source: Meta for Developers, "Get started" (updated 16 Jun 2026), checked 4 Nov 2026. Related guide on WABB: WhatsApp Business API Requirements: Checklist for India (2026).

Pre-flight checklist

• The number is yours, has a country and area code, and can receive a voice call or SMS.
• It is not active on a WhatsApp account, and not banned.
• Call forwarding and IVR are off if the number is a fixed or toll-free line.
• The number is added and verified in WhatsApp Manager.
• POST /register succeeded, and the PIN is stored safely.
• fields=status returns CONNECTED.
• You know the starting limit (250) and which scaling path you will use.
• The production token comes from a system user, not the temporary one.

More from the same team, on the WABB blog: WhatsApp Business API Requirements: Checklist for India (2026), and WhatsApp Coexistence: Use the Business App and API on One Number.

Disclosure: I work at WABB, a WhatsApp automation product and WhatsApp Business Platform provider. Nothing above is specific to any provider.