WhatsApp Service Replies After 1 October 2026: Costs and Trade-offs

What changed on 1 October 2026

Until September 2026, a business could answer a customer's message inside the 24-hour customer service window without paying Meta for that reply. Meta's own developer notice now says it will charge on a per-message basis for all service messages from 1 October 2026, in the same way it charges for template messages. Utility messages sent in response to users inside an open window are covered by the same change. Incoming messages from customers stay free.

The change comes with a free monthly allowance. Meta's current pricing page says each business phone number has one free tier of 1,000 delivered service messages per month. Guides agree on this figure, and they agree that unused messages do not carry over to the next month or to another number. The allowance is counted per number, not per company, so an account with three numbers has three allowances.

The change is a billing change, not a change to how the window works. The 24-hour window still opens when a customer writes first. What changes is that a reply sent inside it now appears on the bill once the monthly allowance for that number is used.

How to count your monthly replies

1. Pick one business phone number. Your allowance does not pool with other numbers.
2. Take one calendar month of outbound messages, not a rolling 30-day window. One guide that works through the calculation specifically recommends the calendar month for this reason.
3. Keep only the messages that were delivered. Meta bills delivered messages, not send attempts, so failed deliveries should be left out of the count.
4. Separate free-form replies from utility templates sent inside the window. Both are billable from October, but they sit in different rows of the rate card.
5. Subtract 1,000 from the count of service messages. Multiply the remainder by the rate for each recipient's country.

Here is a worked example using the India figure from the 2026 rate guides. Suppose one number delivers 5,000 service replies in a month. The first 1,000 are free. The remaining 4,000 at ₹0.115 each come to ₹460 before any local indirect tax. India's GST (goods and services tax) is added on top of Meta's rate, so the invoice total will be higher. If the same number also sent 1,000 utility messages inside the window, those would be billed at the utility rate, which the same guides list as ₹0.115, so the month would total about ₹575 before tax. The result depends entirely on the volume your own number delivers, and the free audit measures that from your own records.

Nigeria shows why the rate itself needs checking. Vanguard's August 2026 report puts a utility message at about $0.0101 for Nigerian numbers. A ChatMaxima 2026 table, however, lists $0.0067 for Nigeria, and says it is based on Meta's October USD card. The two figures disagree. Until the rate is checked against Meta's rate card, neither should go into a budget.

Comparison: service replies before and after 1 October 2026

The table reflects what the 2026 sources and Meta's documentation state. Where the source set does not give a figure or a name, the cell points to the vendor's current documentation rather than offering an estimate.

Who each option suits

Staying on the WhatsApp Business Platform after October makes sense when customer conversations already run through WhatsApp and the reply volume is known. A business with a steady, measured flow of replies can budget the cost per delivered message, and can compare it with what the same conversations cost in staff time and in other channels.

The standard WhatsApp Business app is a different product. Vanguard notes that regular users and small businesses on the standard app are not the main targets of the new charges. A business that answers a handful of customers a week on the standard app should not assume the Platform rules apply to it, but should confirm which product its account uses before planning a budget.

A business that cannot yet tell how many replies it sends should not sign up for a volume plan. It should count first, for one full calendar month, and then decide. Counting is the cheapest step in this whole decision.

Total cost drivers beyond the per-message rate

• Setup time. The business must link its number, confirm its payment method and set up how replies are logged.
• Maintenance. Rates change by market and by date. The India rate in 2026 guides was set alongside changes to marketing rates, so the rate card needs a periodic check.
• Payment lapses. Meta's pricing page says that without a payment method, delivery stops once the free tier is used. A lapse can stop customer replies in the middle of a busy month.
• Breakage. A reply that is sent to the wrong customer or repeated by a worker still counts as a billable message.
• Tax and invoicing. Local indirect taxes can be added to Meta's rate. The business's accountant should confirm how these appear on its invoices.
• Lock-in. Message history, attribution and reporting sit inside the Platform. A later move to another channel means exporting records and rebuilding the reporting.

The custom-built alternative

A custom-built system is software a company or developer builds to handle its own replies, usually connected to its order, billing or ticket records. It does not avoid Meta's fees. Any message sent through the Platform is still billed. What a custom build changes is who maintains the rules, the logs and the reports.

A custom build wins when the replies must be tied closely to the business's own records, such as invoices, ledgers or order status, and when the volume justifies the cost of building and maintaining it. It loses when the volume is modest, when the team has no one to maintain it, or when a provider's standard tools already cover the need. Build cost and upkeep vary widely, and no source in this review gives a reliable figure for them, so the decision should be made from the business's own quotes.

Where a reply worker still needs a person

A reply worker can draft and send routine answers, such as order status, appointment confirmations and standard policy questions, and log each one against the number it was sent from. It can also count the month's billable replies and warn the owner when a number is close to 1,000. What it cannot do is decide what is fair to a customer. A person should approve refunds, complaints, disputes, any reply that promises a date or amount, and any message to a customer who has asked to stop. The worker is built to follow the rules it is given. It does not change Meta's rules, and it does not replace the owner's judgment on exceptions. Results depend on the business's own volumes, which the free audit measures.

Migration notes for the next weeks

1. Confirm the payment method in Meta's Billing Hub now. The deadline in Meta's notice was 30 September 2026, and that date has passed.
2. Count the outbound replies for each business phone number for the last full calendar month.
3. Check each recipient country's rate against Meta's current rate card, not against a guide.
4. Decide, for each number, whether its volume justifies staying on the Platform or moving some conversations elsewhere.
5. Record which messaging account each message is sent from, because Meta attributes messages and charges to the account they were sent from.

Two sources disagree on what happens to a number with no payment method. Meta's pricing page says delivery continues within the 1,000 free messages but not beyond them. Respond.io's 2026 guide says accounts without a payment method still receive the full 1,000. Spur's 2026 guide says Meta stops delivering service messages from 1 October for accounts without a payment method. The Meta page is the primary text, so it should be the reference, and the business should confirm its own account status in Billing Hub.