Number portability in WhatsApp API

If you've made it this far, it's already time to bring your number to Take and start serving your customers in a Blip!

The porting process is quite simple and works like this:

Step 1 - Do the validations and send the information that was requested in this tutorial

Step 2 - According to our team's feedback, we will schedule a call to perform the number portability

Step 3 - Enjoy!

Now that you understand how it works, we can start!

Validations! First of all, make sure

• Your number's two-factor authentication has been removed: request the removal of the number's two-factor authentication from your old BSP (Official Facebook Provider) before we start the process;
• Also request the amount of shards that is present in the availability and scaling structure of the other BSP and inform this number to Take.Ser who will support you in the activation process. In case it is not possible to obtain this information, don't worry.
• That you have administrator access to the Facebook Business Manager that was used for the activation of your number with the other BSP (Official Facebook Provider);

⚠️ This point is very important! Without this access, it is not possible to port your phone number. If you are unsure if you have the correct access, confirm with the other BSP which Business Manager ID was used to create your WhatsApp account.

• Have a chatbot flow already built, because once migrated, the number will already be active on WhatsApp and without the flow, the customer is left without a response.
• That you backup all conversations and contact lists linked to another platform where your number is active, because Blip does not recover the history of messages and/or contact lists.
  
  There you go! Now that you have done the above validations, when asked by Take.Ser who will help you in the process of activating your WhatsApp in Blip, you must provide:

• The number of shards (if possible);
• The ID of the router chatbot in Blip, which centralizes all conversational flow (step 1 of this tutorial).
• The Facebook Business Manager ID that was used for activation on the other platform (step 2 of this tutorial).
• The phone number that will be migrated.
  
  ⚠️Attention: To perform the porting, you will need to confirm a code that will be sent to you by voice call or SMS. Therefore, the number to be migrated must be connected to a phone (fixed or mobile) and if the method chosen to receive the code is via voice call, the number must be able to receive international calls and cannot have an active IVR (you can deactivate it only during the porting process and activate it again later) and any call forwarding must already be configured, ok?
  
  FAQ
• Does the conversational flow of the intelligent contact need to be finalized and published?
  Yes. To do the migration, the chatbot's flow needs to be finalized and published, the service teams must be registered and trained to use Blip Desk. Once migrated, the number will be connected to Blip. Since the number was being used on WhatsApp previously, it is already known to the brand's customers.
• Do I have to disconnect the number to migrate?
  No. The number stays connected during the migration process.
• When migrating a number to a WABA created in Embedded, will there be a sandbox?
  There will be no sandbox, since everything (Company Verification, WABA and display name) have already been approved.
• Is there any downtime during the number migration process?
  Yes. Every migration has downtime, so the customer should prepare for the downtime (approximately 10 minutes).
• A migrated number:
  Keeps the same display name
  The official account seal
  Quality status
  Message limits
  Any pre approved, high quality messaging templates

If you want to learn more about the porting process, you can go to Facebook's documentation on number migration between WhatsApp API accounts.
Continue the conversation in the Blip Forum! Our Blipper Community is ready to help you!

Translated with www.DeepL.com/Translator (free version)