Phone number onboarding with new WhatsApp account model

Here are the steps on how a new phone number or existing WhatsApp API phone number onboarding (from same BM) can take place on Gupshup.

NOTE : If you want to migrate a phone number from 1 BM to another, you have to deregister it from first BM first and then initiate new onboarding as below.

KNOWN LIMITATIONS FOR MIGRATION FROM 1 BSP TO ANOTHER : 
1. Templates will not be migrated automatically to the new PMA. However if you note the source WABA ID and provide it in the Gupshup Embed Signup flow, it will copy the templates from the source to the destination waba. Partner API for the same coming soon.
2. ONLY FOR TECH PROVIDERS : Onboarding of an existing phone number on BSP A with Tech Provider 1 to be done on BSP B by same Tech Provider is NOT YET supported by Meta. 
Disruptive Workaround : Original WAAC will need to be deleted first including the source PMAs which will lead to message disruption till the phone number is onboarded on to Gupshup/ODCEM.

LIMITATION: Wame (Meta's new account model) will not be supported on /v1/msg APIs for template and session messaging. Please upgrade to /v2 or /v3 endpoints.

NEW STEPS FOR ONBOARDING  -

Step 1 : Click on go live on the app dashboard and -

• select 'new phone number' for regular phone number 
• select 'Migrate a live phone number' for migrating a phone number live on another BSP (if using onboarding APIs, run the Partner API for marking app as migration at the end)
• select 'Use existing WhatsApp business app number' for coexistence

[onboarding API users can skip to Step 4 on generation of embed signup link]

Step 2 : Enter the contact details

Step 3 : Continue to Facebook or Share the Embed SIngup Link with customer

Step 4 : Embedded Signup - STEPS FOR BUSINESSES 

This has multiple parts in it - 

Step a: On Embed Signup Glow this will be first screen, click Continue

Step b: Enter the new or the phone number to be migrated
[in case of migration by Tech providers, prerequisite is to delete the Original WAAC - this is a disruptive step, and has been raised to Meta for resolutions]

Step c : Complete the OTP verification of the phone number (This may not be required in some cases of migration)

 [Applicable For Migration Usecase by Tech Provider] -  CRITICAL STEP

Open the WhatsApp Account dropdown and click on 'Create a WhatsApp account' as shown below - 

Now click Next

Step d2 : [For new onboarding case]

You will directly see the Create a WhatsApp Business account option in the WhatsApp Business Account dropdown. Continue with the same

Step e : Enter the business details and continue

Step f : Review screen will appear, Continue with the same 

The setup will begin - 

Step g : Many times the business admin will need to verify their identity with a 2FA setup for their own personal phone number. This step may not come every time. 

NOTE : This is not the Onboarding OTP, hence Gupshup cannot provide the same.

The process will continue

Step h : The setup will now be completed. Click on Finish

ADDITIONAL STEPS FOR MIGRATION USECASE WITHOUT TECH PROVIDER-

[These steps will not be needed in Tech Provider migration case mentioned above, since it will be like a fresh number onboarding - Disruptive approach]

Step i : 

Now ask the business to go to the Facebook Business portfolio and go to WhatsApp accounts.

Select the phone number, you will see both PMAs (BSP names) under Messaging accounts.

Step j : Now click on 'Conversation Routing' and click on 'Manage'

Step k : Click on manage and select 'ODCEM' or 'Gupshup' in all the dropdowns below.

--- Steps for business on Facebook get completed here ------

Step 5 :  The Waba ID (PMA ID) will prepopulate. Select the phone number and continue - 

Also turn on the toggle for 'Migrate templates from another provider' in case of migration 

Enter the source WABA ID (in case of migration to copy templates)

 

The process of Gupshup setup will begin

Now the setup is completed

PREVIEW OF BUSINESS MANAGER (Not visible to BSP / Tech Provider, but only to BUSINESS)

Below is the preview for a new phone number onboarding - where only 1 PMA is added, thus not showing 'Conversation routing configuration'

Below is the preview for a migration onboarding - where only 1 PMA is added, thus not showing 'Conversation routing configuration'