WhatsApp per-message pricing: how to prepare for October 2026

You may have already heard that WhatsApp Business pricing is set to undergo an important change in 2026: a new WhatsApp per-message pricing model is coming.

For companies using WhatsApp for customer service, support, sales, notifications, or automation, October 1, 2026 is a date worth paying attention to: Meta has announced new charges that could increase the financial impact on operations with high messaging volumes.

However, this change does not mean the end of the 24-hour customer service window.

The window will continue to exist. What changes is the pricing: starting in October, service messages and certain utility messages sent within an open customer service window will be charged on a per-message basis.

It is worth remembering that Meta had already moved from conversation-based pricing to per-message pricing in July 2025. The October 2026 update expands this approach to additional scenarios.

For operations with long conversations or high customer service volumes, this makes it even more important to monitor message volume, flow design, and cost per interaction.

In this guide, we will explain what is changing, analyze the potential cost impact, and show ways to adapt your operation, including Z-API, which uses a commercial model based on instances.

What changes with WhatsApp per-message pricing?

To understand the October 2026 change, it is important to separate three different stages in the WhatsApp Business Platform pricing model.

The previous model: conversation-based pricing

In February 2022, Meta introduced the conversation-based pricing model, in which charges were associated with 24-hour conversation windows. The model was updated with new rules in June 2023.

During this period, companies could exchange multiple messages within a conversation without being charged individually for each message sent.

On November 1, 2024, service conversations — initiated by the user — became free for all businesses.

The 2025 change: per-message pricing

On July 1, 2025, Meta replaced conversation-based pricing with per-message pricing for applicable message categories.

Since then, Marketing, Utility, and Authentication template messages may be charged individually depending on the message category and market.

Service messages sent within the 24-hour customer service window, however, remained free.

What changes on October 1, 2026?

Starting October 1, 2026, Meta will begin charging per message in additional scenarios, including service messages and utility messages sent in response to users within an open customer service window.

In practice, a support conversation involving several replies from a company may generate multiple charges instead of keeping those service messages free.

The 24-hour window will still exist and will continue to determine when companies can send free-form service messages without using a template. What changes is that Meta will begin charging for those messages.

Message types and their financial impact

To calculate the impact of Meta’s pricing, it is important to understand how different message types are treated within the WhatsApp Business Platform.

Marketing messages

Marketing templates include promotional communications, offers, campaigns, and other content designed to generate demand. These messages are already charged per delivered message, with rates that vary by market.

For that reason, high-volume operations need to monitor not only conversion rates but also the cost of each campaign stage and the number of messages sent to each user.

Utility messages

Utility templates are used for communications related to user actions or transactions, such as confirmations, order updates, and reminders.

Currently, certain utility messages sent within an open customer service window may be free. Starting in October 2026, Meta has announced per-message charges for these scenarios as well.

This makes it increasingly important to review flows with multiple notifications and avoid unnecessarily fragmented messages.

Authentication messages

Authentication templates are designed for processes such as one-time passwords and identity verification.

These messages are also charged per delivered message according to the applicable rate in the recipient’s market.

For operations with high authentication volumes, resends and duplicate attempts can have a direct impact on total costs.

Service messages

Service messages are free-form messages sent during the 24-hour customer service window opened after a user interaction. Until September 30, 2026, these messages will remain free.

For support teams and chatbots handling long conversations, this is one of the most relevant changes: the more replies a company sends, the higher the cost of that interaction may become.

When do the new rules take effect?

The next stage of the pricing model takes effect on October 1, 2026. Meta has already updated its documentation to explain how service messages and certain utility messages will be charged.

For companies using the WhatsApp Business Platform at scale, now is the time to review:

• average number of messages per customer service interaction;
• number of notifications across each customer journey;
• projected costs by use case;
• flows that can be simplified without compromising the customer experience.

It is important to reinforce that per-message pricing does not begin in October 2026. Meta has already been using this model since 2025 for applicable categories; the October update expands the scenarios subject to per-message charges.

Who is likely to be most affected?

Anyone using the WhatsApp Business API as part of their communication operation will be affected.

E-commerce, logistics, and last-mile delivery

Operations that send multiple notifications throughout a single customer journey may experience a greater impact.

Order confirmation, picking and packing, shipping, route updates, and delivery are all examples of messages that should be included in the financial analysis. Under the new rules, reviewing the number of communications sent per order becomes even more important.

SaaS, fintech, and technology companies

Products that use WhatsApp as a customer service or support interface also need to pay attention to conversation length.

The more replies a company sends during a support interaction, the higher the cost of that interaction may become once the new service-message rates take effect.

Marketing and automation agencies

For agencies managing multiple clients, the change makes it more important to track messaging costs individually by account and campaign.

In high-volume models, variable costs may require adjustments to budgets, pricing strategies, and client pass-through charges.

Companies looking for greater cost predictability

The change also makes it more relevant to compare different commercial models.

With Z-API, pricing is based on each instance, with a fixed monthly fee and no additional platform charge per message. Currently, the Ultimate plan is advertised at R$99.99 per instance, while Partner plans vary depending on the contracted volume.

This makes Z-API a relevant alternative for operations that prioritize cost predictability and high messaging volumes, provided the decision also takes into account the architecture, technical requirements, and risks associated with each model.

5 strategic tips to prepare

The October 2026 change requires companies to review their costs, workflows, and how they use WhatsApp.

Tip 1: review and simplify your workflows

Analyze how many messages your chatbot or support team sends to resolve each interaction.

Whenever it makes sense, consolidate related information into a single message and remove confirmations or steps that do not add value to the conversation.

