Summary

Starting September 23, 2026 - Meta has introduced a new account structure for the WhatsApp Business Platform Cloud API that allows businesses to use the same phone number across multiple integrations, including Business Solution Providers (BSPs), direct integrations, and Meta solutions such as Meta Business Agent.

This structure allows multiple Business Solution Providers to support the same customer journey while keeping billing separate for each integration. Meta has also introduced conversation routing, which lets businesses control which Business Solution Provider can respond to a customer conversation while allowing other providers to follow the conversation.

Note: Wati does not currently support multi-partner solutions with the new WAME / Messaging Accounts setup.

Instructions

What is changing in the WhatsApp Business Platform account structure?

Previously, when a business onboarded with a Business Solution Provider (BSP), Meta created a WhatsApp Business Account (WABA) for that BSP and added the business's phone number to it. This meant the phone number was tied to a single integration at a time.

With Meta's new account structure, a single WhatsApp Account (WAAC) can hold a phone number that is shared across multiple integrations. Each Business Solution Provider gets its own Messaging Account instead of WABA associated with that phone number.

The new structure follows this model:

1 WhatsApp Account (WAAC) → 1 phone number → Multiple Messaging Accounts (PMAs)

What is the difference between a WhatsApp Account and a Messaging Account?

The new structure separates phone number ownership from partner-specific messaging information.

  • WhatsApp Account (WAAC): Holds the business's phone number, which can be shared across multiple integrations.

  • Messaging Account (PMA): Contains information specific to each Business Solution Provider, including message templates, payment settings, and billing information.

Message templates are unique to each Messaging Account also known as PMA, so each Business Solution Provider can manage its own templates and billing settings separately.

Meta is deprecating the 6-digit two-factor authentication (2FA) PIN under the new model, and phone number migration is no longer supported. A business can no longer easily share their number with multiple partners and remove it when no longer needed.

How can multiple Business Solution Providers use the same phone number?

A business can assign different Business Solution Providers and Meta solutions to handle different types of messaging using the same WhatsApp phone number.

For example:

  • BSP A: Handles marketing messages.

  • BSP B: Handles utility messages.

  • BSP C: Handles service messages and customer support.

  • Meta solutions: Handle interactions through Meta Business Agent.

All these integrations can use the same WhatsApp phone number while maintaining a unified customer conversation thread.

Important: Any Business Solution Provider can send template messages. However, service messages can only be sent by the Business Solution Provider selected to handle service conversations.

What are the limitations of the new WhatsApp account structure?

Keep the following limitations in mind:

  • Phone number quality and account restrictions: If the phone number's quality is affected or the WhatsApp Account (WAAC) is banned, messaging services across all Messaging Accounts (PMAs) associated with that phone number will be affected.

  • Messaging Account access: The business and its respective Business Solution Provider can access their Messaging Account (PMA) within the relevant Business Manager (BM). This gives them access to partner-specific information, including message templates and credit line details.

  • WhatsApp Account access: Only business admins can access the WhatsApp Account (WAAC) within the relevant Business Manager because it contains information about all associated Messaging Accounts (PMAs).

What does the new account structure mean for businesses?

The new WhatsApp account structure is designed to make the transition seamless for businesses and technology providers. Here's what you need to know:

  • No action required for migration: Meta migrated all accounts to the new structure in October 2026. Businesses and technology providers don't need to take any action. The updated account structure will appear across Meta platforms, including Meta Business Suite and WhatsApp Manager. Existing campaigns that are in progress will remain unaffected.

  • Existing integrations will continue to work: Existing Cloud API endpoints, phone number IDs, message template workflows, and billing processes will remain unchanged for now. The new WhatsApp account and messaging account IDs are additional identifiers and do not replace existing ones during this backward compatibility period.

  • Embedded Signup will support the new structure: All versions of Meta's Embedded Signup flows will automatically reflect the new account structure. During signup, businesses will be able to share an existing phone number with a Business Solution Provider (BSP). Meta will automatically create a separate messaging account for that BSP.

What does the new account structure enable?

The new structure allows businesses to connect multiple Business Solution Providers to the same WhatsApp phone number.

For example, a business can use different Business Solution Providers for customer support, automation, and other specialized services without needing a separate phone number for each integration.

This helps businesses:

  • Manage customer interactions through a single WhatsApp phone number.

  • Work with multiple Business Solution Providers at the same time.

  • Maintain separate billing for each integration.

  • Create a more consistent customer experience across different platforms and providers.

Businesses can also route customer messages to the appropriate Business Solution Provider on the backend, ensuring that conversations remain continuous even when multiple integrations are involved.

What is conversation routing?

Conversation routing is a feature that allows businesses to control which Business Solution Provider can respond to a customer conversation when multiple providers share the same WhatsApp phone number.

