WABA to Messaging Account: what changes for Shopify WhatsApp

Meta split the WABA into a WhatsApp Account and a Messaging Account. Which ID to paste, where templates live, and what two providers on one number means.

If you opened Meta Business Suite recently and found two lists where there used to be one, WhatsApp accounts and Messaging accounts, you have met Meta's new account model. The WhatsApp Business Account, the WABA that every setup guide including ours tells you to copy the ID of, is being split into two things. This post explains what each half holds, which ID Beacon Messenger actually wants, what changed for you (so far, nothing), and the one genuinely new situation the split makes possible: a second provider sending from the same phone number at the same time.

What was one thing is now two

Until the second half of 2026 a WABA bundled everything about a business's WhatsApp presence: the phone numbers, the display names, the message templates, the payment method, the webhook subscriptions and the partner who had access. Meta's account model evolution splits that bundle along a clear line.

What each account holds under the new model
WhatsApp Account (WAAC)Messaging Account
Phone numbers and display namesYesNo
Business identity, catalogsYesNo
Message templatesNoYes
Billing, payment method, credit lineNoYes
Webhook subscriptions (which app receives events)NoYes
AnalyticsNoYes
Who it belongs toThe businessOne per provider or integration

The point of the split is the last row. A phone number lives once, under the WhatsApp Account. Each provider or integration that sends from it gets its own Messaging Account, with its own templates and its own bill. Providers such as 360dialog describe the result plainly in their account documentation: since October 2026 a phone number can have one Messaging Account per provider, which is how a business can use two of them on the same number at once.

The rollout is staged. Provider write-ups describe a first phase, happening now, in which existing WABA IDs simply become Messaging Account IDs and old API calls keep working; a second phase in 2027 that changes some Graph API behaviour; and a final, mandatory phase in 2028. Meta's own developer pages are the authority on dates, and they have moved before, so treat the years as a direction rather than a promise.

Which ID Beacon Messenger wants

The Connect screen asks for a WhatsApp Business Account ID, a phone number ID, an access token and an app secret. Under the new model the first of those is the Messaging Account ID, and because your existing WABA ID became your Messaging Account ID with the same number, a store connected before the change has nothing to update. The field label still says WhatsApp Business Account, as do most providers' dashboards and the Graph API itself, and we are leaving it that way until the API stops accepting the term.

The reason it has to be the Messaging Account ID, and not the ID of the new WhatsApp Account that holds the phone number, is what the app does with it. Beacon Messenger reads your approved templates from that ID, and it subscribes your Meta app to that ID so Meta delivers message status and inbound reply webhooks to the app. Both templates and webhook subscriptions are Messaging Account things. Paste the WhatsApp Account ID instead and the template list comes back empty and no webhooks arrive, which looks exactly like the automation is on but nothing sends problem.

The phone number ID is unchanged by all this. Messages are sent through it, as they always were, and it is still found on the phone number itself in the WhatsApp Manager.

  • Connected before the change: do nothing. Your saved ID is the Messaging Account ID.
  • Connecting for the first time: in Business settings, open Messaging accounts (not WhatsApp accounts) and copy the ID of the one that lists your templates. If you only have one, that is it.
  • Reconnecting after a disconnect: the credentials post still applies; the IDs are the same ones.

Two providers, one number: what is new

The one number or two post worked through the old constraint: a number could be in the WhatsApp Business app or on the API, and on the API it belonged to one provider. Coexistence loosened the first half of that. The Messaging Account split loosens the second. A store can now keep Beacon Messenger on its number for Shopify order, shipping and cash-on-delivery notifications and, on the same number, use a support desk or marketing platform through that platform's own Messaging Account.

Three things follow, and two of them are easy.

  1. Templates are per Messaging Account. The order confirmation template you had approved for Beacon Messenger is not visible to the other provider, and theirs are not visible here. If you want the same wording in both, submit it twice. This is also why a template that shows as approved in one dashboard can be absent from another: different account, not a sync delay.
  2. Billing is per Messaging Account. Each provider's conversations are charged to its own payment method. For a store that was told it would be billed once for the number, this is the item to check with the second provider before signing.
  3. Messaging limits are per phone number, shared across every Messaging Account on it. The 250 conversations a day tier, and the higher ones, count notifications from Beacon Messenger and campaigns from the other provider against the same ceiling. A marketing blast in the morning can leave no room for shipping notifications in the afternoon until the tier rises.

The hard one: where a reply goes

Outbound messages are simple: each provider sends through its own Messaging Account and Meta knows who sent what. Inbound is not. When the customer taps reply, there is one message and two providers who might want it. Meta resolves this with a conversation routing setting on the number that decides which provider receives incoming messages. The other provider does not get a copy.

For Beacon Messenger this matters in exactly one place: cash on delivery confirmation. The COD flow sends a template asking the customer to confirm, waits for their reply, matches it to the order and tags the order, then sends a short acknowledgement inside the customer-service window. Every step after the first depends on the reply webhook arriving here. If routing sends inbound messages to the other provider, the customer's reply lands in your support desk, the order is never tagged, and the acknowledgement either never sends or, when the app does try to answer, is refused because the conversation belongs to someone else. 360dialog documents a specific Graph API error for this case, which is reassuring in the sense that it fails loudly rather than silently.

The order confirmation, shipping update and abandoned checkout automations are outbound only and are not affected. They send, Meta reports delivered or read, and that status webhook follows the Messaging Account that sent the message, so the log stays accurate whoever is receiving replies.

So the decision is: who should get the replies? If the second provider is a support desk, the honest answer is probably them, in which case turn COD confirmation off in Beacon Messenger and let the support team confirm cash orders by hand from the conversation. If COD confirmation is the reason you installed the app, routing has to point at Beacon Messenger, and the support desk only sees conversations it starts. There is no setting on our side that changes this; the routing control is Meta's, in the WhatsApp Manager for the number.

A short checklist if you add a second provider

  1. Before signing up, confirm with the provider whether they will create their own Messaging Account on your number or expect to take over the existing one. Taking it over would disconnect Beacon Messenger's templates and webhooks.
  2. After their onboarding, open Business settings and check that you now have two Messaging Accounts and still one WhatsApp Account. Beacon Messenger's saved ID should match the first one.
  3. Send a test from the Connect screen. If it fails with a template error, the template list may have been read from the wrong account; reconnect with the right Messaging Account ID.
  4. Decide where replies go and set conversation routing accordingly. Then place a test cash-on-delivery order, reply to it, and check that the order gets tagged. The reply matching post covers what a correct run looks like.
  5. Watch the dashboard for a week. A rise in failed messages with a limit-related error after the other provider starts campaigns is the shared messaging limit at work, not a fault in either integration.

Nothing in this post asks you to change anything today if you have one provider and a working connection. The split is mostly invisible until a second party shows up on your number. When it does, the three questions are which account holds the templates, who pays for which conversations, and who gets the replies. Know the answers before the first order comes in, and Beacon Messenger will keep doing what it did before, under an account that merely has a new name.

More guides