With per-message charges expanding to new scenarios in October, reducing unnecessary messages can directly lower operating costs.

Tip 2: use AI to make customer service more efficient

AI agents can help interpret user intent, retrieve information, and generate more contextual responses.

With Z-API, the MCP Server also makes it possible to expose certain WhatsApp actions as tools for AI applications. The goal should not simply be to automate more, but to resolve each request in fewer steps and with greater accuracy.

Tip 3: choose the right moment for human support

Not every request should remain with a bot. When an issue requires judgment, negotiation, or information the automation does not have, quickly routing the conversation to a person can prevent unnecessary interactions.

The same principle applies to human teams: clear and complete messages can improve the customer experience while reducing fragmentation that may now have a direct financial impact.

Tip 4: monitor costs before the bill arrives

Track message volume, cost per interaction, and the behavior of your most important workflows.

Z-API already provides an impact calculator that lets you simulate Marketing, Utility, Authentication, and Service message volumes and compare estimated costs with its per-instance subscription model.

This type of monitoring helps identify which customer journeys should be optimized before the new rules take effect.

Tip 5: compare pricing models

For high-volume operations, it is worth comparing the variable costs of the WhatsApp Business Platform with alternatives based on a fixed monthly fee per instance.

With Z-API, the platform advertises a fixed monthly fee with no additional per-message platform charge within the subscribed plan.

This can provide greater financial predictability for operations with a high number of interactions.

However, it is important to distinguish “no per-message charge from Z-API” from “unlimited messaging with no restrictions or risk.” Z-API itself recommends following appropriate WhatsApp usage patterns, managing message volume, and avoiding unwanted communications.

The main advantage, therefore, is not “sending 1 million messages without worrying,” but rather being able to increase interaction volume without having the Z-API subscription fee increase with every message sent.

Why is cost predictability becoming more important?

In customer service, reducing messages simply to save money can hurt the customer experience. The challenge is to find the right balance between efficiency, quality, and cost per interaction.

Under Meta’s new pricing model, longer conversations may result in higher costs. Z-API follows a different commercial model: plans are charged per instance and do not add their own fee based on the number of messages sent.

This can be especially relevant for high-volume operations, as long as communication continues to follow WhatsApp usage best practices. Z-API itself notes that volume, number of recipients, and messaging patterns may influence the risk of blocks or restrictions.

How can you calculate the financial impact?

A simplified projection can be calculated as follows:

Monthly cost = Marketing + Utility + Authentication + Service

Multiply the number of billable messages in each category by the corresponding rate for the market and period being analyzed. Rules and rates should always be checked against Meta’s current pricing table.

For example, if an operation sends 20,000 billable service messages per month, simply multiply that volume by the future service-message rate applicable in Brazil.

Avoid using a fixed figure until the corresponding rate is officially in effect.

Z-API vs. Official API: differences in the pricing model

Criteria	WhatsApp Business Platform	Z-API
Pricing	Per billable message according to Meta’s rules	Monthly fee per instance
Cost variation with volume	May increase based on the number of billable messages	No additional per-message platform fee
Templates	Used in the scenarios defined by Meta	Does not use the same template system
24-hour window	Continues to apply	Does not use the same commercial pricing logic
Instances/numbers	Supports multiple numbers	Model structured around instances
AI and automation	Can be integrated with AI systems	API, webhooks, and MCP Server

The comparison should take into account not only cost, but also architecture, policies, technical requirements, and risk tolerance.

October 2026 checklist

• Map your volume: count messages sent, not just conversations.
• Simulate costs: apply current rates to your main workflows.
• Review automations: eliminate redundant messages.
• Compare alternatives: evaluate the Official API and Z-API based on your own scenario.
• Monitor results: track cost per support interaction and per customer journey.

Cost predictability becomes a strategic variable

The October change makes it increasingly important to know how much each WhatsApp workflow costs your company.

For some operations, remaining on the WhatsApp Business Platform will continue to make sense. For others, especially those with high messaging volumes and a need for predictable per-instance costs, Z-API’s model may be a relevant alternative.

Currently, Z-API advertises the Ultimate plan at R$99.99 per month per instance, with no additional platform fee per message.

The point is not to choose between “paying Meta” and “having complete freedom.” It is to understand which architecture best balances cost, flexibility, risk, and the technical needs of your operation.

Want to compare the numbers in practice? Click the banner below, open our app, and simulate the impact of your current messaging volume.

FAQ: key questions about the change

1. Will the 24-hour window disappear?

No. When a user sends a message or makes a call, a 24-hour customer service window will continue to open. This window determines when the company can send free-form service messages without using a template.

The October change affects pricing, not the existence of the window.

2. Will messages received from customers be charged?

No. Meta states that messages sent by users to businesses are not charged. Applicable charges occur on messages sent by the business.

3. Will Z-API charge the new Cloud API fee?

Z-API has its own commercial model, which currently consists of a monthly fee per instance with no additional per-message platform charge.

That does not mean Z-API operates independently from the WhatsApp ecosystem: instances still use WhatsApp technologies and accounts and remain subject to the platform’s behavior and associated risks.

4. Can I use a number I already have with Z-API?

Z-API allows users to connect existing numbers and currently works with both Web and Mobile instances. Mobile instances operate as the primary device and do not require a physical smartphone or emulator.

5. What happens if I do not change anything?

Your operation will continue to be subject to the current rules and pricing of the WhatsApp Business Platform. The impact will depend on the number and type of billable messages you send.

For that reason, the practical recommendation is to simulate your costs before October and make a decision based on your actual messaging volume.