WhatsApp Business API pricing change, October 2026: what's actually confirmed
We read through a stack of blog posts about the WhatsApp pricing change this month, and they don't agree with each other. Some say there's a free monthly allowance before you get charged. One says flatly there isn't. So we went to Meta's own documentation ourselves to see what it actually says, and we're sharing exactly what we found below.
Short answer: starting October 1, 2026, Meta charges per message for service messages (free-form replies inside the 24-hour customer service window) and for utility template messages sent inside that same window. By market, the rate for service messages is the same as the rate for utility and authentication messages, and there are no volume tiers for service messages. We confirmed all of that directly in Meta's developer documentation. A widely repeated claim that each phone number gets 1,000 free service messages a month before charges apply is not confirmed anywhere in Meta's own pages, so we wouldn't budget against it until you see it on your own account.
What changed, and what we confirmed directly from Meta
Service messages, the everyday free-form replies a human agent or a chatbot sends inside WhatsApp's 24-hour customer service window, had been free since November 2024. We checked Meta's own developer documentation, and it now states plainly that this is ending: Meta will charge on a per-message basis for service messages, and for utility messages sent in response to users within an open 24-hour customer service window, effective October 1, 2026.
That's the confirmed part, and we're quoting it straight from Meta's pricing documentation rather than passing along a vendor's summary of it. Receiving messages stays free, and Meta's documentation states outright that "the 72-hour free entry point window is unchanged for message delivery," meaning conversations that start from a Click-to-WhatsApp ad or a Facebook Page button keep their free window.
The same page also answers the question of price. In its words, "by market, rates for service messages are the same as the rates for utility and authentication messages," and Meta does not offer volume tiers for service messages, while utility and authentication messages keep theirs. So the more you send, the price per service message does not go down.
We also found a hard deadline in Meta's documentation that several vendors had reported without citing a source: "for any Solution Provider or directly-integrated businesses that does not have a payment method on file by September 30, 2026, Meta will stop delivering service messages" once charging started on October 1.
What's still disputed
A number circulating in nearly every vendor explainer this month is a free monthly allowance of 1,000 service messages per business phone number, after which charges apply. Several platforms state this as fact. At least one states just as plainly that Meta has published no such allowance. We searched Meta's own developer pricing documentation for the number, and it isn't there.
That doesn't mean the allowance is fiction. Multiple platforms converging on the same specific figure is real evidence, but it does mean we can't confirm it where you could check it yourself. We'd treat it as a rumor with decent odds, not a number you plan your budget around.
What you won't find on that page is a dollar figure for every market: it sends you to Meta's rate cards instead. For a sense of scale, the same page gives one concrete example, a $0.0068 delivery rate for utility and authentication messages to users in Brazil. If service messages follow the same rule there, that is what one reply would cost, but check your own market's rate card before you do any math.
What this means if you run a WhatsApp bot
A habit a lot of scripted bots still have is sending three to five short messages in a row to feel more like a live conversation: "Hi there!", "One sec...", "Here's your answer." Since October 1, each of those is a separate billable message, so that habit now has a direct cost attached to it.
We'd make two changes regardless of which platform you run your bot on:
- Combine information into one message. A list or a few bullet points in a single reply covers the same ground as a chain of three or four separate pushes, at a fraction of the message count.
- Keep branching, multi-step conversations off WhatsApp where you can. A long qualifying flow works just as well on a website chat widget or Telegram, leaving WhatsApp for the critical service notifications it's actually built for.
For e-commerce and service businesses with a low average order value, this is worth taking seriously. At a few cents a message, a routine support conversation that takes four or five replies to resolve can quietly eat into the margin on a single order. If you're setting up a bot on Mavibot and want the no-code basics first, our WhatsApp bot guide covers connecting WhatsApp and building the conversation flow.
What we'd check now
- Confirm a payment method is on file for your WhatsApp Business Account. Meta's documentation said it would stop delivering service messages for any account without one on file by September 30, 2026.
- Pull last month's message volume, split into service messages and template messages, so you have a baseline to compare against now that billing has started.
- Check your first October invoice line by line, not just the total. Whether free-form replies appear as billable from message one or from message 1,001 answers the disputed allowance question for your account better than any blog post can.
- Don't restructure your bot's flows around the unconfirmed allowance. Wait for your first invoice, then optimize against what you were actually charged.
Keep your WhatsApp bot efficient with Mavibot
Whatever Meta ends up charging, a bot that answers in fewer, clearer messages costs less either way. With Mavibot's chatbot builder, we make it easy to design conversations that get to the point, and move the parts that don't need to live in WhatsApp onto your website chat or Telegram instead. Start free.
Frequently asked questions
Is WhatsApp really charging for service messages starting October 1, 2026?
Yes. Meta's own developer documentation states it will charge on a per-message basis for service messages and for utility messages sent within an open 24-hour customer service window, effective October 1, 2026.
How much does a WhatsApp service message cost?
By market, the same as a utility or authentication message. Meta's documentation states that rates for service messages are the same as the rates for utility and authentication messages, and that service messages have no volume tiers.
Is there really a free allowance of 1,000 messages per month?
It's reported by several platforms but not confirmed anywhere in Meta's own documentation. Don't plan your budget around it until you see it reflected on your own account's billing.
Does this affect the regular WhatsApp Business app?
No. This change applies to the WhatsApp Business Platform (the API used by chatbot and CRM platforms), not the free consumer WhatsApp Business mobile app.
Will this make my chatbot more expensive to run?
It depends on how many free-form replies it sends inside the 24-hour window. A bot that sends several short messages per conversation will feel this more than one that answers concisely in a single message.
What should I do right now?
Make sure a payment method is on file for your WhatsApp Business Account, check last month's message volume as a baseline, and read your first October invoice line by line once it arrives.