WhatsApp's New Account Model: What the WABA Split Means for Your Business

For years a WhatsApp Business Account, the WABA, was one box that held everything: your phone number, your templates, your payment method and the partner that sent messages for you. Meta is now splitting that box in two. The change is already rolling out, it is automatic, and for most businesses nothing has to be done. It still decides how you can work with more than one provider, how billing is split and how your API calls will look from 2027.

This guide explains the two new objects, the three phases of the timeline, and what to check if you use more than one platform. It is based on Meta’s own documentation, linked at the end.

What changed: one WABA becomes two accounts

According to Meta’s account model documentation, the old WABA is divided by job:

New object	What it holds	Who owns it
WhatsApp account (WAAC)	One business phone number and, in the future, one business username, plus the profile information and catalogs	The business (the client)
Messaging account	Templates, billing and webhook subscriptions	One per partner working with the business

Two details are worth remembering:

• Existing WABA IDs become Messaging account IDs. Your current ID keeps working. Meta advises subscribing to the whatsapp_business_account webhook with that ID, as before.
• The client owns the WAAC and shares it with partners. WhatsApp accounts can be linked into a hierarchy Meta calls a phone set, and a client can share that set as a group.

The practical meaning is simple. Your number and your customer-facing identity now belong to you in one place. Each tool that sends messages for you gets its own Messaging account, and you decide which tools may use the number.

The timeline, 2026 to 2028

Meta describes three phases:

1. Phase 1, general availability. Rolling out from September 23, 2026, with all businesses migrated by mid-October 2026. The migration is automatic. Meta says no code changes are required, except in multi-Messaging account scenarios.
2. Phase 2, a new Graph API version, first half of 2027. The newest Messages API version requires messaging_account_id in setups where one token can reach several Messaging accounts on the same number, and a WAAC ID is introduced.
3. Phase 3, mandatory transition, first half of 2028. All Messages API versions require messaging_account_id in those setups, and APIs that use phone number IDs must target the WAAC ID instead.

Meta’s advice is to plan engineering work in 2027 so integrations are on the new APIs before the 2028 date. If you use a platform rather than your own code, that work is your platform’s job. Ask it for its plan.

What changes for templates, billing and limits

Templates. They stay in the Messaging account where they were created. If templates are migrated into another Messaging account, Meta says their quality ratings and messaging tier reset to baseline, with a ramp-up of roughly 2 to 4 weeks. Do not move templates between accounts the week before a campaign.

Billing. Each Messaging account has its own payment method, and each partner is billed through its own Messaging account. The charge goes to the Messaging account tied to the sending app, while delivery receipts return to the sending app. If a credit line is attached to a client-owned Messaging account, that account cannot be shared with another partner. For the per-message rates themselves, see WhatsApp Business API pricing.

Limits. Throughput stays at the phone number level and messaging limits stay at the business portfolio level. Meta states that the messaging limit, the number of unique users you can message in 24 hours, is shared across all partners on a number. Two providers on one number do not double your limit.

Number moves. Meta’s page says that moving a number between Solution Partners is not supported in the new model. Instead the client shares its WAAC with the new partner. Moving numbers inside one business is done by linking and unlinking WhatsApp accounts in Meta Business Suite. If you are planning a switch, read WhatsApp number migration and check Meta’s current instructions first, because this area is changing.

What changes in API calls

• messaging_account_id is a new optional parameter on Messages API calls. It becomes required in multi-Messaging account setups from phase 2.
• paid_messaging_account_id is kept as a deprecated, backward-compatible alias. Meta asks developers to move to messaging_account_id by December 31, 2026, after which the alias is planned for removal in a future Graph API version.
• A new whatsapp_account webhook topic is available as an option.
• Meta tells integrations to keep sending a valid 6-digit pin on registration calls.

If you send through one platform only, none of these are your concern today.

A checklist for this month

1. Find out who holds your WhatsApp setup. In Meta Business Suite, open WhatsApp Manager and look at the new split between WhatsApp accounts and Messaging accounts.
2. List your providers. If more than one tool sends from the same number, check which Messaging account each one uses and who pays for it.
3. Check your payment method on every Messaging account that sends messages. Billing follows the Messaging account, so the one that sends must have its own.
4. Do not migrate templates before a campaign. A quality and tier reset is the last thing you want in the middle of a launch.
5. Ask your platform for its API plan. The new Graph API version arrives in 2027, and the mandatory date is 2028.
6. Keep the business profile in one place. Because the profile and catalog live in the WhatsApp account, a clean profile now helps every partner you connect.

What this means in MonoChat

MonoChat is an official Meta Business Partner. You connect your own WhatsApp number to Meta’s Cloud API from Settings › Chat › Channels › Connect › WhatsApp Business API (Cloud), sign in through Meta’s popup and choose or create your business account. The WhatsApp number and its account stay yours, and Meta bills you directly for messages, with no markup from MonoChat. The steps are in the channels help article.

If you already work with another provider on the same number and want to bring MonoChat in next to it, or you plan to move to MonoChat, contact us before you start so we can look at your setup together. You can try the shared inbox on the free Basic plan at app.monochat.ai, and see the unified team inbox for what your team gets.

Sources: Meta for Developers, WhatsApp account model evolution; Meta for Developers, WhatsApp Business Platform pricing.