Partners can now migrate their OBO WABAS to Embedded Signup method through these APIs available here. Note : It is not mandatory for partners to migrate to Cloud API (CAPI) before transitioning to Embed Signup method. We highly recommend partners to complete TPP process so that the Solution ID can be passed to Meta for these WABAs and they do not have to do a separate migration to Solution ID in future.
Partners have to do it in below steps -
a. Recommended step (Optional): Complete TPP and then go to step B to tag Solution ID with the given WABA
b. Whitelist an OBO waba and get the Embed URL with the first API + share the URL with the customer ASAP. Ask customers to complete the Embed flow within 2 days and confirm the partner. There is NO webhook for the same at this point to inform the partner that flow is completed. (Refer below instructions to share with customer). Additionally customers will also receive a notification on their business manager which they can simply accept to complete the migration.
c. As soon as the customer completes the flow or accepts the notification, the partner must call the 2nd API to re-enforce the credit line. Also it will update in Metabase (internally).
NOTE: If a customer does not complete flow after whitelisting, in T+30 days (earlier 90days), the WABA will automatically be migrated to Embed. Also there will be no downtime during steps b and c.
HERE ARE THE STEPS FOR THE CUSTOMER ON CLICKING THE SHARED LINK IN STEP B ABOVE -
For every phone number, a link will be generated and shared with the customer. Admin of the FBM must follow the below steps to complete the conversion -
Step 1: Open the Link and Log In 🔗
- Action: Click on the link you received.
- Login: Use your Facebook Business Manager account to log in or continue.
-
Tips
Make sure you're logged into the correct account associated with your business. The client with admin rights should complete the embedded sign-up process.
During the sign-up, select the same BM ID and WABA ID used to create the OBO WABA, which needs to be changed.
Complete the entire signup flow - No OTP verification step will be asked in this case.
Step 2: Connect to Messaging Solution Provider 🤝
- Action: Connect your account to the Messaging Solution Provider.
- Permissions: You'll need to share account and billing permissions with the provider
Step 3: Fill in Your Business Information 📝
- Action: Enter your business information as prompted.
- Details: Complete all fields accurately to add your phone number.
- Note: Your audience will not see this information on your WhatsApp profile.
Step 4: Review and Confirm Requests ✅
- Action: Review requests mentioned
- Options: If you agree with the requests, confirm them; if not, click ignore and proceed with onboarding.
Step 5: Accept Permissions
- Action: Review the permissions requested
- Acceptance: Accept the permissions if they align with your needs.
- Tip: These permissions are necessary for a smooth migration and ongoing management.
Step 6: Complete Migration and Meta-Review 🔄
- Action: Once permissions are accepted, your migration is complete
By following these steps, you'll be able to successfully migrate your apps from OBO to Embedded Signup. If you have any questions or encounter any issues, please reach out for support.
If you are not working with a partner, please reach out to devsupport@gupshup.io for helping you migrate.
Comments
1 comment
Chat
Please sign in to leave a comment.