For a business, a WhatsApp number is more than a way for customers to send messages. It is the number customers use to discover products, receive updates, ask for support, complete authentication, and continue conversations with a brand. But behind that single number, a business may use several different technologies and service providers. One platform may handle marketing messages. Another may support customer service. A business may also have a direct API integration or use one of Meta’s own solutions.
Until now, the WhatsApp Business Platform account structure has made these relationships relatively closely tied to individual integrations. Meta is now changing that model. With its updated account structure, one WhatsApp phone number can be shared across multiple integrations while keeping billing separate for each integration. This can include partners, direct integrations, and Meta’s own solutions.
For businesses, this could make it easier to build a more connected customer journey. For developers and WhatsApp solution providers, it introduces a new way to think about how phone numbers, integrations, and billing are connected. More importantly, the change is designed to happen without breaking existing integrations.
Why is Meta changing the WhatsApp account structure?
The way businesses use WhatsApp has become more complex. A company may not rely on one system for every customer interaction. Marketing, authentication, service messages, advertising, and other use cases can be handled by different teams or technology providers. The challenge is that the customer should not have to understand any of this complexity.
If a customer starts a conversation with a brand through WhatsApp, they expect to continue that conversation with the same business, regardless of which system is handling the interaction in the background. Meta’s new account structure is designed around this idea.
Instead of treating a phone number as being tied to one integration, the new model allows businesses to use the same number across multiple integrations. The different systems can work in the background while the customer continues to interact with one recognisable business number. That is the central idea behind the update.
From one integration to multiple integrations
The easiest way to understand the change is to compare the old and new models.
Previously, the relationship was largely:
One phone number → One integration
Under the new account structure, it becomes:
One phone number → Multiple integrations
For example, imagine a business using WhatsApp for three different purposes. Its marketing partner could handle promotional messages. A separate technology provider could manage utility messages. A direct integration could handle service conversations. Instead of requiring a separate number for each setup, the business can use the same WhatsApp number across these integrations.
Meta describes this as moving from a 1:1 relationship between phone numbers and integrations to a 1 model. This does not mean that every connected system simply responds to every customer message. The business can configure which integration should respond to different messages.
That distinction matters because the goal is not to create more confusion behind the scenes. It is to allow more systems to work together while keeping the customer experience simple.
The important change: separating the WhatsApp account from the messaging account
This is where the technical part of the update becomes easier to understand. Under the new structure, Meta is separating the business’s WhatsApp phone numbers from the messaging and billing relationships connected to those numbers. The WhatsApp account becomes the layer associated with the business and its phone numbers.
A Messaging Account, meanwhile, is associated with an individual partner or integration and carries its own payment method and billing relationship. In simple terms, the phone number no longer has to determine which single provider or integration is responsible for messaging. The number can remain the same while different integrations have their own messaging accounts. This separation is what makes the new multi-integration model possible.
One important detail is that message templates are also kept separate for each messaging account. A template created by one provider is not automatically available to another provider, even when both use the same WhatsApp phone number. If a business needs the same template across multiple integrations, it must create it separately in each messaging account or use Meta’s Template Migration API to copy it. (Source: Facebook Developers)
What does this mean for billing?
The separation is not only about technology. It also applies to billing. Each messaging account can have its own payment method. A payment method attached to one partner’s A messaging account cannot simply be shared with another partner. This gives businesses more control over how messaging costs are separated.
For example, a company could have different teams or business units using the same WhatsApp number while maintaining separate billing arrangements. Meta also highlights a use case where different departments or regions of the same company can maintain separate billing under one phone number. This requires the solution provider or direct integration to implement the relevant API parameter.
So the new structure is not simply about allowing more integrations. It also creates a clearer boundary between those integrations when it comes to payments.
One customer conversation can involve multiple systems
There is another important part of this update: conversation orchestration. When several integrations are active on the same phone number, businesses can configure which system should respond to a particular message. Meta also says its system can provide an AI-generated conversation summary to the responding system during handoffs. This is intended to help the next responder understand what has already happened in the conversation. The AI-powered routing feature requires business opt-in.
This could become important as businesses use WhatsApp for more parts of the customer journey. A customer could discover a product through one use case, receive an update through another, and later contact the business for support. Behind the scenes, different systems may be involved. From the customer’s point of view, however, the conversation can remain connected to the same business number.
The larger idea is simple: more technology behind the conversation does not have to mean a more fragmented customer experience.
What changes for developers?
For developers and WhatsApp solution providers, the update is significant, but Meta is positioning it as a backward-compatible change rather than a forced migration. Existing Cloud API endpoints continue to work. Phone number IDs, access tokens, template workflows, and the existing message-sending endpoint remain unchanged. Conversation-based billing is also unaffected. The main new development consideration is the messaging account ID parameter.
Meta is making this parameter available for Cloud API calls used for sending messages, including /messages and /marketing messages. Solution providers are encouraged to test and implement it because it enables capabilities such as separate billing for different business departments or regions using the same phone number.
Importantly, this is an additive change. Existing API calls that do not include the messaging account ID will continue to work. That means developers do not need to treat the update as a complete rebuild of their existing WhatsApp integrations.
However, developers should prepare for the next stages of the rollout. Meta plans to introduce a new Graph API version in the first half of 2027, followed by a mandatory transition in the first half of 2028. From that final phase, APIs that currently use a phone number ID in the endpoint path or as a query parameter will need to use the new WhatsApp Account ID instead. Developers should plan their updates ahead of this deadline. (Source: Facebook Developers)
What happens to Embedded Signup?
Embedded Signup is also being updated to support the new structure. For businesses, the updated flow allows a phone number to be re-shared during partner onboarding, after which a unique messaging account is created for the partner.
For partners, Meta says the existing WABA ID will continue to be returned, meaning current partner integrations do not need to change simply because the new account structure is being introduced.
This is another example of the broader approach Meta is taking: introducing the new account structure while keeping the existing developer experience largely intact.
What stays the same?
This is perhaps one of the most important things for developers and businesses to understand. The account structure is changing, but several familiar parts of the WhatsApp Business Platform are not.
Existing Cloud API endpoints continue to work. Phone number IDs and access tokens remain valid. Template creation, editing, and submission continue as before. Marketing Messages API behaviour remains unchanged, as does the existing message-sending endpoint. Meta also says business verification, display names, quality rating,s and messaging limits remain unchanged. Conversation-based pricing is unaffected.
So the update should not be understood as:
“Everything about WhatsApp Business Platform is changing.”
It is more accurately understood as:
“The underlying account structure is becoming more flexible, while the existing APIs and workflows remain compatible.”
What does this mean for WhatsApp’s partner ecosystem?
The change could also reshape how businesses choose and combine WhatsApp solutions. A business no longer has to think only in terms of selecting one provider for an entire WhatsApp setup. The new structure creates more room for specialised providers to become part of the same customer journey.
This could include CPaaS providers, CRM and CDP platforms, ecommerce platforms, agencies, chatbot providers, adtech companies, and other technology businesses. Meta describes the updated structure as creating opportunities for partners to add capabilities to existing solutions and specialise within a customer’s broader technology stack.
For the ecosystem, that could mean more collaboration between different types of providers. For businesses, it could mean greater choice. And for customers, the real measure of success will be whether that additional choice remains invisible in the experience they have with the brand.
A more connected WhatsApp ecosystem
The biggest change in Meta’s new account structure is therefore not simply the introduction of another account ID or API parameter. It is the separation of three things that businesses increasingly need to manage independently: the phone number customers recognise, the systems that send messages, and the billing relationships behind those systems.
Once these layers can operate more independently, a single WhatsApp number can become a shared customer-facing layer for multiple technologies. That creates room for businesses to add new capabilities without having to change the number of customers they already know. It also gives developers more flexibility to build specialised solutions around an existing WhatsApp setup.
For now, Meta’s message to developers is relatively clear: existing integrations remain backward compatible, while the new messaging account ID provides a path to take advantage of the additional capabilities. Meta states that the new identifiers and account structure are additive, with existing integrations remaining compatible through the first half of 2028. The broader shift is equally clear.
WhatsApp is moving from a model where one number is closely tied to one integration towards an ecosystem where one number can support several integrations without losing the continuity of the customer relationship. For businesses building increasingly complex customer journeys on WhatsApp, that may be the more important change to watch.
