Why incoming WhatsApp messages aren't arriving
A step-by-step diagnosis when customers message you on WhatsApp but the messages never show up in your Omnifox inbox.
When to use this article
Customers message you on WhatsApp, they see the message as sent, but it never shows up in your Omnifox inbox. The cause is almost always one of three layers: Meta's webhook, a mis-routed number/channel, or the wrong workspace. This guide is for channel admins.
Before you start
- You need an admin role and access to WhatsApp Manager in Meta Business.
- Have the affected number and the channel ID ready (in Channels, the "Copy channel ID" button).
Step-by-step diagnosis
- Confirm the channel is Connected. Open Channels. If the number shows Disconnected or an alert, its token expired (Meta error 190). Reconnect it through Embedded Signup.
- Check the webhook points to Omnifox. In Meta → your app → WhatsApp → Configuration, the webhook must point to the Omnifox endpoint and be subscribed to the
messagesfield. If another tool hijacked the webhook, inbound messages go there, not to you. - Make sure the number delivers to a single destination. A given number (phone number ID) can only deliver to one app/webhook. If you connected it elsewhere before, unlink it there.
- Confirm the right workspace. The channel belongs to a specific workspace. If you're viewing a different workspace in Omnifox, the messages exist but you don't see them. Switch workspace at the top left.
- Rule out blocking/opt-out. Inbound always arrives, but if the contact was marked blocked or spam on your side, it can be filtered. Look it up under Contacts.
Verification
Ask someone to send you a fresh WhatsApp. It should hit the inbox within seconds. If not, force a channel check: in the Channels panel use "Re-activate channel" to trigger an immediate health check.
If it still doesn't arrive
- Webhook green in Meta but nothing in Omnifox: the
messagesfield is likely not subscribed, or the number delivers to another app. Re-configure the webhook. - Arrives for one number, not another: each number is an independent channel; check the specific channel, not the first one in the list.
- It used to arrive and stopped: almost always an expired token (190) or the number got re-paired in another tool. Reconnect.
- Coexistence: if you run the channel in Coexistence mode, messages typed from the phone app must also sync; check the channel's sync indicator.
Tips
- Never connect the same number in two platforms at once: the webhook is exclusive and they fight over inbound.
- After reconnecting, always send a real test message before calling it resolved.
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.