WhatsApp Business not receiving messages: why the business can't see what customers send

If you ended up here, it's because your WhatsApp Business stopped showing the messages customers send you: the person swears they wrote to you, you see nothing, and the chat doesn't appear on either the phone or the computer. It's not an API error with a strange code: it's a configuration or usage problem, and in most cases you can check it yourself without being technical. The bad news is that there isn't a single cause: there are at least six different situations that produce exactly the same symptom. The good news is that they can be ruled out one by one, in order, without touching a single line of code.

Before starting, an important clarification: WhatsApp doesn't notify you when a message doesn't arrive. On the customer's side the message goes out with one checkmark, sometimes two, and on yours nothing happens. That makes the problem get discovered late, when the customer is already upset. That's why it's best to treat it as a configuration review and not as a one-off error.

What it means exactly that you're not receiving messages

It means that the number your customers are using to write to you is not the same number your inbox is looking at, or that number is in a state that doesn't allow receiving. There's no silent failure by Meta: there's always a concrete reason. The job is to find which of the possible reasons applies to your case.

There's a very common confusion worth clearing up first. WhatsApp Business (the free app you install on your phone) and Meta's official WhatsApp API (the channel through which software like Wando connects to the number) are two different things. The same number can't be active on both at the same time. If the number is registered on the API, the phone app stops receiving messages, and vice versa. A huge number of "I'm not receiving messages" cases are actually this: someone connected the number to a platform and kept expecting to see the chats in the phone app.

Why it happens: the most frequent causes, in order of probability

These are the causes that explain the vast majority of cases. They're not in order of severity but of frequency: the first ones are the ones that most often turn out to be the explanation.

• The number is connected to the official API and you're still looking at the phone app. Messages arrive, but somewhere else. It's the number one cause and the easiest to verify.
• The number was registered twice. Someone registered it on the API and also has it open in the WhatsApp Business app on a phone. Meta only allows one active session per number; the one that stays active is the last one registered, and the other stops seeing everything without warning.
• The phone number you publish is not the one connected. This happens when the business changed numbers, added a new line, or has an old number on the website, on Google, or on Instagram, and the new number is the one on the platform. Customers write to the old one.
• The phone running the app lost connection or ran out of battery and nobody noticed. If the number still lives in the phone app, that phone must be on and connected to the internet to receive. If it turned off, messages wait and sometimes never arrive.
• The app is outdated or the session closed on its own. Old versions of WhatsApp Business stop syncing without showing a visible error.
• The customer wrote to you on a channel that isn't WhatsApp. Instagram, Messenger, and WhatsApp are different channels. If someone writes to you on Instagram and you expect to see it on WhatsApp, it won't appear.

How to check it step by step, without being technical

Do these steps in order. Don't skip any: each one rules out a cause and gets you closer to the one that applies to your case. If at any step you find something strange, write it down before continuing, because it may be the answer.

1. 1Find out which number your customers write to. Look at the website, the Google profile, the Instagram bio, and the last status you posted. Write down that number exactly as the customer sees it, with country code.
2. 2Find out which number is actually connected. If you use a platform, go to the channel settings and look at the number listed there. If you use the app, open WhatsApp Business → Settings → and look at the number at the top of the profile.
3. 3Compare the two numbers. If they don't match, you already have the cause: your customers write to a number that isn't connected to anything. Fix the website, the Google profile, and the social networks so they show the number that does receive.
4. 4If the numbers match, check whether the number is in the phone app or on a platform. If it's on a platform (official API), don't look for it in the app: messages will never appear there.
5. 5If the number is in the phone app, check that the phone is on, connected to the internet, and has the app open at least once a day. Try sending yourself a message from another number of yours and see if it arrives.
6. 6If the number is on a platform, check the channel connection status. Most platforms show whether the channel is active, disconnected, or pending. A disconnected channel receives nothing.
7. 7If the channel shows as active and you still don't see messages, check whether there is more than one agent or more than one inbox. On teams with several people, it's common for a colleague to be seeing the chat and you not, because it's assigned to another inbox.
8. 8If after all this you still don't see the messages, switch channels to test: ask someone to write to you on WhatsApp and, at the same time, test that a message arrives on Instagram or Messenger if you have those channels connected. If it does arrive on the other channels, the problem is specifically on WhatsApp and not on your platform.
9. 9If none of the above works, gather the evidence before escalating: exact number, date and time of the message that didn't arrive, screenshot of the customer's chat, and screenshot of your inbox. With that, your platform's support or Meta's support can review the specific case. How long it takes to resolve varies by case and can't be promised in advance.

How to prevent it from happening again

