Since October 1, 2026, WhatsApp charges for service messages: the replies you send inside the 24-hour customer service window after a customer writes to you. Each business phone number gets 1,000 of them free every month.
The part that breaks production is what happens next. If your WhatsApp Business Account has no payment method on file, Meta delivers the first 1,000 free service messages and stops delivering service messages at message 1,001. Your support bot, your agents, your AI assistant: all of them go quiet on WhatsApp, in the middle of a month, with no change on your side.
This post is the practical half of the change. For the full pricing model, before and after, read WhatsApp starts charging for your replies on October 1, 2026. Here: what the 1,000 free messages cover, how to check your billing setup in five minutes, and how to recognise the failure if it already happened.
The short version
- From October 1, 2026, service messages are billable after the first 1,000 delivered per business phone number per month.
- The price is the utility rate of the recipient's country. No volume discounts on service messages.
- Utility templates sent inside the 24-hour window are billable too.
- Free: messages customers send you, reactions, and everything inside the 72-hour free entry point window.
- No payment method on the WhatsApp Business Account means Meta stops delivering service messages at message 1,001. Not a provider limit, not a balance issue. Meta simply does not deliver the message.
What the 1,000 free service messages cover
A service message is a free-form reply, not a template, sent while the customer service window is open. The window opens when a customer messages you and lasts 24 hours from their last message. Anything your team, your inbox or your AI agent writes back in that window is a service message.
How the allowance works:
| Question | Answer |
|---|---|
| How many are free? | 1,000 service messages per month |
| Per what? | Per business phone number, not per account or per company |
| Does it reset? | Yes, every month |
| Do unused messages carry over? | No |
| What counts? | Delivered service messages |
| What does message 1,001 cost? | The utility rate for the recipient's country |
The per-number part matters if you run several numbers. A WhatsApp Business Account with five registered numbers has five separate allowances of 1,000. A single number that handles all your support burns through one allowance five times faster.
A quick way to size it: 1,000 messages a month is about 33 replies a day. A support team answering 30 conversations a day with three replies each will cross it around the eleventh day of the month.
What stays free
Not everything moves. These remain free after October 1:
- Inbound messages. Everything your customers send you.
- Reactions.
- The 72-hour free entry point window. When someone reaches you through a Click to WhatsApp ad or a Facebook Page call-to-action button and you reply within 24 hours, what you send for the next 72 hours is free.
And one thing that used to be free and is not anymore: a utility template sent inside an open 24-hour window. It is now charged at the utility rate, window open or not.
Why message 1,001 fails without a payment method
WhatsApp message fees are billed by Meta, to the payment method on your WhatsApp Business Account (WABA). Until now, a business that only answered customers could run for months without one, because replies inside the window cost nothing.
From October 1, service messages have a price after the free allowance. Meta's rule for accounts that cannot pay is to stop delivering them: the first 1,000 service messages of the month go out, and from message 1,001 Meta does not deliver service messages until a payment method is on file.
Three consequences worth planning for:
- It fails mid-month, not on the 1st. Everything works when the month starts. The failure arrives whenever a number crosses 1,000, which for a busy number could be the second week.
- It fails per number. One high-volume number can stop while a quieter one keeps working, which makes it look like a bug in your code.
- Templates are a separate question. Sending templates has always required billing on the account. Accounts that only ever replied inside the window are the ones exposed.
How to check your WhatsApp payment method in five minutes
Do this for every WhatsApp Business Account you send from.
If you connected WhatsApp to Zavu through embedded signup, the WhatsApp Business Account is yours, in your Meta business portfolio. That is where the payment method goes. There is nothing to add on the Zavu side.
How to tell if it already happened
The symptom is a WhatsApp reply that is accepted by the API and then never arrives, starting at some point in the month and only on one number.
In Zavu, a message Meta refuses to deliver moves to failed, unless it fell back to SMS (see below). You will see it:
- In the dashboard, on the message, with the reason.
- Through
GET /v1/messages/{messageId}, witherrorCode131042and anerrorMessagesaying the account's payment method is not configured, declined or over its limit. - On your webhook, as a
message.failedevent carrying the sameerrorCode.
If failures start in the second half of the month, cluster on one number and mention payment or billing, the cause is almost always the missing payment method. Add it in Meta's billing settings; new replies deliver again once Meta sees a valid method. The ones that already failed are not delivered later, so resend the ones that matter.
One safety net worth knowing: if the Zavu sender also has SMS and you sent with channel omitted or set to auto, a failed WhatsApp text or template message falls back to SMS automatically. The customer still gets an answer, billed as an SMS. Sends with channel: "whatsapp" do not fall back unless you set fallbackEnabled: true, and media, buttons, lists and other WhatsApp-only types never do. It is not a substitute for fixing billing.
Where Zavu fits
Nothing changes in how you connect or use WhatsApp through Zavu.
| Who bills it | |
|---|---|
| WhatsApp messages, including service messages beyond the free 1,000 | Meta, to your WhatsApp Business Account |
| Your Zavu plan, overage, extra WhatsApp connections, SMS, voice, email | Zavu |
Zavu does not resell WhatsApp messages and adds no markup to Meta's rates, so Meta's October 1 change did not change your Zavu invoice. WhatsApp messages do count toward your Zavu plan's monthly message allowance.
What does change is the infrastructure under your WhatsApp traffic: sending a reply can now have a Meta cost, and hitting the free limit without a payment method means replies stop going out.
How to spend less on service messages
Once the 1,000 are gone, every reply costs the utility rate. A few habits keep that number down:
- Say it in one message. Three short replies cost three times one complete reply. If an AI agent answers for you, prompt it for brevity; it is now a line on an invoice.
- Spread traffic across numbers where it makes sense. The allowance is per number, and each number gets its own 1,000.
- Use Click to WhatsApp ads for paid traffic. Conversations that start there are free for 72 hours.
- Deflect what does not need a reply. A tracking link or a status page removes conversations that are about to become billable.
- Check template categories. A utility notification miscategorised as marketing is billed at the marketing rate on every send.
The deeper version of each of these is in the full October 1 pricing guide.
Watch the explainer
The video at the top of this post walks through the change in three minutes. Watch it in your language:
- English: WhatsApp API pricing from October 2026
- Español: Precios de la API de WhatsApp desde octubre 2026
The one thing to do today
Open Meta's billing settings and confirm that every WhatsApp Business Account you send from has a valid payment method. It takes five minutes, and it is the difference between a small Meta invoice and a support channel that goes silent at message 1,001.