What happens when a contact changes their WhatsApp number
When a customer moves their WhatsApp account to a new number, Omnifox updates the contact and keeps the whole conversation automatically.
What it is
When one of your customers moves their WhatsApp account to a different phone number, Meta notifies Omnifox with a system event. Omnifox automatically migrates the contact's identity to the new number and keeps the entire conversation: no duplicate contact is created and no history is lost.
This article explains what you'll see in the Inbox and what to do (usually nothing).
When it applies
- The customer keeps their WhatsApp account but ties it to another number (new SIM, portability, etc.).
- Your workspace's WhatsApp channel is connected through Meta's API (Cloud API or Coexistence).
What Omnifox does automatically
- Detects the event. Meta sends a
user_changed_numberevent carrying the old and new numbers. - Reassigns the identity. The contact's WhatsApp identifier (wa_id) is updated to the new number.
- Merges duplicates. If a separate contact already existed for the new number, Omnifox merges them: it re-links conversations, identities, and custom fields, and writes a merge record.
- Keeps the conversation. The open conversation stays the same, with every previous message intact.
- Drops a system message inside the chat, e.g. "📱 Customer changed their WhatsApp number from +1… to +1…", so the agent has a clear audit trail.
How to verify it
- Open the customer's conversation in Inbox.
- Look for the system message with the 📱 icon showing the old and new numbers.
- Open the contact panel (on the right) and confirm the phone number is already the new one.
- Check that the earlier history is still visible in the same thread.
If it doesn't work
- I don't see the system message: Meta only sends the event when the customer migrated the same account to a new number. If they created a brand-new account, it arrives as a new contact (no history), because to Meta it's a different person.
- Two separate contacts appear: this happens when the old number wasn't resolvable at the moment of the event. You can join them manually from the contact using merge contacts.
- Old history not migrated (Coexistence channels): an admin can reconcile past changes with the
whatsapp:fix-changed-numberscommand, which applies the same migration logic to historical events.
Tips
- Don't hand-edit the contact's number when the notice arrives: Omnifox already updated it. Editing in parallel can create inconsistencies.
- A merge is permanent. Before manually merging two contacts, make sure they really are the same person.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.