The problem of messages that don't arrive is almost never an isolated event: it's the result of a poorly documented number or a duplicated session that nobody controls. These are the practices that prevent it from repeating.

• Have a single official number and always write it the same way everywhere: website, Google, Instagram, email signature, quotes. A different number on each channel is the most common cause of lost messages.
• Before connecting a number to the official API, make sure no one else is using it in the phone app. One number, one session.
• If you change numbers, update all channels the same day. An old number published on the website keeps receiving inquiries you'll never see.
• If the number lives in the phone app, keep that phone always on, connected to the internet, and with the app updated. It's not a personal phone: it's the business line.
• Check once a month that the channel is still active and that the connected number is the correct one. It's a two-minute check that prevents losing customers.
• If you have several people handling messages, define who looks at which inbox. On teams with multiple agents, messages aren't lost: they're assigned to someone. If nobody knows to whom, it seems like they didn't arrive.

When the real problem is something else and this symptom is just the tip

There are situations where "I'm not receiving messages" is true but it's not the problem. Messages arrive at the platform just fine, and what's failing is something else. It's worth ruling these out because they completely change what needs to be fixed.

• Messages arrive but nobody answers them. If the team doesn't have a shared inbox or a way to know what's still pending, messages pile up and two days later it looks like they never arrived. The problem is process, not connection.
• Messages arrive but they're outside business hours. If you set up auto-replies by schedule, the customer gets an automatic response and the message is saved for when you're back. It wasn't lost: it's waiting.
• Messages arrive but the customer wrote to a channel you're not watching. Instagram and Messenger are separate channels from WhatsApp. If you have them connected but nobody checks them, it's as if they didn't exist.
• The customer says they wrote but never hit send. It happens more than people admit, especially when someone writes from a computer with WhatsApp Web and closes the tab before sending. Ask for a screenshot of the chat with the message time before assuming it was lost.
• The customer wrote to a number you no longer use. If you have an old number published somewhere, messages keep going there. Check the website, the Google profile, old quotes and Instagram highlights.

What to do if the number is on the official API and you don't see the messages in the app

This is the case that confuses people the most, and it deserves its own section. When a number is connected to Meta's official WhatsApp API, the phone app stops receiving messages for that number. It's not an error: it's how it works. Messages go to the platform that's connected to the API.

If you're not seeing the messages anywhere, then the problem isn't the app: it's that the platform isn't showing them. There you should check three things: that the channel shows as active, that the connected number is the one your customers are using, and that your user has permission to see that inbox. All three are checked from the dashboard, without touching anything technical.

Tools like Wando show messages in a shared inbox and suggest AI replies that the team approves with one click. If the number is connected there and you still don't see anything, the check is the same one we did above: number, channel and permissions. The tool doesn't change the diagnosis.

Configuration errors that look similar but aren't this

There are other WhatsApp Business problems that produce similar symptoms, and it's best not to mix them up, because the solution is different. We name them by situation, not by number, precisely so you don't confuse them.

• When the access token expired: incoming messages may still arrive, but automatic replies or campaigns stop going out. The symptom is different: it's not that you don't see messages, it's that you can't send. When a template was rejected: the problem appears when sending campaigns or messages outside the 24-hour window, not when receiving. Template approval can take up to 48 hours according to Meta. When the number was placed under review or restricted: it may temporarily stop receiving or sending. This is decided by Meta on a case-by-case basis and there is no guaranteed timeframe; you need to check the number's status in the Meta dashboard. When the webhook stopped responding: messages reach Meta but don't show up in your platform. This is a technical problem that generally requires support; the business owner can't fix it from the dashboard.

Quick checklist to print or save

• Is the number you publish the same one that's connected?
• Is the number in the phone app or in the official API?
• If it's in the app: is the phone on, with internet, and with the app updated?
• If it's in the API: does the channel show as active on the platform?
• Is more than one person handling it, and is the chat assigned to another inbox?
• Did the customer write via WhatsApp or via another channel (Instagram, Messenger)?
• Do you have a screenshot of the customer's chat with date and time?
• If none of this solves it: gather the number, screenshots, and times, and escalate to support.

What you can't solve yourself and should escalate

There is a clear line between what the business owner checks and what needs support. If, after going through the checklist, the number matches, the channel shows as active, the phone is on, and messages still don't arrive, the problem is on Meta's side or the platform's side, and it can't be fixed from the dashboard.

In that case, gather concrete evidence before writing: exact number, date and time of the message that didn't arrive, screenshot of the customer's chat, and screenshot of your inbox. The more specific the case, the faster whoever assists you can review it. Resolution time depends on each situation and there is no way to promise it in advance.