WhatsApp’s New Pricing Structure: What Will Be Charged Starting October 1, 2026
Starting October 1, 2026, Meta will begin charging for service messages and for utility templates sent in reply to a customer. And from August 1, it started charging for messages sent through its new Meta Business Agent service. Here’s a breakdown of exactly what’s changing, who it affects most, and what you can do right now so your October bill doesn’t come as a surprise.
What’s changing and when
| Date | What changes | How it’s billed |
|---|---|---|
| August 1, 2026 | Messages from Meta Business Agent — Meta’s new AI agent — become paid | By tokens: $2 per 1 million tokens, roughly 4–5 cents per message |
| October 1, 2026 | Service messages become paid — any business reply sent outside a template | Per message |
| October 1, 2026 | Utility templates sent inside an open service window become paid | Per message |
The key takeaway: starting October 1, every business reply sent inside the service window is billed — whether it’s a plain message, a utility template, or a reply from an AI agent.
Meta sets the message prices; edna simply passes them through. So as soon as these changes take effect, they’ll appear on your invoice. For details, see Meta’s documentation.
Why the free window stops being free
Under the current pricing model, when a customer messages you first, a 24-hour service window opens. Inside that window, businesses can send non-template messages for free. Since July 2025, utility templates sent within that window have been free too. Every new message from the customer resets the clock and extends the window by another 24 hours.
From October 1, the 24-hour window for replying to a customer without a template still exists — but every outgoing message sent within it will now be billed.
The only messages that will remain free are incoming messages from customers.
How much it will cost
A service message will cost equally to utility template based on the country of the recipient. From October 1, that’s also what every agent or bot reply will cost.
Example: the same conversation, before and after
Take a typical exchange: you send a broadcast, the customer replies, you handle their request, and the next day you send an order status update.
| Time | What happened | Now | From Oct 1 |
|---|---|---|---|
| 11:00 | You send a marketing template | Paid | Paid |
| 13:00 (+2h) | Customer replies — a service window opens until 13:00 the next day | Free | Free |
| 14:00 (+3h) | You reply with a plain message | Free | Paid |
| 15:00 (+4h) | You send a utility template within the window | Free | Paid |
| 17:00 next day (+30h) | You send a utility template — the window has already closed | Paid | Paid |
Who’s affected the most — and who almost isn’t
It no longer matters how you reply to a customer — with a plain message or a utility template: from October 1, both become paid. So the only thing that now separates one scenario from another is how many messages you send within a conversation.
Conversations with an agent
This is the scenario to look at first. Every agent reply becomes its own line item on the invoice: if an agent sends twenty messages in a conversation, all twenty are billed. Customer messages remain free.
Chatbots with long scenarios
The more clarifying questions a bot asks, the more expensive the interaction becomes. Branches that used to cost nothing will now noticeably affect the budget.
Marketing broadcasts and verification codes
Here the mechanics don’t change — these messages were already billed. If your traffic is mostly broadcasts and OTPs, the new rules will barely touch you.
What is Meta Business Agent
This is the second change.
On July 1, 2026, Meta launched the Meta Business Agent platform — its own AI agent that replies to customers on behalf of a brand. The agent draws on your knowledge base, answers questions about products and services, can pull data from your systems (order status, available appointment slots), and hands the conversation off to a human agent when it can’t help.
As of August 1, 2026, the agent became paid: $2 per 1 million tokens, which works out to roughly 4–5 cents per message. The price floats — the more complex the reply, the more tokens it consumes. A simple response costs less than a detailed consultation.
Two things worth understanding:
- Meta bills the business directly for the agent, bypassing the provider. It’s a separate invoice — not one from edna — and you’ll need to pay it yourself.
- The agent isn’t available in every country or industry yet. It is needed to check whether the service is launched in your country.
We’re continuing to test Meta Business Agent and will share results as we go. We’re also helping with setup — if you’re interested in this product, reach out to your edna account manager, contact support, or submit a request on our website.
What will change in edna Pulse
The invoice format itself isn’t changing.
Your WhatsApp summary report will now show the number of outgoing service messages and agent messages, so you can see the breakdown of your spending. Billing will follow Meta’s new rules.
What you can do right now
There are two months left until October 1 — enough time to estimate your future costs and rework your scenarios.
- Calculate your service traffic volume. Open your summary report in edna Pulse and find the “Outgoing messages / Chat messages” line — these are the non-template messages that become paid on October 1. Multiply the monthly count by your utility-template rate to see how much this will add to your bill.
- Implement WhatsApp Flows. Flows is an interactive form inside a single message. The customer moves through several screens, answers questions, picks options, and leaves their contact details — all within one message instead of a chain of five to seven. Previously this had no effect on cost; now it directly affects your bill. Flows work well for satisfaction surveys, collecting contacts and leads, appointment booking, product selection, and price calculations. Sending Flows is supported in edna Pulse; the forms themselves are built in your WhatsApp Manager account.
- Enable the WhatsApp Business App via CoExistence. A good option for companies where customers are assigned a personal account manager. CoExistence lets you use a single number simultaneously in the WhatsApp Business app and in edna Pulse. When a manager messages a customer from their own device using the app, Meta doesn’t bill those messages. Conversations and contacts still sync with edna Pulse — chats remain visible in the platform, and contacts land in the Audience section. Note: messages sent from edna Pulse itself — from conversations, broadcasts, or the API — will still be billed at Meta’s rates. But for quick questions managers handle on the go, replying from the app will be more cost-effective.
- Cut unnecessary messages from conversations. Review your service scenarios: “Thanks for reaching out,” “Anything else I can help with?”, “Have a great day” — each of these now costs money. Wherever three messages can be merged into one, merge them.
- Check which notifications you actually need. Some reminders are never opened; others duplicate information the customer already saw in the app or on your website. An unnecessary message used to cost nothing — now it does.
Link buttons can help you understand which messages customers actually use. If you send order-status updates with a tracking link, or payment reminders with a link to an invoice, turn on click tracking — edna Pulse will show click statistics in both broadcast details and the message report.
Look at the statistics as a whole: a customer might read “your order has shipped,” get the information they needed, and simply not click the link. Review clicks alongside read rates together — together they give an honest picture of which messages are working and which can be dropped.
The bottom line
From October 1, 2026, there will be almost no free outgoing WhatsApp messages left. For companies with active support teams and long conversations, that means a noticeable rise in costs.
The good news is there’s still time before the changes take effect. Calculate your current service traffic volume, move multi-step scenarios to Flows, set up CoExistence for personal account managers, and cut anything from your conversations that isn’t worth paying for. If you need help with calculations or setup, reach out to your edna account manager.
