How to unify two WhatsApp numbers in one Meta account

When a contact moves to a different playbook and that playbook uses a different WhatsApp number, template sends often start failing. This isn’t a Vixiees bug caused by the playbook change, it’s a Meta restriction: each WhatsApp Business Account (WABA) has its own templates, and templates created in one WABA can’t be used from a number that lives in a different WABA.

1. Why this happens

Every WhatsApp number belongs to a WABA, and the templates approved in Meta are tied to that WABA, not to the number itself. When a contact changes playbook and that playbook uses a number from another WABA, the contact moves to a channel where those templates don’t exist, which is why the sends fail.

There are two ways to fix it: use a single number across both playbooks, or keep both numbers but unify them under the same WABA.

2. Option 1: use a single number in both playbooks

This is the simplest option. The contact always receives messages from the same number regardless of which playbook they’re in, and all templates work because everything lives in one WABA.

Steps:

1. Choose the number (and therefore the WABA) that all messages will be sent from.
2. Create the templates that currently only exist in the other WABA, and wait for Meta’s approval.
3. Once approved, change the WhatsApp number on the playbook that used the other number. This is done from Playbook Configuration → Communication → WhatsApp numbers.

Nothing gets deleted or moved in Meta: you’re only replicating templates and changing the playbook’s configuration. This is the recommended option unless you specifically need to keep two separate numbers: no risk, no service interruption.

3. Option 2: keep both numbers, unified under the same WABA

This is for cases where you need to keep messaging from two different numbers, but with templates working on both because they both live in the same WABA.

Part A: prepare the templates in the destination WABA

Do this before moving the number. If you move it first, it ends up in a channel where the templates you need don’t exist yet.

1. Decide which WABA the two numbers will be unified into.
2. Create all the templates you need in that WABA and wait for Meta’s approval.

Part B: move the number from one WABA to the other (from Meta)

1. Go to WhatsApp Manager: business.facebook.com → menu → WhatsApp Manager (or Business Settings → Accounts → WhatsApp Business Accounts → select the account → “WhatsApp Manager Settings”). You need to be an admin of the business portfolio.
2. Select the source WABA (the one you’re emptying) in the account selector.
3. Turn off two-step verification for the number: Account Tools → Phone Numbers → select the number → Turn off two-step verification.
4. Remove the number from that WABA, from the same Phone Numbers screen.
5. Switch to the destination WABA (where everything will be unified) in the account selector.
6. Add the number with the “Add Phone Number” button. The wizard will ask you to create the profile (display name, category, description, timezone) and verify the number with a 6-digit code, received through a call handled by Vixiees.

The number needs to be added and verified in the destination WABA in Meta before you integrate it again in Vixiees (Settings > Phones). Integrating it in Vixiees first, without completing this step in Meta, won’t work.

With this, both numbers end up in the same WABA: even if the contact changes playbook and number, the templates will work without issues.

4. Important conditions before applying Option 2

• Only portfolio admins can remove a number, and Meta doesn’t allow removing a number that has sent paid messages in the last 30 days. If the number is actively sending templates or campaigns, you’ll need to wait 30 days without paid sends before you can remove it. This is usually the main blocker for this option.
• Removing a number is irreversible and requires re-verifying it to add it again.
• There’s a downtime window: between removing the number and re-verifying it on the destination WABA, that number is out of service and customer messages queue up.
• Templates don’t move with the number, they belong to the WABA. That’s why Part A always has to be done first.

Conclusion

If WhatsApp templates stop sending when a contact changes playbook, the reason is almost always that the new number lives in a different WABA than the one with those approved templates. The simplest fix is using a single number across both playbooks; if you need to keep two separate numbers, unify them under the same WABA from Meta, preparing the templates first and only then moving the number, respecting Meta’s 30-day rule with no paid sends before it can be removed.

Relevant scenarios

A client reporting that a contact stopped receiving WhatsApp templates right after a playbook change most likely doesn’t have a Vixiees configuration issue, but two numbers in different WABAs with different templates. Before escalating as a technical issue, check which WABA each number lives in and whether the templates being sent actually exist and are approved in that WABA.