Meta Platform Tracker

WhatsApp Business API Roadmap 2026: Meta Changes & Pricing Explained

Meta’s WhatsApp Business Platform is undergoing three major shifts: complete Cloud API migration (on-premises API deprecated October 2025), a transition to per-delivered-template-message billing, and native task-specific AI via the Meta Business Agent Platform. The most critical upcoming deadline is October 1, 2026, when service messages inside the 24-hour customer service window begin being charged.

As the engineering team behind Klaros (built directly on Meta's Cloud API v25.0+), we track Meta's developer changelogs continuously. This page is our live, primary-sourced tracker documenting platform changes, pricing models, and implementation requirements.

Last verified: · Next review: October 2026 · Sources: Meta Developer Docs
WhatsApp Business Platform Roadmap 2025–2026 — Meta Platform Changes Tracked by Klaros
Figure 1: Meta WhatsApp Business Platform roadmap (2025–2026) tracked from the implementation layer by Klaros.

What changed on this page

A roadmap that never says when it was wrong is not a roadmap, it is an advert. Every correction we have made to this page is listed here, including the ones where we had published the thing we later took back.

  1. Fixed the BSUID bug this page found in our own product. Writing the entry below sent us to check our webhook handling, which turned out to drop inbound messages from customers who had hidden their phone number, silently. Klaros now learns the BSUID mapping while both identifiers still arrive, and resolves later messages through it. The card says what is still not covered.
    Added WhatsApp usernames and business-scoped user IDs to the tracker. This should have been here in April, when BSUIDs started arriving in webhooks. It is the only mandatory change on the page and it was the one we were not covering.
    Added the rates we have actually been charged, per message, per market, read back from live billing rather than copied from a rate card.
    Noted that Meta's own deadline passed. Meta committed to publishing the rates effective 1 October by 1 September. As of today no service rate table has appeared, and the commitment is still written on the page that makes it.
  2. Confirmed at primary source that utility messages become billable on 1 October too, not just service messages. Almost all third-party coverage carries only the service half. The difference matters, because the standard advice given alongside it — move your replies into utility templates — routes spend into a bucket that starts billing on the same day.
  3. Downgraded the 30 September payment-method deadline to an attributed claim. We had asserted it here in nine places, including in this page's structured data. It is widely reported and may well be real, but we could not find it in Meta's own documentation, and the articles carrying it cite no Meta source. Attach a payment method regardless. What is documented is that the Meta Terms for WhatsApp Business change on 23 September 2026.

WhatsApp Business API 2025–2026 at a glance

Executive Summary

A quick-reference summary of every major platform change shipped or scheduled by Meta.

WhatsApp Service Message Charges Starting October 1, 2026

Critical Deadline

The upcoming October 1, 2026 policy change affects every business running on the WhatsApp Business API. Here is a breakdown of what changes, what will be charged, and what actions are required.

What is changing on Oct 1, 2026?

Service and utility messages become chargeable

Until September 30, 2026, non-template service messages (free-form text, media, voice notes, or Flows sent in reply to customer-initiated conversations inside the 24-hour window) are free on Meta's side, and so are utility templates delivered inside an open window. Starting October 1, 2026, Meta charges for both. In Meta's words: "Effective October 1, 2026, Meta will charge for service messages", and "Effective October 1, 2026, Meta will charge on a per-message basis for utility messages".

The utility half is the part most coverage is missing, and it matters because it removes the obvious workaround. Advice to escape service charges by moving replies into templates and Flows routes the spend into a bucket that starts being billed on the same day. From October 1 there is no free way to answer a customer inside an open window, whichever form the answer takes.

You can estimate your October exposure today. Meta prices service messages at "the same rates as utility and authentication messages" for the recipient's country, with no volume tiers, and those rates are already published. Final rates were due by September 1, 2026.

Primary Source: Meta: upcoming pricing for non-template messages ↗
Reported, not verified

The September 30 payment method deadline

Many providers, and an earlier version of this page, state that a valid payment method must be attached to your WhatsApp Business Account by September 30, 2026 or Meta will stop delivering service messages from October 1.

We checked on 2026-08-29 and could not verify it at source. The deadline does not appear in Meta's pricing documentation, in Meta's non-template message pricing page, or in Zendesk's partner announcement of the same change. The articles asserting it cite no Meta document. It may well be accurate and relayed through BSP partner communications, but we describe this page as primary-sourced, so we are not going to present it as one.

What is documented: the Meta Terms for WhatsApp Business are updated effective September 23, 2026, and an account with no valid payment method cannot be billed for messages that are now billable. Attaching one before October is prudent regardless of whether the specific deadline is real. Doing so costs nothing.

Add a payment method in Meta Business Settings ↗

Does this change affect BSP users or Cloud API users?

Both. This is a Meta platform-level billing change, not a vendor policy. Whether you connect directly to the WhatsApp Cloud API or access WhatsApp through a Business Solution Provider (BSP) like Twilio, Interakt, WATI, or Respond.io, Meta will charge for service messages starting October 1, 2026.

How does Click-to-WhatsApp (CTWA) impact service message charges?

Click-to-WhatsApp (CTWA) ads retain a major advantage: conversations initiated via a CTWA ad receive a 72-hour free messaging window (extended from the standard 24-hour service window). All messages sent within this 72-hour window — including service replies — remain free of Meta messaging charges.

The question this raises is what it costs you, and that depends on your market. We publish the per-message rates Meta actually billed us, rather than the ones Meta lists.

See the rates we were charged →

WhatsApp Business API Roadmap 2026: The Three Major Platform Shifts

In effect now

Understanding these is prerequisite to building anything on the platform today. Two are already live. One deadline lands 1 October 2026.

Shift 01 · Infrastructure

Cloud API only — no exceptions

The on-premises WhatsApp Business API was deprecated in October 2025. The WhatsApp Cloud API is now the sole supported path for any new or existing integration. It supports up to 500 messages per second and requires no local server. API Coexistence lets the same phone number run on both the WhatsApp Business App and the Cloud API simultaneously.

Effective:
Shift 02 · Billing

Per-message billing replaced conversation billing

From , Meta moved from charging per 24-hour conversation window to charging per delivered template message. From , rates are set by the recipient's country (destination-based pricing). Service messages — non-template replies within the 24-hour window — are free until .

Effective: Jul 2025 → ongoing changes
Shift 03 · AI

Native agentic AI on the platform

The Meta Business Agent Platform, launched , enables task-specific AI agents to book appointments, qualify leads, check order status, and connect to Shopify, Zendesk, or any external system via API. Since , Meta requires all WhatsApp AI to be task-specific — open-ended general-purpose bots risk losing platform access.

Effective: June 2026

The on-premises WhatsApp Business API was officially deprecated by Meta in October 2025. The WhatsApp Cloud API is now the sole supported infrastructure for all businesses, supporting up to 500 messages per second with no local server requirement.

From July 1, 2025, Meta moved from per-24-hour-conversation billing to per-delivered-template-message billing. Service messages sent within the 24-hour customer service window remain free until October 1, 2026, when they begin being charged. From January 1, 2026, rates are determined by the recipient's country (destination-based pricing), not the sender's.

The Meta Business Agent Platform launched globally on June 3, 2026. It enables task-specific AI agents to perform concrete actions — booking appointments, qualifying leads, checking order status, recommending products — by connecting to enterprise systems like Shopify and Zendesk via the Meta Business Agent Platform API. Unlike traditional rule-based WhatsApp chatbots, these agents reason across multi-turn conversations and maintain session memory.

Since January 15, 2026, Meta has required all WhatsApp AI agents to be task-specific. Open-ended, general-purpose chatbots are prohibited and risk losing platform access.

WhatsApp Business Platform Feature Tracker (2025–2026)

Meta's shipping status

Status reflects Meta's platform, not Klaros. Each card includes a Klaros implementation note. Green = shipped by Meta. Amber = rolling out. Blue = announced/upcoming.

✓ Shipped by Meta Klaros: Live

Cloud API — On-Premises Deprecated

The on-premises WhatsApp Business API is no longer supported as of October 2025. Every business running WhatsApp must now use the Cloud API. Up to 500 msg/sec. No local server. API Coexistence lets the same number run on both the Business App and the API simultaneously.

What this means in practice: Any BSP or tool still advertising "on-premises WhatsApp" is running deprecated infrastructure. Every new integration must target the Cloud API endpoints.

Klaros implementation: Klaros has been built exclusively on the WhatsApp Cloud API (v25.0+) since launch. No migration needed for Klaros users. Your WABA, your number, your billing — connected directly to Meta.
Infrastructure
✓ Shipped by Meta Klaros: Zero markup

Per-Template-Message Billing

Meta moved from a flat 24-hour conversation fee to a per-delivered-template-message model from July 1, 2025. Marketing, Utility, and Authentication templates each carry their own per-message rate, and utility templates delivered inside an open 24-hour window are free. Non-template service messages are free inside that window too. Both of those free paths close on October 1, 2026.

The practical change: You are now billed for every template that delivers, regardless of whether the customer replies. A campaign of 10,000 marketing templates = 10,000 billing events at the applicable country rate.

Destination-based rates from Jan 1, 2026: India's marketing template rate is approximately ₹0.86 per message. This figure changes — verify against Meta's current rate table →

Klaros: Our cost dashboard shows zero-markup Meta costs by template category, per campaign, and as a pre-send estimate. There is no Klaros charge on any message. Cost calculator →
Pricing
✓ Shipped by Meta Klaros: Exploring

Meta Business Agent Platform

Meta's native agentic AI platform for WhatsApp, launched June 3, 2026. Task-specific agents book appointments, qualify leads, recommend products, and check order status — connecting to your own CRM, Shopify, Zendesk, or any system via the Meta Business Agent Platform API. A new "Meta Business Agent Messages" billing category was introduced alongside it.

How it differs from chatbots: Meta Business Agents reason across multi-turn conversations, maintain session memory, and call external APIs to complete tasks — they don't just pattern-match keywords to canned responses.

The January 2026 compliance rule: Since January 15, 2026, Meta prohibits open-ended, general-purpose AI chatbots on WhatsApp. All AI must be task-specific. Non-compliant agents risk losing platform access.

Klaros: Our AI auto-reply is task-specific by design — it only answers from facts you explicitly configure, never improvises about pricing or policies, and hands off to a human on anything outside scope. Meta Business Agent Platform integration is on our exploring roadmap →
AI
✓ Shipped by Meta Klaros: Attribution live

CTWA 72-Hour Free Messaging Window

When a customer initiates a conversation via a Click-to-WhatsApp (CTWA) ad, businesses get a 72-hour free messaging window — three times the standard 24-hour service window. All messages in this window are free regardless of type.

Why this matters more in 2026: As service messages start being charged from October 2026, the CTWA free window becomes a significant cost advantage. 72 hours of free non-template messaging after an ad conversion is a primary lever for performance marketing teams.

Klaros: CTWA ad referral capture (ad source, campaign ID) is live. Every CTWA-originated thread shows a "From ad" context chip. CTWA rollup analytics — cost-per-conversation from ad spend through to reply — is in active development. Roadmap →
Ads
✓ Shipped by Meta Klaros: 15 pre-built flows

WhatsApp Flows

Meta's native in-chat structured interaction layer. Calendar pickers, multi-step forms, appointment booking, lead capture, feedback — all without the customer leaving WhatsApp. The preferred method for structured data collection in 2026, complementing agentic AI for unstructured inputs.

The 2026 architecture pattern: Flows handle the 80% of inputs that are predictably structured (booking, order detail, registration). AI extraction — voice notes, photos, documents — handles the unstructured 20%. Together they cover the full operational surface.

Klaros: 15 pre-built Flow blueprints across 8 solution packs. Full Flows lifecycle (create, upload JSON, publish, deprecate), blueprint deployment, completion actions (tag, enroll, branch by field value). See the Flow library →
UX
Rolling out Klaros: Monitoring

WhatsApp Business Calling API

Voice calls within the WhatsApp thread. User-initiated calls are free on Meta's side; business-initiated calls require prior customer consent and are billed by duration. Calls surface within the same thread as text messages — full interaction history in one place.

Capabilities: WebRTC-based (SIP available for enterprise setups). Branded caller ID. Call deflection (voice → chat). Routing to AI agent or human agent. Agentic handoff is supported — route an incoming call to an AI agent or to a live person with full context.

Access requirements: Currently gated to accounts with high message volume (approximately 2,000+ conversations per rolling 24-hour period) and active whatsapp_business_messaging permissions.

Klaros: Monitoring for general availability. This is a hardware/telephony integration that requires specialized infrastructure. Not in current build scope.
Voice
Rolling out Klaros: Watching

Marketing Messages Lite (MM Lite)

AI-optimized delivery timing and template pacing for marketing messages. Instead of delivering at your scheduled time, Meta's system determines the optimal delivery window to maximize engagement and reduce opt-outs.

How it differs from standard broadcast: Standard sends deliver immediately at your scheduled time. MM Lite asks Meta's delivery AI to find the right moment within a window you configure.

Klaros: Our broadcast engine handles rate-limit-aware scheduling and staggered retry. MM Lite integration depends on stable API availability from Meta. Watching for general release.
Marketing
⚠ Deadline: 1 Oct 2026 Klaros: Dashboard shows it

Service and Utility Billing Starts — Action Required

From , Meta begins charging for service messages, the non-template replies your team sends inside the 24-hour customer service window, and for utility templates sent inside an open window, which were free under the July 2025 per-message model. Both were previously free. From that date there is no free way to reply inside an open window.

What this changes: Every reply your team sends in an active WhatsApp service conversation becomes a billing event, whether it is free-form or a utility template. Meta prices service messages at the same rate as utility and authentication messages for the recipient's country, with no volume tiers, which means you can estimate your exposure from rates that are already published. Primary source: Meta: upcoming pricing for non-template messages →

Still free: inbound messages from customers, and everything inside the 72-hour free entry point window opened by a Click-to-WhatsApp ad or a Page CTA.

On the September 30 payment method deadline: widely reported, and we reported it here too, but we could not verify it in Meta's own documentation on 2026-08-29. Treat it as a provider-relayed claim rather than a documented one, and attach a payment method anyway. What is documented is that the Meta Terms for WhatsApp Business change on September 23, 2026.

Klaros: Our cost dashboard already categorizes service vs. template messages. Because we pass Meta's rates at zero markup, you'll see the exact service message charge with nothing added on top the moment Meta activates it.
Pricing · Deadline
✓ Shipped by Meta

API Coexistence

The same phone number can now be used on both the standard WhatsApp Business App and the Cloud API simultaneously. This enables a smoother transition for growing businesses that want to pilot the API without disconnecting their existing Business App setup.

Practical impact: A business can take WhatsApp messages via the App (for simple conversations) and via the Cloud API (for automated workflows and CRM integration) using the same number. This was not possible prior to 2025.

Klaros: Because Klaros connects to the Cloud API, you can use it alongside the WhatsApp Business App on the same number during an evaluation period before fully migrating.
Infrastructure
✓ Shipped by Meta Mandatory Klaros: partial

WhatsApp Usernames and Business-Scoped User IDs (BSUID)

WhatsApp is separating a customer's identity from their phone number. Users can adopt a username and hide their number from businesses they message. In its place, Meta issues a business-scoped user ID: a per-business identifier, so the same person has a different BSUID for every business they talk to and no two businesses can correlate them. BSUIDs started appearing in webhooks in April 2026, and Meta's APIs have accepted them as a send target since July 2026. Meta states that supporting them is mandatory for partners, directly-integrated businesses, and Click-to-WhatsApp advertisers.

The detail most write-ups get wrong. Several summaries say the phone number is "replaced by" a BSUID in the webhook. Meta's documentation says something materially different: when the number cannot be included, messages[].from and contacts[].wa_id are omitted. The identifiers arrive in new fields, from_user_id and user_id.

That distinction decides how your integration fails. If the field were replaced, code reading msg.from would get a strange-looking string and probably create an odd contact. Because the field is absent, that same code gets undefined — and whatever it does next, it does silently. A phone normaliser hands back nothing, a contact lookup misses, and an inbound message from a real customer lands nowhere, with no error raised. It is the quietest possible failure mode for the most important message you get.

The format: the user's ISO 3166 alpha-2 country code, a period, then up to 128 alphanumeric characters, for example US.13491208655302741918. Anything storing a WhatsApp identity in a column sized for an E.164 phone number is too small for it.

If you genuinely need the phone number — to send an OTP to it, say — you have to ask the customer to share it inside the conversation. There is no lookup from a BSUID back to a number, and that is the point of the design rather than a gap in it.

Klaros: we are flagging this one harder than the rest of the tracker because we failed it ourselves. Identity in most WhatsApp CRMs is keyed on the phone number, since for a decade the phone number was the only identity WhatsApp had. Ours was too, and our inbound consumer opened with the equivalent of if (!from) return — so a customer who had hidden their number was acknowledged to Meta and then dropped, with nothing logged.

What we ship today, stated precisely because a vague status here would be worth nothing: we record a sender's BSUID against their contact whenever Meta sends the phone number and the BSUID together, which is what happens while the customer still shows their number. That overlap is the only chance to learn the mapping, and it is why this could not wait for a tidier design: a contact we fail to map now becomes an unrecognisable stranger the day they switch a username on, and nothing Meta exposes lets us reconstruct it afterwards. A message that then arrives with no phone number is resolved back to that contact and handled normally.

What we do not do yet: a BSUID-only message from someone we have never seen cannot become a contact, because every downstream surface — conversation keying, country inference, consent, outbound — is still phone-keyed, and threading an empty phone number through all of it would trade a visible gap for an invisible one. Those messages are captured verbatim and logged. That is a real limitation and we would rather write it down than round it up.

If you run your own integration, the audit is cheap and worth doing before usernames reach your customers: find every place you read from or wa_id off a webhook, and decide what each one does when the field is absent rather than empty. In ours the sender identity is read in the webhook route, the coexistence echo handler and the queue consumer, and it was the consumer that threw messages away.
Identity

WhatsApp Business API Roadmap Timeline (2025–2026)

Key dates

The exact sequence of Meta's platform changes, with the forward-looking deadline.

Per-template-message billing begins

Meta replaces 24-hour conversation windows with per-delivered-template-message pricing for Marketing, Utility, and Authentication templates.

On-premises API officially deprecated

WhatsApp Cloud API becomes the only supported infrastructure. All businesses must migrate or have already migrated.

Destination-based pricing takes effect

Message rates now depend on the recipient's country, not the sender's. India, Brazil, Indonesia, and other high-volume markets each have their own rate table.

Task-specific AI mandate enforced

Meta begins enforcing the requirement that all WhatsApp AI agents be task-specific. Open-ended general-purpose chatbots risk losing access.

Meta Business Agent Platform launches globally

Native task-specific AI agents on WhatsApp. New "Meta Business Agent Messages" billing category introduced. Third-party AI integrations via the Meta Business Agent Platform API.

— Terms change

Meta Terms for WhatsApp Business updated

Revised platform terms take effect, one week before the billing change. Payment obligations live here rather than in the pricing documentation.

— Reported

Payment method deadline (provider-reported)

Many providers say a valid payment method must be on file by this date or Meta stops delivering service messages. Not stated in Meta's published documentation as of 2026-08-29. Attach one regardless.

— Upcoming

Service and utility message billing begins

Non-template replies within the 24-hour service window begin being charged, and utility templates inside an open window lose their free status on the same date. Priced at the utility and authentication rate for the recipient country, no volume tiers. Affects all service conversations regardless of platform or BSP.

WhatsApp API Pricing & Billing Changes (2025–2026)

Before/after across all message types. The October 2026 column is what's coming.

Before October 1, 2026: attach a valid payment method to your WhatsApp Business Account. Providers widely report a hard September 30 deadline after which Meta stops delivering service messages; we could not verify that date in Meta's own documentation on 2026-08-29, so we no longer state it as fact. The underlying point stands either way: from October 1 your replies are billable, and an account Meta cannot bill is an account with a problem. Add a payment method in Meta Business Settings →

Destination-based rates (from January 1, 2026): WhatsApp charges based on the recipient's country, not the sender's. India's marketing template rate is approximately ₹0.86 per delivered message (as of August 2026). Rates change — always verify against Meta's published rate table → The most important principle: the business that initiates the conversation pays. Replying to a customer who messaged you first is cheaper than starting a conversation.

What Meta actually charged us, per message

The tables above describe how Meta says billing works. This one is different in kind: every figure below was read back from real billing on a live WhatsApp Business Account through Meta's pricing_analytics endpoint, cross-checked across multiple days until each cell returned one consistent unit price. They are not list prices copied off a documentation page.

We publish them because the gap between a published rate and a billed rate is exactly where cost surprises live, and almost nobody shows the billed side.

Last re-verified against live billing on . We re-check at least every 90 days.

How we can price the October service column before Meta publishes it. Meta committed to announcing the rates taking effect on 1 October 2026 by 1 September 2026. That date has passed without a service rate table appearing. But the number is already determined, because the same page states the rule: by market, rates for service messages are the same as the rates for utility and authentication messages. So the October service rate for a market is that market's utility rate, which we have measured. Cells marked derived follow that rule rather than an observation, and we will replace them with observed figures once October billing data exists.

Every figure is in INR, including the rows for the UK and Canada. This surprises people, and it is not a mistake in our table: Meta bills the WABA's own account currency no matter where the message lands. A UK recipient on an INR-denominated account is charged in INR. If you are modelling costs off a rate card denominated in the destination's currency, you are modelling a different bill from the one you will receive.

A cell reading not observed means we have never sent that category to that market on this account. We leave it empty rather than filling it with a neighbouring country's rate, because an interpolated rate and a measured one look identical once they are in a table, and only one of them is true.

And if your market is not in the table. Four markets is what one company's billing can honestly support, so this is a sample rather than a rate card for the world. If yours is missing, the rule still gives you the answer: your October service rate is your market's current utility rate, which your own Meta billing already shows you. What we will not do is print a number for a market we have not sent to. Every other page covering this change is quoting Meta's list price; the whole reason to read this table is that these are not list prices.

What this does to your bill depends on how many replies you send inside an open window, which is the number almost nobody tracks. The calculator runs on this same rate card.

Work out your October cost →

How Klaros implements Meta's platform direction

Klaros doesn't wait for a BSP to integrate an API change. We connect directly to the WhatsApp Cloud API on your own Cloudflare account — so every Meta update is available as soon as it ships.

Zero markup on every Meta pricing change

When Meta changes rates — per-message, destination-based, new categories — you see the exact change in the Klaros cost dashboard. No BSP fee added on top. Our codebase has markup: 0. See the cost comparison →

Task-specific AI — Meta-compliant by design

Since January 2026, Meta requires task-specific AI agents. Klaros's AI auto-reply only answers from facts you explicitly configure, cannot improvise, and hands off to a human on anything outside scope. Off by default. See AI roadmap →

WhatsApp Flows — 15 pre-built blueprints

Full Flows lifecycle management, blueprint deployment, completion-action branching, and flow-response parsing. Used across the vertical solution packs. See the Flow library →

CTWA attribution live

Click-to-WhatsApp ad source, campaign ID, and "From ad" context chip in every thread. The 72-hour free window is tracked and surfaced in cost reporting. CTWA rollup analytics (cost-per-conversation) in development. Roadmap →

October 2026 billing, zero surprise

Our cost dashboard already separates service messages from template messages by category. When Meta starts charging in October 2026, the charge appears in your dashboard at Meta's exact rate with nothing added. The dashboard copy that called in-window replies free is date-gated as of 2026-08-29, so it stops saying so on the day it stops being true rather than whenever we next notice. Cost calculator →

Your WABA, your billing, your data

You connect your own WhatsApp Business Account and pay Meta directly. Klaros is never in the payment path. Your data lives in your own Cloudflare account. Full export at any time. No lock-in. Deployment model →

Frequently asked questions

What is the WhatsApp Business API roadmap for 2026?

Meta's 2026 WhatsApp Business Platform roadmap has three pillars:

1. Cloud API only — the on-premises API was deprecated in October 2025. Every business must now use the Cloud API.

2. Per-message billing — from July 1, 2025, billing moved from per-24-hour-conversation to per-delivered-template-message. Destination-based rates (by recipient country) took effect January 1, 2026.

3. Native agentic AI — the Meta Business Agent Platform launched June 3, 2026, enabling task-specific AI agents on WhatsApp. A new billing category for these agents was introduced alongside it.

What is the Meta Business Agent and how is it different from a WhatsApp chatbot?

The Meta Business Agent, launched globally on June 3, 2026, is a task-specific AI platform that performs concrete actions — booking appointments, qualifying leads, checking order status, recommending products — by connecting to enterprise systems like Shopify and Zendesk via the Meta Business Agent Platform API.

Unlike traditional rule-based WhatsApp chatbots that pattern-match keywords to canned responses, Meta Business Agents reason across multi-turn conversations, maintain session memory, and call external APIs to complete tasks.

Since January 15, 2026, Meta prohibits open-ended, general-purpose AI on WhatsApp. All AI must be task-specific. Non-compliant agents risk losing platform access.

How did WhatsApp pricing change in 2025 and 2026?

Two major changes:

Per-message billing (July 1, 2025): Meta moved from charging per 24-hour conversation window to charging per delivered template message. Marketing, Utility, and Authentication templates each carry a per-message rate.

Destination-based rates (January 1, 2026): Rates are now determined by the recipient's country, not the sender's country. India, Brazil, and other markets each have their own rate table.

Service and utility messages (October 1, 2026): service messages (non-template replies within the 24-hour customer service window) remain free until October 1, 2026, when they begin being charged. Utility templates sent inside an open window lose their free status on the same date, so no free reply path remains. Meta prices service messages at the same rate as utility and authentication messages for the recipient country, with no volume tiers. Click-to-WhatsApp ad-triggered conversations retain a 72-hour free messaging window, and inbound messages from customers stay free.

What is the October 2026 WhatsApp deadline and what do I need to do?

Three things happen around October 1, 2026:

Terms update (Sep 23): the Meta Terms for WhatsApp Business are updated, effective September 23, 2026.

Payment method (Sep 30, reported): providers widely report that a valid payment method must be on file by September 30, 2026 or Meta stops delivering service messages. We could not verify this date in Meta's published documentation on 2026-08-29, so we present it as a provider-relayed claim. Attaching a payment method before October is sensible regardless.

Service and utility billing begins (Oct 1): non-template messages your team sends within the 24-hour customer service window begin being charged, and utility templates inside an open window become chargeable on the same date. Both were previously free. Service messages are priced at the same rate as utility and authentication messages for the recipient country, with no volume tiers.

This affects all businesses regardless of which platform, BSP, or tool they use. It is a Meta platform-level change, not a vendor policy.

What is the WhatsApp Business Calling API?

The WhatsApp Business Calling API allows businesses to integrate voice calling directly within WhatsApp conversation threads, without the customer leaving the app.

It supports user-initiated calls (free on Meta's side) and business-initiated calls (requires prior customer consent, billed by call duration). Calls can be routed to a human agent or an AI agent, with agentic handoff supported.

Access is currently gated to high-volume accounts (approximately 2,000+ conversations per rolling 24-hour period) with appropriate messaging permissions.

How does Klaros implement WhatsApp's Cloud API compared to using a BSP?

Klaros connects directly to the WhatsApp Cloud API (v25.0+) on your own Cloudflare account and your own WhatsApp Business Account (WABA). You pay Meta directly at their published rates — there is no BSP markup on any message.

Because there's no intermediary between your WABA and the Cloud API, every Meta update is available to Klaros users without waiting for a BSP to integrate it. The Klaros engineering team tracks Meta's developer changelog and ships compatibility updates within weeks of any API change.

A BSP (Business Solution Provider) typically hosts your WhatsApp account on their infrastructure, charges a per-message or per-conversation markup on top of Meta's rate, and may introduce a delay between Meta releasing an API feature and you being able to use it.

What is a WhatsApp Business-Scoped User ID (BSUID) and what breaks without it?

A BSUID is a per-business identifier for a WhatsApp user. It exists so a customer who adopts a WhatsApp username can message you without revealing their phone number. The same person gets a different BSUID from every business they talk to, so two businesses cannot compare notes and work out they are the same customer.

They have been arriving in webhooks since April 2026, Meta's APIs have accepted them as a send target since July 2026, and Meta states that supporting them is mandatory for partners, directly-integrated businesses and Click-to-WhatsApp advertisers.

The detail worth getting right: when the phone number cannot be included, Meta omits messages[].from and contacts[].wa_id. It does not put a BSUID in them. The identity arrives as from_user_id and user_id instead. So code that reads msg.from gets undefined, not something unfamiliar it might notice — which means a real customer's message is dropped quietly rather than erroring.

A BSUID looks like US.13491208655302741918: an ISO 3166 alpha-2 country code, a period, and up to 128 alphanumeric characters. That is longer than a field sized for a phone number. And there is no route back from a BSUID to a number, by design — if you need the number, ask for it in the conversation.

What will a WhatsApp service message actually cost from October 1, 2026?

The same as a utility or authentication message to that market, with no volume tiers. Meta said it would publish the October rates by September 1, 2026, and at the time of writing that table has not appeared — but you do not need it, because the equivalence rule is already documented. Your market's utility rate is your service rate.

The rates we measured on a live WhatsApp Business Account put that at ₹0.1150 per message for India and ₹1.1509 for the UAE. Those came out of Meta's pricing_analytics endpoint, not off a published rate card.

One thing that catches people modelling this: Meta bills in your WhatsApp Business Account's own currency, whatever country the message lands in. If you are working from a rate card denominated in the recipient's currency, you are forecasting a different bill from the one you will get.

What are WhatsApp Flows and how do they fit into the 2026 roadmap?

WhatsApp Flows are Meta's native in-chat structured interaction forms — calendar pickers, multi-step registration forms, appointment booking, order customization, feedback collection — all within WhatsApp without the customer opening a browser or app.

In 2026, Flows remain the preferred method for structured data collection and integrate with agentic workflows. The recommended architecture is: Flows for predictably structured inputs (80% of cases), AI extraction for unstructured inputs like voice notes, photos, and documents (20%).

Klaros ships 15 pre-built Flow blueprints across 8 solution packs, with full Flows lifecycle management (create, publish, deprecate) and completion-action branching.

Do I need a BSP to use the WhatsApp Business API?

No. Any business can connect directly to the WhatsApp Cloud API using their own WhatsApp Business Account (WABA) and Meta billing. The API, endpoints, webhooks, and message rates are identical whether you use a BSP or connect directly.

Meta distinguishes between two partner types: Solution Partners (who can extend credit and invoice clients directly) and Tech Providers (who cannot). Neither tier unlocks messaging features the other lacks — the Cloud API is the same for everyone.

A BSP may still be the right choice if you need done-for-you onboarding, local invoice support, or managed infrastructure. The decision is about convenience and support model, not API capabilities.

Sources and further reading

Primary sources used to compile this tracker, plus Klaros implementation write-ups.

Meta for Developers — WhatsApp Business Platform

Official documentation, API reference, and changelog. The primary source for all platform information on this page.

Meta WhatsApp Pricing (official, verify current rates here)

Per-message rates by country and category. Rates change, and this is the authoritative current source for them. Note that as of 2026-08-29 this page still describes non-template messages and in-window utility templates as free and does not mention the October 1 change at all. It is the right source for rates and the wrong one for what is about to be billable.

Meta: upcoming pricing for non-template messages

The primary source for the October 1, 2026 change, and the only Meta page that documents it. States the effective dates for service messages, utility messages and Meta Business Agent messages, the rate benchmark, the absence of volume tiers, and that the 72-hour free entry point window survives. Re-checked 2026-09-04: the page still carries Meta's commitment to publish the October rates "by September 1, 2026", and that table has not appeared. The benchmark it documents is enough to derive them anyway.

Meta: business-scoped user IDs

The primary source for usernames and BSUIDs, and worth reading rather than reading about. It is specific where the summaries are loose: it states that the phone number fields are omitted when a number cannot be included, not repopulated, gives the identifier format, and says plainly that support is mandatory. Verified 2026-09-04.

WhatsApp Cloud API — reference documentation

The technical reference for the API Klaros is built on. Every endpoint, webhook event, and message type.

What you are actually buying when you buy WhatsApp →

First-hand structural map of the WhatsApp Business supply chain: Meta, Solution Partners, Tech Providers, and where Klaros fits. Includes the honest case for when a BSP is the better choice.

WhatsApp payments with Razorpay: what the docs leave out →

First-hand implementation guide to collecting payment inside a WhatsApp thread in India.

Klaros vs BSPs — honest cost comparison →

What a per-message BSP markup actually costs at volume. Live calculator.

Klaros product roadmap →

What Klaros is building, what's in development, and what we deliberately won't build.

On 1 October, every reply starts costing something.
The question is how much, and to whom.

Two things change your answer. One is the volume of in-window replies you send, which the calculator will tell you from this same rate card. The other is whether anything is added on top of Meta's rate before it reaches you: Klaros connects straight to the Cloud API on your own WhatsApp Business Account, so what Meta charges is what you pay. That part is worth checking against your current invoice either way, ours or anyone's.

Work out your October cost → Check your invoice for markup → Start free trial