WhatsApp account model in October 2026: what changed for Cloud API teams?

Meta described the WhatsApp Account Model Evolution on 16 June 2026. Its design gives a WhatsApp Account (WAAC) the number and identity, while a Messaging Account (PMA) holds an integration's templates and billing. Gupshup's partner guidance dates the automatic migration from 23 September through mid-October 2026. Gupshup says existing campaigns should continue through the scheduled rollout; this window is not evidence that a particular number was migrated or tested.

The account split is useful to teams that manage a Cloud API number, templates, a payment method, partner access or more than one integration. A business using only the WhatsApp Business phone app should not infer that it now has a Cloud API integration. The new architecture also does not establish that Whats91 has enabled a multi-provider workflow for a given customer.

Before this change, teams often used one WABA identifier when discussing the number, message templates and billing together. In the new model, the WhatsApp Account contains the business phone number and identity. A separate Messaging Account is associated with an integration and manages its own templates, payment settings and related messaging activity. Meta's developer presentation describes one number being usable across multiple partners and integrations with billing kept separate.

Gupshup says the migrated Messaging Account retains the existing WABA ID for compatibility, while the WhatsApp Account gets its own identifier. Do not rename an existing account ID in code based on its label alone. Check the actual object returned by Meta and the identifier expected by each API call, webhook subscription and admin screen. The business portfolio remains a separate owner and permission boundary.

The architecture allows a number to be associated with more than one Messaging Account. Each integration can have separate templates and billing. That is a platform capability, not an instruction to connect another provider immediately. Gupshup notes that the number's quality or a ban can affect all associated messaging accounts, so separation of billing does not isolate every operational risk.

Account and routing map

One number, separate messaging accounts

Check the number owner, each integration's templates and billing, and the inbound responder.

01

Identity

Confirm the WhatsApp Account that holds the business phone number.

02

Messaging

Check each integration's templates, payment method and account ID.

03

Routing

Verify who receives and replies to each incoming conversation.

Inbound messages need a clear responder. Meta's Conversation Routing documentation describes assigning each inbound message to a single responder based on its entry point. Before adding a second integration, identify who handles organic chats, ad-initiated chats and any handoff. Test the route with a consented number and inspect the actual webhook destination. Do not assume both systems receive or can reply to every message.

For an existing customer, start with read-only checks in Meta Business Suite and WhatsApp Manager. Note the business portfolio, WhatsApp Account, Messaging Account, phone number ID, template list, billing method and subscribed app. Compare these with the IDs your integration stores. A changed label in the UI does not by itself require a migration or a new template.

Gupshup's rollout guidance says existing Cloud API endpoints, phone number IDs, template workflows and billing remain backward compatible through the first half of 2028. This is partner guidance about Meta's transition, not a warranty for custom code. If an API or webhook payload differs from what your integration expects, capture a sanitized example, compare it with current Meta documentation, and plan a small test before changing production mappings.

This guide was prepared on 16 October 2026. Meta's June developer presentation establishes the account model; Gupshup's September partner article gives the September–October rollout window and implementation context, including compatibility and routing. A recent independent explanation was also checked, but the account-model claims here rely on Meta and the partner's documented rollout. The Meta Help Center and developer routing pages may require a browser session; their links are provided for direct account-specific verification.

No Whats91 customer account, WhatsApp Manager view, billing record, Cloud API request, webhook route or multi-provider setup was inspected for this article. Availability and the safe next step depend on the exact business portfolio, permissions, integration and Meta screen shown to the account owner. Do not treat the scheduled rollout date as a promise that every customer's configuration is identical.