Your WhatsApp bill, explained: conversations, categories, and the 24-hour clock

WhatsApp pricing in October 2026: what actually changes

Meta already replaced conversation-based billing with per-template-message pricing on July 1, 2025. October 2026 extends charging to messages that previously qualified for free delivery. It does not introduce per-message billing for the first time.

Starting October 1, ordinary non-template service replies become chargeable, including responses from human agents, bots, and third-party automation. Utility templates delivered inside an open customer service window also become chargeable. Twilio’s October notice specifies an allowance of 1,000 free service messages per business phone number per month; provider fees can still apply.

For budgeting, count the outbound messages your team delivers, not just the customers it serves. One resolved ticket might involve two replies. Another might involve twelve. Those exchanges no longer have the same potential messaging cost.

The 24-hour customer service window still exists

A customer message opens or refreshes a service window lasting 24 hours from that customer’s most recent message. During that period, your business can send non-template replies. Your own outbound messages do not restart the timer.

For example, a customer writes on Monday at 10 a.m. Your agent replies at 4 p.m. The window still expires on Tuesday at 10 a.m. If the customer writes again on Monday at 6 p.m., it extends until Tuesday at 6 p.m.

Outside the window, you need an approved template to message the customer. Sending that template does not itself reopen permission for free-form replies; a customer response does. From October, staying inside the window preserves that flexibility but no longer guarantees free service replies.

Which WhatsApp message category are you paying for?

Marketing templates cover promotions and commercial outreach. Utility templates cover qualifying transaction-related updates, such as order confirmations. Authentication templates deliver verification codes. Service messages are ordinary non-template responses from your team or third-party automation. Meta Business Agent responses have their own pricing category.

Check the category actually assigned to a template. An order update containing a discount offer can be treated differently from a purely transactional notification. Renaming a template in your inbox does not change Meta’s classification.

Each delivered message is assessed under its applicable category. A marketing template does not make every subsequent message in the thread a marketing charge, and an earlier utility message does not include unlimited later updates. Review template categorization whenever you change the content or Meta updates its classification.

What remains free after October 1?

Customer-to-business messages remain free of Meta messaging charges. Separately, Twilio’s October notice documents the monthly allowance of 1,000 service messages per business number. That allowance concerns service messages, not a blanket exemption for all message categories.

Eligible Click-to-WhatsApp ads and Facebook Page call-to-action buttons can open a 72-hour free-entry-point window when your business responds within 24 hours. The 72 hours begin with that response. An ordinary website link or QR code should not be assumed to qualify.

The free-entry window concerns delivery charges; the separate 24-hour service window still governs non-template sending. Advertising spend and provider fees remain separate, and Meta Business Agent token usage is not waived by the free-entry window.

Meta Business Agent pricing is different from ordinary chatbot pricing

Since August 1, 2026, Meta Business Agent has used a global rate of US$2 per million tokens, covering input processing and response generation. Meta applies one charge for its agent message, including delivery; it does not also apply a service-message charge to that same response.

At that rate, an illustrative response consuming 25,000 billable tokens costs $0.05. Ten thousand such responses would cost $500 before separate provider charges or taxes. This is a calculation, not a prediction of your token usage.

A third-party support bot follows a different cost structure: its outbound non-template replies fall under service messaging, while its AI supplier may charge separately. Compare complete costs rather than comparing one vendor’s AI-only price with another vendor’s combined AI-and-delivery price.

How much does a WhatsApp message cost in your market?

Rates depend on the recipient’s country calling code, message category, billing currency, and applicable volume tier. Use the rate card effective on the delivery date. Utility and authentication messages have volume tiers; service messages do not.

October also brings announced market changes affecting Bangladesh, Iraq, Nepal, Sri Lanka, Kazakhstan, Kuwait, Morocco, Oman, and Ukraine. Check their individual rate-card entries instead of carrying forward an older regional rate.

Avoid budgeting from a table that merely says ‘2026 pricing.’ A July rate card and an October rate card can produce different forecasts. Record the effective date beside every rate in your spreadsheet, and separate standard authentication from authentication-international pricing where applicable.

A simple WhatsApp pricing example you can adapt

Here is a hypothetical monthly budget for one business phone number. Assume 12,000 delivered service messages, all outside free-entry-point windows, with the documented 1,000-message allowance available. That leaves 11,000 chargeable service messages. At an invented planning rate of $0.01 each, the service subtotal is $110.

Now add 3,000 chargeable utility messages at an illustrative $0.01 each and 1,000 chargeable marketing messages at an illustrative $0.05 each. Those add $30 and $50, bringing the Meta messaging subtotal to $190. These rates are examples, not published prices for any country.

If your software subscription is $99 and separate AI usage costs $20, the example reaches $309 before taxes, additional provider fees, or other services. Substitute your actual rates and volumes, applying each exemption or allowance once.

For a multinational business, repeat the calculation by market and category, then add the subtotals. A single blended rate is useful for a quick estimate, but a detailed forecast shows which customers and workflows drive the bill.

Your provider’s invoice can include more than Meta charges

A WhatsApp Business Platform budget can include Meta messaging charges, provider handling fees, inbox subscriptions, agent seats, AI usage, and taxes. Not every provider charges every item. Ask which fees are included, passed through, or added separately.

For example, Twilio lists its own $0.005 handling fee for inbound and outbound WhatsApp messages, separate from applicable Meta charges. That illustrates why ‘free from Meta’ does not always mean ‘free on your invoice.’ Other providers use different commercial models.

When comparing quotes, give each supplier the same scenario: phone numbers, seats, recipient markets, inbound volume, outbound volume by category, and expected AI usage. Otherwise, a low headline subscription can conceal a higher total cost.

How to reduce WhatsApp messaging costs without weakening support

Start with unnecessary sends. A greeting, an acknowledgment, a status update, and an answer can become four separate messages even when one clear response would serve the customer. Combine related information where it improves readability, while keeping timely acknowledgments when customers need them.

For example, replace three consecutive bubbles saying ‘I checked your order,’ ‘It ships tomorrow,’ and ‘Here is your tracking link’ with one helpful update. If this removes two chargeable messages across 5,000 exchanges, it avoids 10,000 sends. At a hypothetical $0.01 per message, that is $100.

Improve routing before adding more automation. Pass the customer’s issue, order details, and previous answers to the person taking over. That can prevent repeated questions and duplicate replies. Merging inbox threads alone does not alter Meta’s billing.

Measure cost per resolved issue alongside customer satisfaction and repeat-contact rates. A short reply that forces three follow-ups may be more expensive than a complete answer. A bot that responds instantly but repeatedly misunderstands the request can increase both messaging costs and customer effort.

A practical audit before your first October invoice

Export a recent month of delivered messages and separate service, utility, authentication, marketing, and Meta Business Agent usage. Use message and pricing analytics rather than treating every inbox thread as a billing unit.

For each business number, identify eligible free-entry traffic and the applicable service allowance. Match chargeable deliveries to the correct market, category, effective rate, and any eligible volume tier. Reconcile provider charges separately.

Then inspect the workflows with the most outbound messages per resolved request. Look for duplicate notifications, unnecessary follow-ups, repeated questions after handoffs, and templates whose assigned category differs from your expectation.

Give someone ownership of this report. Track delivered messages, total channel cost, resolved issues, and customer outcomes each month. That turns WhatsApp pricing from an invoice surprise into an operational decision your team can manage.