> ## Documentation Index
> Fetch the complete documentation index at: https://whatsapp-docs.kap.so/llms.txt
> Use this file to discover all available pages before exploring further.
# Multi solution conversations
# Multi-solution Conversations (MSC)
Updated: Dec 4, 2025
**Feature Availability: Invite-only beta. Managed partners, reach out to your SPM for more details**
To qualify for Multi-Solution Conversations, your business must have a messaging limit of 2,000 or higher.
**If WABAs associated with your phone numbers have restrictions or bans, you cannot onboard to the MSC Closed Beta.** Please [clear these restrictions](https://business.facebook.com/business-support-home/) before attempting to onboard.
Some features may not be available or work as expected. [Beta terms apply](https://www.facebook.com/legal/BetaProductTestingTerms).
## Overview
Multi-Solution Conversations enables businesses to use multiple partners and solutions **on the same phone number**, enabling a seamless chat thread experience for their customers.
## Key features
**Simple end-business onboarding via Embedded Sign-up:** Partners can onboard businesses easily through [Embedded Signup](https://developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/multi-solution-conversations#onboarding-for-msc--embedded-signup-flow-).
**Payment and template isolation per partner:** Each partner has their own WhatsApp Business Account, their own templates, and their own billing and metrics.
## How Multi-Solution Conversations works
The chart above illustrates a new WABA shared with each integrated partner, and assets separated per WABA.
The business shares all phone numbers associated with their WhatsApp Business Account (WABA) to a partner through the [Embedded Signup flow](https://developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/multi-solution-conversations#onboarding-for-msc--embedded-signup-flow-).
A new WABA is created and shared with the respective partner that the business onboards with.
The partner now has messaging or calling access to the business phone numbers shared with them and can message or manage calls on behalf of the business.
### Supported APIs and Usage
Businesses can use a single phone number across one or multiple partners across the following APIs and uses:
[Messaging via WhatsApp Cloud API](https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages)
[Calling via WhatsApp Cloud API](https://developers.facebook.com/documentation/business-messaging/whatsapp/calling)
[Click-to-WhatsApp Ads via Ads Manager](https://www.facebook.com/business/help/447934475640650?id=371525583593535)
**Note:** Direct developers using a partner for any of these use cases is supported with Multi-solution Conversations, **except for MM Lite**.
## Limitations
MM Lite is not supported for MSC businesses. Any [`marketing_messages`](https://developers.facebook.com/docs/whatsapp/marketing-messages-lite-api/sending-messages#send-marketing-template-messages) requests will either be routed via Cloud API or rejected if the `product_policy` filed is set to strict.
**MSC does not currently support:**
Conversation routing and management: currently, all parties the phone number is shared with receive incoming webhooks. Businesses must work with partners to manage response handling.
Coexistence phone numbers
Phone numbers using the Groups API
WABA created through Embedded Signup which are used on Ads Manager for Marketing Messages
[Measurement Partner onboarding](https://developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/measurement-partners)
### General limitations
Only 5 partners or solutions can be enabled per each end-business WhatsApp Business Account (WABA).
Only 1 partner can attach a catalog to the shared phone number(s) between partners.
### Phone number sharing limitations
The business cannot share a phone number with the same partner more than once via different WABAs.
For example, the business has a phone number linked to WABA 1 and then shares WABA 1 with Partner 1. If you have the same phone number linked to WABA 2, you cannot also share WABA 2 with Partner 1. If you try to share the phone number, you may receive an error.
## How messaging, calling, and account management works when using MSC
Use the table below to understand how different features and APIs work when using MSC as a partner or business.
### Onboarding
**Value:** Use an existing phone number across multiple partners and solutions.
| Business Experience | Partner Experience |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| The business onboards an existing phone with more than one partner via [Embedded Signup.](https://developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/multi-solution-conversations#onboarding-for-msc--embedded-signup-flow-) | Partners are able to see the new WABA shared with them within Meta Business Suite settings. |
### Account management
**Value:** Account management as usual
| Business Experience | Partner Experience |
| ------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
| Able to perform account management operations via the usual pathways (WhatsApp Manager, API, etc) based on permissions granted. | |
### API usage
**Value:** Enable messaging and calling functions across multiple partners on a single phone number
| Feature | Business Experience | Partner Experience |
| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cloud API Messaging
MM Lite (see limitations section above) | Not applicable | **Send messages:** All partners are able to send messages via API on the shared phone number(s).
**Receive messages:** All partners will receive all incoming webhooks on the shared phone number(s). |
| [Cloud API Calling](https://developers.facebook.com/documentation/business-messaging/whatsapp/calling) | Not applicable | Partners onboarded to the Calling API are able to make [business-initiated calls](https://developers.facebook.com/documentation/business-messaging/whatsapp/calling/business-initiated-calls), and receive [user-initiated calls](https://developers.facebook.com/documentation/business-messaging/whatsapp/calling/user-initiated-calls).
[Learn more about the WhatsApp Business Calling API](https://developers.facebook.com/documentation/business-messaging/whatsapp/calling) |
| [Templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview#create-and-manage-templates) | Not applicable | Partners can create templates as usual by using the new WABA, either through the API or WhatsApp Manager.
[Learn how to create and manage message templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview#create-and-manage-templates) |
| Conversation Routing and Management | Currently, all parties the phone number is shared with receive incoming webhooks.
Businesses must work with partners to manage response handling. | Currently, all parties the phone number is shared with receive incoming webhooks.
Businesses must work with partners to manage response handling. |
### Billing
**Value:** Simplified, siloed billing ownership per WABA
| Business Experience | Partner Experience |
| ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Businesses can add a payment method to any of the WABAs created and shared with partners. | Partners add their own payment methods to the WABA shared with them, the same as they do today.
Each Partner is billed only for the messages sent through their app.
[Per-message pricing applies.](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing#per-message-pricing) |
### Asset management
**Value:** Simplified, siloed asset management per WABA
| Feature | Business Experience | Partner Experience |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Templates | The business can create and see templates on all WABAs shared with partners. | Partners can only create templates on the WABAs that are shared with them.
Partners are not able to see other Partners’ templates |
| Phone numbers | Phone numbers are a shared resource.
Whether the end business or partner adds the phone number, it will be visible to all in Whatsapp Manager. Any new phone numbers added to WABAs using MSC are shared with all partners with access to these MSC WABAs. | |
### Offboarding
**Value:** The business has full control of what partners, assets, and accounts they retain.
| Role/Asset | Business Experience | Partner Experience | Partner Experience |
| ------------ | ------------------------------------------------------- | ---------------------------------------------------- | ------------------ |
| WABA | The business can delete the WABA. | Partners **cannot delete** the WABA shared with them | |
| Phone number | Both the business and partner can delete a phone number | | |
| Partner | The business can remove the partner. | Not applicable. | |
## How violations and bans work with MSC
**Phone Number Violations**
Phone number violations will ban all WABAs across all partners, associated with the phone number.
**Template Violations**
Template violations will only apply to the violating WABA.
**Business Portfolio Violations**
Any bans on the Business Portfolio will ban all WABAs associated with the phone number
[Decision appeals](https://developers.facebook.com/documentation/business-messaging/whatsapp/policy-enforcement#appeals) continue to function as they do today.
## Onboarding for MSC (Embedded Signup flow)
Only available to businesses with a messaging limit of at least 1000 business-initiated conversations in a rolling 24 hour period.
Once a business meets the eligibility requirements, the MSC flow for Embedded Signup is automatically displayed in the Embedded Signup (ES) flow ( [v2 and above](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/versions#version-2)). Partners don’t need to configure anything in Embedded Signup for this to work.
This means that when businesses sign-up to a partner through ES, they will automatically be shown the flow below and be given the choice to share their existing business phone numbers which will onboard the business and partner to MSC. ES has two experiences and a given business may see either one of these randomly. Both experiences are described below
Once the business completes the Embedded Signup flow, the partner does not need to re-register with the business again.
### Embedded Signup flow for businesses (experience 1)
The Notes column calls out any MSC specific notes for each screen.
| Screen | Notes |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Authentication screen](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/default-flow#authentication-screen) | No changes |
| [Authorization screen](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/default-flow#authorization-screen) | No changes |
| [Business Asset Selection Screen](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/default-flow#business-asset-creation-screen) | This is where you’re able to select a WhatsApp Business Account that is already shared with other partner(s) |
| [Phone number addition screen](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/default-flow#phone-number-addition-screen) | Select ‘Use a new or existing WhatsApp number’, then click on the dropdown ‘Add a new WhatsApp number’, then select existing WhatsApp Business Account you want to share with current partner |
| [Permissions review screen](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/default-flow#permissions-review-screen) | No changes |
| [Success screen](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/default-flow#success-screen) | No changes |
### Embedded Signup flow for businesses (experience 2)
Businesses onboard to MSC by using the Embedded Signup flow:
Note: This screenshots may differ as we evolve the product. Use them only for illustration of the concept
Step 1: Select the Business Portfolio
Step 2: Select **Share existing WhatsApp phone numbers**
Step 3: The business selects the WABA with the phone number(s) they would like to share.
*Note: These numbers are only selectable if they have not been shared already with this partner.*
Step 4: Create a name for the new WhatsApp Business Account being created.
Step 5: Verify permission information.
Step 6: Verify signup information and finish.
## Troubleshooting
**The “Share existing WhatsApp phone numbers” option is greyed out**
This can happen for a couple of possible reasons
The business has already has a solution with the partner they are trying to share the number with
The business has exceed the 5 partner maximum for the number
The phone number is not eligible to send 1k messages yet
The phone number has not been registered
**What can I do if the business phone number goes offline?**
Rarely, a phone number can go offline. To solve this issue, try the following:
**Register the phone number again:** The business should search each of their WABA activity logs to find which partner registered the phone number first. Then, that partner can register the phone number again.
***(Optional)* Turn off 2-factor authentication (2FA):** If the business cannot obtain which partner originally registered the phone number, they can shut off 2FA and have another partner register the number again. [Learn how to disable 2FA on a phone number](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/phone-numbers#disabling-two-step-verification).
## FAQ
**How do I get support?**
For support concerning Multi-Solutions Conversations, choose the **WABiz: Onboarding** topic when opening a [Direct Support](https://business.facebook.com/direct-support/) ticket.
**How can I offboard from MSC?**
To offboard from MSC
***(Optional)* Migrate templates:** If there are newly created templates on an MSC-created WABA, please migrate them before offboarding. \[Learn how to migrate templates here.]
**Submit a WhatsApp support ticket:** Use the request type “Embedded Signup - MSC Offboarding” and include the WABA you would like to retain retained.
**Is MSC supported for Tech Providers, Tech Partners, and Multi-Partner Solutions?**
Yes.
**Will a partner be able to see how many partners a client is using and the specific services/capabilities each partner provides?**
No.
**Does every partner need to register a given business phone number to onboard it to MSC?**
No, only one partner needs to register it. Once the number has been registered, it is ready to be used with new partners without the need to re-register it.
**What happens if a business tries to onboard without having previously registered their phone number(s)**
In this case, an error will be displayed in the Embedded Signup UI prompting the business to register their number(s)
**If multiple partners respond to messages within the same conversation window, who will be charged?**
[Pricing follows the per-message changes released on July 1, 2025](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing#per-message-pricing).
**What happens if two partners send messages at the same time? Will I get billed twice?**
[Pricing follows the per-message changes released on July 1, 2025](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing#per-message-pricing).
**When will MSC become generally available?**
Mid-2026.
Did you find this page helpful?
ON THIS PAGE
Overview
Key features
How Multi-Solution Conversations works
Supported APIs and Usage
Limitations
General limitations
Phone number sharing limitations
How messaging, calling, and account management works when using MSC
Onboarding
Account management
API usage
Billing
Asset management
Offboarding
How violations and bans work with MSC
Onboarding for MSC (Embedded Signup flow)
Embedded Signup flow for businesses (experience 1)
Embedded Signup flow for businesses (experience 2)
Troubleshooting
FAQ
***