The business manages provider assignments through Meta Business Suite. This ensures that the right Business Solution Provider responds to each conversation while other providers can stay informed.

To find the Conversation Routing settings log into your Meta Business Suite and go to Settings → Accounts → WhatsApp accounts, select the WhatsApp phone number, then open the Conversation routing tab.

How does conversation routing work?

Conversation routing gives businesses control over which Business Solution Provider can respond in specific situations.

  • Assign response permissions: Businesses can decide which Business Solution Provider is allowed to respond to a conversation through Meta Business Suite.

  • Allow takeovers: Businesses can assign another Business Solution Provider, such as one providing live agent support, to take over a conversation when needed.

  • Keep other providers informed: Handoff summaries and standby capabilities help other Business Solution Providers stay updated on the conversation, even when they are not the ones responding.

This approach helps multiple Business Solution Providers work together on the same customer journey without sending conflicting responses.

What is the role of Meta Business Suite in conversation routing?

Meta Business Suite allows businesses to manage which Business Solution Provider can respond to customer conversations. Businesses can assign response responsibilities and change those assignments when needed, including handing over a conversation to a live agent.

The business retains control over Business Solution Provider roles and conversation assignments.

Frequently Asked Questions (FAQs)

WhatsApp account structure

1. What is the new WhatsApp Business Platform account structure?

The new WhatsApp Business Platform account structure allows businesses to use the same WhatsApp phone number across multiple integrations, including different Business Solution Providers (BSPs), direct integrations, and Meta solutions such as Meta Business Agent.

A single WhatsApp Account (WAAC) holds the business's phone number, while each BSP gets a separate Messaging Account (PMA) containing its own messaging and billing information.

2. What is the difference between a WhatsApp Account (WAAC) and a Messaging Account (PMA)?

A WhatsApp Account (WAAC) holds the business's WhatsApp phone number, which can be shared across multiple integrations. A Messaging Account (PMA) contains information specific to a Business Solution Provider, including message templates, payment settings, and billing information.

Each Messaging Account has its own message templates and billing settings, allowing different providers to manage their integrations separately.

3. How can multiple Business Solution Providers use the same WhatsApp phone number?

A business can connect multiple Business Solution Providers and Meta solutions to the same WhatsApp phone number. Each provider can handle different types of messaging.

For example:

  • One BSP can handle marketing messages.

  • Another BSP can handle utility messages.

  • A third BSP can handle service messages and customer support.

  • Meta solutions can handle interactions through Meta Business Agent.

All integrations can use the same phone number while maintaining a unified customer conversation thread. Each provider maintains separate billing through its own Messaging Account (PMA).

Any BSP can send template messages. However, only the BSP assigned to handle service conversations can send service messages.

4. What are the limitations of the new WhatsApp account structure?

The new WhatsApp account structure has the following limitations:

  • Phone number quality and account restrictions: If the phone number's quality is affected or its WhatsApp Account (WAAC) is banned, messaging services across all associated Messaging Accounts (PMAs) will be affected.

  • Messaging Account access: The business and its respective BSP can access their Messaging Account through the relevant Business Manager (BM). This provides access to partner-specific information, including message templates and credit line details.

  • WhatsApp Account access: Only business admins can access the WhatsApp Account through the relevant Business Manager because it contains information about all associated Messaging Accounts.

  • Phone number migration: Phone number migration is no longer supported under the new model.

  • Two-factor authentication: Meta is deprecating the 6-digit two-factor authentication (2FA) PIN under the new model.

  • Multi-partner support in Wati: Wati does not currently support multi-partner solutions with the new WAME / Messaging Accounts setup.

Migration and existing integrations

5. Do businesses need to take any action to migrate to the new WhatsApp account structure?

No. Meta migrated all accounts to the new WhatsApp account structure in October 2026. Businesses and technology providers do not need to take any action. The updated structure will appear across Meta platforms, including Meta Business Suite and WhatsApp Manager. Existing campaigns that are already in progress will remain unaffected.

Existing Cloud API endpoints, phone number IDs, message template workflows, and billing processes will also remain unchanged during the backward compatibility period. The new WAAC and PMA IDs are additional identifiers and do not replace existing ones during this period.

Meta Embedded Signup also supports the new structure across all versions. During signup, businesses can share an existing phone number with a BSP, and Meta automatically creates a separate Messaging Account for that provider.

Conversation routing

6. What is conversation routing in the new WhatsApp account structure?

Conversation routing allows businesses to control which Business Solution Provider (BSP) can respond to a customer conversation when multiple providers share the same WhatsApp phone number.

Businesses manage provider assignments through Meta Business Suite. They can assign response permissions, allow another provider (such as a live agent support provider) to take over a conversation, and keep other providers informed through handoff summaries and standby capabilities.

This helps multiple providers collaborate on the same customer journey without sending conflicting responses.

Did this answer your question?