If your business answers customers on WhatsApp through software — a helpdesk, a CRM, a chatbot, an order-tracking system — the replies your team sends have been free since November 2024. On 1 October 2026 that ends. Meta will charge for every service message after the first 1,000 a month per phone number, at a rate set by the customer's country, and on the same day Pakistan's rate goes up by half. Most coverage so far comes from companies that resell WhatsApp access and stops at "prices are changing". This article goes to Meta's own rate card, works out what a month of replies will cost in the markets our readers sell into, and sets out what to do in the twenty days left.
What Changes on 1 October, in Meta's Own Words
The change is documented on Meta's developer site, not in a press release, which is why it has had less attention than it deserves. The operative sentence: "Effective October 1, 2026 - Meta will charge on a per-message basis for all service messages, consistent with how Meta charges for template messages. These messages have not been charged since November 1, 2024."
Some vocabulary, because the whole cost model turns on it:
- A service message is any free-form reply sent inside the 24-hour window that opens when a customer messages first. A person typing, a helpdesk agent, a third-party AI bot — all service messages. They can only respond, never reach out.
- A template message is a pre-approved message a business can send at any time. Marketing, utility (order confirmations, delivery updates) and authentication (one-time codes) are the three categories, and they have always been charged.
- Only delivered messages from the business are charged. What the customer sends you is free, as it always has been.
Three things change at once on 1 October. Service messages become chargeable. Utility templates sent inside an open window — the confirmation sent while the customer is still chatting — become chargeable too; they have been free since July 2025. And the quarterly rate card update lands the same day, with increases in several markets this blog is read from.
The Free Tier: 1,000 Messages a Number, Which Is Smaller Than It Sounds
Meta added a free allowance to the plan, and it is the detail that decides whether this touches you at all: "Every business phone number will receive 1,000 free service messages per month. Meta will only charge as of the 1,001st service message delivered each month." The allowance is per phone number, it resets monthly, and it does not roll over.
A thousand a month is about 33 replies a day. A clinic handling fifteen enquiries a day, two messages each, sits inside the allowance and pays nothing. A retailer whose catalogue bot answers two hundred conversations a day, four or five messages each, burns through it by the second morning of the month. The free tier is sized for a small business run by people, not for automation.
There is a harder edge to it. If a number has no payment method on file, Meta will deliver the first 1,000 service messages of the month and then stop. Not queue, not warn — stop: "Meta will deliver your first 1,000 service messages each month but not deliver as of your 1,001st." Meta's guidance is to have a payment method in place by 30 September. If you reach WhatsApp through a provider, the provider holds that payment method, and it is worth a message to them this week to confirm it is there.
What a Reply Will Cost in Pakistan, the Gulf and the Markets You Sell Into
Meta publishes the rate card as a spreadsheet, and the rule for service messages is simple: "rates for service messages will be the same as those of utility and authentication messages, by market." The market is the customer's phone number, not your address. A Dubai company answering a +92 number pays the Pakistan rate.
Here is the rate card, in US dollars per delivered message, for the markets our readers most often message. "Today" is Meta's card effective 1 July 2026; "1 October" is the one published on 1 September. Service messages cost zero today in every row.
| Customer's market | Utility today | Service & utility from 1 Oct | Marketing today | Marketing from 1 Oct |
|---|---|---|---|---|
| Pakistan | $0.0100 | $0.0150 (+50%) | $0.0473 | $0.0473 |
| Saudi Arabia | $0.0107 | $0.0107 | $0.0501 | $0.0576 (+15%) |
| UAE | $0.0157 | $0.0157 | $0.0499 | $0.0576 (+15%) |
| Qatar | $0.0120 | $0.0120 | $0.0341 | $0.0341 |
| Kuwait (new standalone) | $0.0091 (regional) | $0.0440 (4.8x) | $0.0341 (regional) | $0.0792 (2.3x) |
| Oman (new standalone) | $0.0091 (regional) | $0.0247 (2.7x) | $0.0341 (regional) | $0.0341 |
| Rest of Middle East | $0.0091 | $0.0091 | $0.0341 | $0.0392 (+15%) |
| Egypt | $0.0036 | $0.0036 | $0.0644 | $0.0644 |
| India | $0.0014 | $0.0014 | $0.0118 | $0.0118 |
| Bangladesh (new standalone) | $0.0113 (regional) | $0.0037 (down) | $0.0732 (regional) | $0.0732 |
| United Kingdom | $0.0220 | $0.0220 | $0.0635 | $0.0635 |
| North America | $0.0034 | $0.0034 | $0.0250 | $0.0250 |
Source: Meta's USD rate cards effective 1 July 2026 and 1 October 2026, downloaded from the WhatsApp Business Platform pricing documentation on 11 September 2026. Rates are per delivered message. "Regional" means the market was billed at its "Rest of" region rate until 30 September.
Two rows deserve a second look. Kuwait and Oman have until now been billed at the Rest of Middle East rate. From 1 October they get their own line, and Kuwait's is nearly five times the regional rate. A Gulf business with a meaningful Kuwaiti customer base will see that in October's invoice whether or not anything else changes.
Pakistan's Rate Went Up Twice This Year
Pakistan is the row that matters most to many of our readers, and the increase is easy to miss because it is bundled into a wider change. Meta's rate history shows Pakistan's utility and authentication rate was already raised on 1 April 2026. The 1 October card raises it again, from $0.0100 to $0.0150. Because service messages take the utility rate, a Pakistani business is not just starting to pay for replies — it is paying at a rate 50% higher than it was in the summer.
Put a realistic month against it: one business number handling 10,000 customer replies — a busy retailer, a private hospital, a courier depot. The first 1,000 are free. The remaining 9,000 cost:
One number, 10,000 service replies in a month, from 1 October 2026
Cost of the 9,000 replies after the free 1,000, by the customer's market, at Meta's published rates
India
$12.60
Saudi Arabia
$96.30
Qatar
$108.00
Pakistan
$135.00
UAE
$141.30
United Kingdom
$198.00
Oman
$222.30
Kuwait
$396.00
Every bar is $0 today. Our arithmetic from Meta's 1 October 2026 USD rate card; it excludes any margin your messaging provider adds.
Those are Meta's figures. A provider passes them through and typically adds a margin; we have found no published figure for it we would trust enough to print, so read your contract.
Utility Templates in the Window Are No Longer Free Either
This is the change most write-ups skip, and for an operations business it may cost more than the service-message change. Since July 2025, a utility template sent while the customer had an open window — the order confirmation sent right after they ask "do you have it in stock?" — has been free. From 1 October it is charged at the utility rate like any other template.
Meta's own worked example: a customer replies to a marketing message, asks two questions, is handed to a human, and receives an order confirmation, all within an hour. Until August that was one charge, for the marketing template. From 1 October it is five: one marketing, two for the automated replies (Meta's own AI agent, charged since August), one service message from the human, one utility for the confirmation.
For a courier or an e-commerce business, the "confirm inside the conversation" trick that kept confirmations free is gone. The small mercy is that a confirmation now costs the same whenever it goes, so send it when it is useful to the customer rather than when it is cheapest.
What This Does to the Economics of a WhatsApp Chatbot
This is where the change bites hardest, because a bot that replies to every message has until now cost nothing per reply on the WhatsApp side. From 1 October a third-party bot has two costs per reply: the AI provider's charge for the answer, and Meta's delivery charge.
Meta publishes its own estimate of the first number. In its cost comparison for Brazil it puts a third-party AI reply at "~2 cents" for a lower-complexity model and "~9 cents" for a higher-complexity one, against 0.68 cents of delivery. Those AI figures are Meta's estimates, and they are in the neighbourhood of what we see running our own metered AI systems, so we will use them. Delivery is the part that now varies by market:
- India. About 2 cents of AI plus 0.14 cents delivery. The AI is almost the whole cost; the WhatsApp change is a rounding error.
- Pakistan. About 2 cents of AI plus 1.5 cents delivery, roughly 3.5 cents a reply. Delivery is now over 40% of the cost of a cheap bot reply.
- UAE. About 2 cents plus 1.57 cents. Same shape as Pakistan.
- Kuwait. About 2 cents plus 4.4 cents. Delivery costs more than double the AI, and a bot that sends four short messages where one would do pays four delivery charges for one answer.
That last point is the design change worth making before October. Bots are tuned to be conversational — a greeting, an answer, a follow-up, a sign-off — because it felt free. From 1 October every bubble is a delivered message, and collapsing four into one well-written message cuts delivery cost by three quarters without changing what the customer learns. We are making exactly that change in the WhatsApp flows on our own MCAS ticketing, where clients message a business number and the reply comes from inside the ticket.
Meta is also, since August, selling its own AI agent for WhatsApp at one global rate of $2.00 per million tokens, which it says works out at roughly 4 to 5 cents a message including delivery. Because that rate is global and delivery is not, its appeal depends on your market: in Kuwait, where delivery alone is 4.4 cents, it undercuts any third-party bot; in India, where a third-party reply lands around 2 cents, it is roughly twice the price; in Pakistan and the Gulf the two are close enough that the decision should turn on what the bot can do. That is our arithmetic from Meta's figures, and Meta itself cautions the comparison is not apples-to-apples.
From 1 October, every reply your business sends on WhatsApp is a line item, and the country code of the customer decides how big it is.
Three Things That Stay Free, and One Trap
- The 72-hour free entry point. When a customer starts a conversation from a Click to WhatsApp ad or a Facebook call-to-action button and you reply within 24 hours, Meta opens a 72-hour window in which every message you send is free for delivery. That is unchanged, and it now has real money attached: a conversation that starts from an ad is worth up to three days of free replies. If you run ads, check they use the click-to-WhatsApp objective and not a plain link.
- Messages from the customer. Never charged. Only what you send counts.
- The WhatsApp Business app. Replying from the app on a phone is not the Platform and is not affected. Neither is a "chat with us on WhatsApp" link that opens the customer's own WhatsApp pointed at your number — that is how the after-hours fallback on our AI Agent works, and it costs nothing per message because no API is involved.
- The trap: no volume discount. Utility and authentication messages have volume tiers that lower the rate as you send more in a month. Meta is explicit that service messages get none: "Meta will not offer volume tiers for service messages." Do not budget for the rate coming down as you grow, because it will not.
What to Do Before 30 September
Twenty days is enough if you start this week. In order:
- Find out how you connect. If replies go out through software — a helpdesk, a CRM, a bot, an ERP — you are on the Platform. Ask the vendor one question: "Which of our numbers have a payment method on file with Meta?" Any number without one stops delivering at its 1,001st reply in October.
- Count last month's replies per number. Meta's pricing analytics report service messages by number and by country. If every number is under 1,000 a month, the free tier covers you; confirm the payment method and stop. If not, multiply the excess by the rates above and you have October's bill.
- Split by the customer's country, not yours. A business in Lahore whose customers are in Saudi Arabia pays Saudi rates. A small Kuwaiti share can dominate the invoice.
- Shorten your bot. One good message instead of four. The cheapest fix, and it improves the customer's experience at the same time.
- Move confirmations to where they help. An in-window utility template now costs the same as one sent later, so send status updates when the customer needs them. Delivery notifications on our Courier platform were never timed around the free window, so nothing there changes.
- Decide where WhatsApp is the wrong channel. Missed-call handling is a phone problem, and an AI receptionist on the phone line is priced per call, not per message. We wrote about the trade-off in our piece on AI voice agents.
None of this makes WhatsApp a bad channel. In Pakistan and the Gulf it is still where customers are, and a reply at a cent and a half is far cheaper than a call that goes unanswered. We argued last year that automated replies were the cheapest customer service a business could run, and that is still true — it is just no longer free, and the countries you sell into now set the price. As with the AI price increases we mapped out for January, the businesses that get hurt are not the ones paying more per message. They are the ones who find out from the invoice.
If you want a second pair of eyes on your WhatsApp flows before the switch — which numbers, which countries, how many messages per conversation — talk to us. It is an hour's conversation, and October's bill is on the other side of it.