Meta is separating business phone numbers from provider-specific templates and billing through its WhatsApp Account Model Evolution update. You can now use a single WhatsApp phone number across Salesforce and another provider simultaneously without disrupting existing journeys, templates, or API integrations.
Where: This change applies to Marketing Cloud Engagement and Messaging Cloud Next editions with WhatsApp add-on.
When: This change is available as of October 15, 2026.
Why: Share one phone number with Salesforce and another business solution provider, each with its own messaging account. You can’t connect two Salesforce messaging accounts to the same phone number.
How: Meta automatically migrates existing accounts. Your existing account IDs and API calls continue to work.
For a single messaging account on a phone number, no action is required. On a shared number, Salesforce supports only the primary partner role to manage conversations and message routing.
Consent doesn’t sync across providers on a shared number. If a customer opts out through one provider, the other providers don’t receive that opt-out, so the customer can keep receiving WhatsApp messages from them.
Use one provider for all WhatsApp messaging. Alternatively, to keep consent status consistent across providers, manually record opt-outs in Salesforce, as you do for Meta Direct.