This process will help to prepare for migrating the phone numbers that have not been migrated to Cloud API yet because of a phone-number mismatch. This process is only for updating the Source Phone numbers and not recipient numbers with mismatch.
For other things to keep in mind for Cloud API migration, refer this article.
NOTE: In case it is not handled correctly while migration it may have lead to disruption of messaging.
STEPS TO PREPARE FOR MIGRATION -
- Make note of the planned date and time for migration with Gupshup team (the time planned should be of low-volume window to not impact messaging during the changes, however downtime can be expected for up to 60 minutes)
- Once date and time is known, ensure that your DB is updated with the Meta PN (instead of Current PN) at the same time. After migration, Gupshup’s DB will store the exact phone number format as provided by Meta. This may differ from the format in your current database. Hence follow below steps for updating -
a. Identify the Updated Source Phone Number: Current PN and Meta PN both would have been shared with you before migration. If not shared with you, please reach out to aig.product@gupshup.io or your local CSM.
b. Update Database or Integrations: Update your systems/DB with the revised source phone number that matches the Gupshup DB at the decided time. The updated source phone number should be the 'Meta PN'
Example:
- The current number in Gupshup DB which you were setting as source while on -prem was - 553111100000. Post migration Gupshup receives the number as 5531911100000 (Meta PN), we will update this number in our DB and you must ensure your system reflects the same format. - Gupshup team will inform you once the migration is completed
- Perform outgoing and incoming test messages to confirm that the updated phone numbers in your database work as intended through the Gupshup platform. Inbound messaging will largely be handled by Meta’s infrastructure, requiring minimal action from you. However please note that if an end-user sends messages to the business phone number with or without extra digits (e.g., an additional 9 or 1 in Brazil and Mexico), Meta will automatically redirect the conversation to the updated Meta PN which you should receive. The message events will be forwarded successfully to your system without manual intervention.
REPORT ISSUE : Post migration, for any edge cases where unexpected behavior occurs or messaging does not function as expected post migration please report them to support immediately with subject line 'Urgent : Mismatch PN migrated issue' and keep aig.product@gupshup.io or your local CSM in CC.
By following these steps, you can minimize disruptions caused by phone number mismatches and ensure a seamless experience during the migration to WhatsApp’s Cloud API.
By following these steps, you can minimize disruptions caused by phone number mismatches and ensure a seamless experience during the migration to WhatsApp’s Cloud API.
Comments
0 comments
Please sign in to leave a comment.