WhatsApp Business account model: what is changing

What is Meta changing?

Today, a WhatsApp Business Account, commonly called a WABA, bundles phone numbers, message templates, billing, webhook subscriptions and partner access. That structure works for one integration but creates friction when a business needs multiple providers or separate billing arrangements.

The new model separates business identity from messaging operations. The legacy WABA becomes two account types: a WhatsApp Business Account for the phone number and a Messaging Account for templates, billing, analytics and webhooks.

The two account types

WhatsApp Business Account (WAAC)

The WAAC represents the identity customers see. It holds one business phone number and may support a business username in the future. A company can share the same WAAC with a direct integration and multiple partners, allowing everyone to work with one trusted number.

Messaging Account

The Messaging Account holds message templates, payment settings, metrics and webhook subscriptions. Each partner can have a separate Messaging Account connected to the same number. Existing WABA IDs will remain and become Messaging Account IDs during the first phase.

A practical example

Consider a small business using its own integration for customer service and an agency for marketing campaigns. Under the old structure, this often required a second number or a provider migration. Under the new model, both integrations can use the same phone number while maintaining separate templates, billing and analytics.

• Customers see one company contact.
• The service integration retains its own operational setup.
• The agency manages separate templates and spending.
• Adding or changing a partner no longer requires moving the number.

What stays the same at first?

Phase 1 is designed to be backward compatible. Meta migrates existing phone numbers, business profiles, templates, payment methods and tokens automatically. Current IDs and API calls continue to work initially, and customers do not need to complete onboarding again.

Conversation pricing, number registration, throughput and portfolio messaging limits are not immediately changed. When multiple partners use the same number, they still share that number's throughput and the business portfolio's messaging limit.

Templates and billing require attention

Templates are isolated by Messaging Account. If two partners need the same template, it must exist in both accounts. Meta provides a Template Migration API, but copied templates lose their previous quality rating and messaging tier. Meta estimates that the new history may need roughly two to four weeks to ramp up.

Billing is isolated as well. Each Messaging Account has its own payment method. This creates cleaner financial control, but developers must identify which Messaging Account pays for each message in multi-account scenarios.

Transition timeline

Phase 1 — general availability in the second half of 2026

Meta performs the migration automatically. The phone number moves to a WAAC and the existing WABA becomes the Messaging Account. Current APIs keep working. Meta's email notice says the terms take effect on September 23, 2026, with account transitions between September 23 and October 15, 2026. The technical feature is still described as beta and details may change.

Phase 2 — new Graph API version in the first half of 2027

Meta plans to expose WAAC IDs, new endpoints, a new webhook topic and separate permissions. When several Messaging Accounts share one number, the newest Messages API will require messaging_account_id.

Phase 3 — mandatory transition in the first half of 2028

messaging_account_id becomes mandatory for applicable multi-account setups. APIs that currently use a phone number ID in the path or parameters will need a WAAC ID instead.

What should businesses do now?

1. Map integrations: list every CRM, agency and platform sending messages through the number.
2. Assign ownership: document who manages templates, billing, webhooks and quality.
3. Talk to providers: confirm their roadmap for WAAC and messaging_account_id.
4. Avoid unnecessary migrations: Phase 1 is automatic, so do not recreate accounts without a clear reason.
5. Plan engineering work: multi-partner setups should schedule API changes during 2027.
6. Monitor templates and costs: reporting must account for separate Messaging Accounts.

Conclusion

The new model gives businesses more flexibility. One phone number remains the trusted identity while multiple integrations operate with independent templates and billing. Most small businesses do not need immediate action, but they should clarify responsibilities and ensure their providers are ready for the 2027 and 2028 API changes.

Because the feature is still in beta, review the official Meta documentation before implementing technical changes.