Provider update

WhatsApp pricing changes on 1 October 2026.

Meta will begin charging per delivered message for service replies and utility templates inside the 24-hour customer service window. This guide separates what changes from what stays the same and gives DripTell teams a practical review checklist.

Action before 1 October
Effective
1 October 2026
Last verified
August 24, 2026
For
WhatsApp workspace owners, finance teams and operations leads
In this guide
  • Service replies become chargeable
  • In-window utility becomes chargeable
  • The 72-hour free entry window remains

01

What Meta is changing

WhatsApp Business Platform pricing is based on delivered messages. Meta says that from 1 October 2026, non-template service messages sent by a person or a third-party AI during an open 24-hour customer service window will be charged per message. Utility template messages inside that same open window will also be charged per message.

Marketing and authentication templates are already chargeable. Utility templates sent outside the customer service window are already chargeable. The recipient's country calling code determines the market rate, not the sender's office location.

02

Before and after

Use this table to identify the charging rule. It does not replace Meta's live rate card or your DripTell invoice and plan terms.

WhatsApp Business Platform delivery charging rules
Message typeThrough 30 September 2026From 1 October 2026
Customer's inbound messageNo Meta delivery chargeNo Meta delivery charge
Service reply inside the 24-hour windowFreeCharged per delivered message
Utility template inside the 24-hour windowFreeCharged per delivered message
Utility template outside the 24-hour windowChargedCharged
Marketing templateChargedCharged
Authentication templateChargedCharged
Messages in the 72-hour free entry-point windowFreeFree

03

Who should review the change

Any team that replies to WhatsApp customers or sends utility templates during the 24-hour window should review its forecast. The effect will be larger for high-volume support operations and flows that break one useful answer into many short messages.

  • Support teams sending person-written replies after a customer message.
  • Automations or third-party AI agents sending non-template service messages.
  • Order, appointment, payment or account workflows using utility templates inside the open service window.
  • Finance teams forecasting Meta pass-through charges by recipient market.

04

Estimate exposure without guessing

Start with delivered messages, not conversations, agents or contacts. Group the last representative period by recipient market and message class, then separate service messages and in-window utility templates that were previously free. Apply the current Meta utility or authentication rate for the recipient market where Meta directs, and keep marketing and free-entry traffic separate.

  1. 1

    Count delivered messages

    Use a representative period and exclude failed or undelivered attempts.

  2. 2

    Separate message classes

    Identify service, utility, marketing, authentication and free-entry traffic.

  3. 3

    Group by recipient market

    Use the customer's country calling code and Meta's current rate card.

  4. 4

    Model behavior changes

    Test whether a concise complete reply can replace several fragmented messages without reducing service quality.

05

What to review in DripTell

The goal is not to suppress useful replies. It is to remove accidental message fragmentation, make message purpose visible and give finance a reliable baseline before the effective date.

  • Review support and AI flows that send several consecutive service messages for one answer.
  • Check utility templates used after customer replies and confirm their category still matches the actual purpose.
  • Keep free-entry traffic distinguishable from ordinary customer-service-window traffic.
  • Set a weekly delivered-message and recipient-market report for the first month after the change.
  • Brief agents on clarity and completeness without encouraging them to withhold necessary information.

06

Meta Business Agent token pricing is a separate rule

Meta introduced token-based charges for its own Meta Business Agent from 1 August 2026. That token charge is separate from WhatsApp message delivery pricing. Meta classifies a response from a person or a third-party AI as a service message for the 1 October delivery rule.

Do not apply Meta Business Agent token pricing to a DripTell AI workflow unless that workflow actually uses Meta Business Agent and the account documentation says so.

07

Use the official sources for the final forecast

DripTell maintains this explanation for operational clarity. Meta is the authority for WhatsApp Business Platform pricing, categories and effective dates. Check the official documentation and rate card immediately before approving a budget or customer communication.

Primary sources

Provider terms and rates can change. These are the original sources reviewed for this guide.