Friday, 23 October 2026 EN ES
Founder Fieldwork.

Field notes for people building companies

Growth

Re-Cost WhatsApp Support Replies Before Free In-Window Replies End

Before in-window WhatsApp service messages become billable, pull your outbound counts by country, subtract the 1,000-message allowance, and budget the new line.

Illustration: Re-Cost WhatsApp Support Replies Before Free In-Window Replies End

If you answer customers on the WhatsApp Business Platform, the support channel you priced as free gets a line item. Beginning October 1, 2026, free-form service messages sent inside the 24-hour customer service window become individually billable. From November 2024 until that change, service messages inside the window were not charged per message. The bill lands on the replies you already send. Treat it as a budgeting task: get a current count, apply a country rate, and decide whether the channel still pays for itself.

The billable change is narrow

Utility templates sent inside the same 24-hour customer service window also become individually billable on October 1, 2026. Meta will grant 1,000 free service messages each month to each WhatsApp Business Account. Service messages will not receive volume-based pricing tiers. Use the allowance as the built-in discount, and the payable count as the base for the budget.

Country rates set the bill

Meta confirmed on September 1, 2026 that a service message is priced at the utility or authentication template rate for the recipient's country. As of September 2026, SendPulse's service-message rates were $0.0098 in Brazil, $0.0024 in India, $0.0115 in Mexico, $0.0064 in the United States, and $0.0264 in the United Kingdom. For a United States-focused queue, start with the United States rate. Among the listed rates, the United Kingdom is the most expensive and India is the cheapest. The spread is wide enough that a country mix can matter. A queue with United Kingdom and India traffic will feel the difference.

When a vendor sits between you and the platform, check whether the rate you see is the platform's or the vendor's. A support team can serve customers in several countries while billing from one address, so the recipient's country drives the charge. For a queue that serves United Kingdom customers from a United States billing address, the United Kingdom rate is the one to check.

Run the re-cost before the first billable month

Do the math before the first invoice, not after. The order keeps the total clean: volume, price, allowance, payment, channel decision. For a queue mixed by country, build a small table with country, count, rate, and subtotal. Keep the table small enough to update when a rate changes. For a queue mostly in one country, the budget is a count times a rate, minus the allowance.

  • Pull the most recent outbound service-message count by country.
  • Apply the utility or authentication rate for each recipient country.
  • Subtract the monthly free service-message allowance per WhatsApp Business Account.
  • Budget the remaining messages at the country rate.
  • Confirm a payment method before the first billable month.
  • Mark a decision: consolidate replies, shift volume, or keep the channel.

Count first, because the total needs a base. Rate second, because the country list drives the total. Allowance third, because it changes the payable count. Payment before the first billable month, because the account needs a way to pay. Decision last, because the cost may change what the channel is for.

Move volume only when unit economics change

Do not move volume just because the channel now has a price. Move it when the cost changes the unit economics of support. Most replies may be short, human, and tied to a live conversation. The channel may still be worth the rate. Many replies may be status updates, confirmations, or routine follow-ups. Those may fit a templated message or another channel better. The test is simple: compare the new message cost to the support outcome it protects.

Consolidation is the conservative move. Fewer replies per conversation can lower the bill without changing where the customer talks to you. Shifting volume is the aggressive move. It can save money, but it can also break the flow of a support conversation. When you choose to shift, pick a limited test first: a country, an issue type, or a reply pattern. Then measure the cost and the customer response before you widen it.

Advertisement