Your WhatsApp message says sent. It was never delivered.
“Sent” means WhatsApp took the message from you. It says nothing about whether it reached anybody. Here is what each acknowledgement really means, the failures that produce a tick and no delivery, and how to find out which one you are looking at.
A dashboard that says Sent is telling you something narrower than it sounds. It means WhatsApp accepted the message from your software. It does not mean it reached a phone, and it certainly does not mean anybody saw it.
Most of the time the gap is milliseconds and the distinction is academic. Occasionally it is permanent, and a business spends a fortnight wondering why nobody replies to messages that all say “sent”.
What the ticks actually mean
| What you see | What happened | What it does not mean |
|---|---|---|
| A clock, or nothing | Your device has the message; WhatsApp does not | — |
| One grey tick | WhatsApp’s servers accepted it | That any device has it |
| Two grey ticks | It reached the recipient’s device | That anybody read it |
| Two blue ticks | It was opened | That it was read, strictly — the chat was on screen |
The important line is the second one. One tick is an acknowledgement from a server, and a server will happily acknowledge a message addressed to somebody who will never get it.
The failures that still show a tick
The number is not on WhatsApp
The commonest cause and the least suspected. A number that looks perfectly valid — right country code, right length, someone answers it when you call — may simply not have a WhatsApp account. Your message is accepted and goes nowhere.
Worth checking before a campaign rather than after: any decent tool can ask WhatsApp whether an account exists for a number, and the answer is free.
The number is right but the address is not
Countries renumber. Cameroon added a leading 6 to mobile numbers in 2016; other markets have done the same. An account registered before a renumbering and never re-verified can still be addressed by its old form — so the number printed on the business card is correct, and the address derived from it is not.
We hit this on our own test number. Messages were accepted, marked sent, and delivered nowhere, because the address derived from the modern number was not the one the account answered on. Nothing anywhere reported an error. The fix is to ask WhatsApp what address a number actually resolves to and store that, rather than deriving it and hoping.
The recipient blocked you
A blocked sender sees one tick forever. There is no error and no notification, by design — telling you would defeat the purpose. If a specific contact stopped receiving messages some time ago and everyone else is fine, this is usually why.
The phone is off, or has no space
Genuinely transient, and the one case where waiting works. WhatsApp holds undelivered messages for about 30 days. A phone that comes back online receives the backlog; a phone that never does means the message expires quietly.
Your own session is half-connected
The nastiest category, because everything looks healthy. A session can be attached enough to accept messages into a queue and not attached enough to deliver them. Ifeverything stopped being delivered at a particular moment, suspect this before suspecting your recipients.
How to tell which one you have
Work down this list; it is ordered by how often it is the answer.
- Is it one contact or all of them? One contact points at a block, a missing account, or a wrong address. All contacts points at your session.
- Does the number have WhatsApp at all? Check it rather than assume it. This eliminates a surprising share of “delivery problems”.
- Did it start at a moment? A clean cut-off is a session or an account restriction. A gradual decline is a reputation problem.
- Do you have a delivery receipt, or only an accept? If your tool cannot tell you the difference, that is worth knowing about your tool.
- Send to your own second number. Thirty seconds, and it separates “my sending is broken” from “this recipient is unreachable” definitively.
Why software reports this badly
Most messaging tools collapse several distinct states into one word. The message was queued, accepted, delivered, or it failed — and all four get rendered as “sent” because that is what the send call returned.
It is worth insisting on the distinction. A tool that marks a message delivered when it has only been accepted is inventing a receipt that never arrived, and the invented receipt is what hides a real failure for as long as it stays hidden.
Four states, and they are all different: queued (we have it), sent (WhatsApp has it), delivered (a device has it), read. Anything that cannot show you which one a message is in cannot answer the question this article is about.
Keeping it from happening
- Check numbers before a campaign, not after it underperforms.
- Store the address WhatsApp returns rather than one derived from the number, so a renumbered market does not silently swallow your messages.
- Alert on the gap between accepted and delivered. A number that suddenly delivers 60% of what it accepts has a problem that no error log will mention.
- Watch replies as well as delivery. Messages that arrive and are never answered are the signal WhatsApp weighs most heavily, and the one that precedes a restriction — see what to do when a number is banned.
Common questions
Why does my message show one tick for hours?
WhatsApp has the message but no device has collected it. The phone may be off or offline, or you may be blocked. If it clears after a few hours the phone was simply unreachable; if it never clears for one contact while others are fine, a block is the most likely explanation.
Does one tick mean I have been blocked?
Not on its own. A phone that is off produces exactly the same single tick. What distinguishes a block is that it persists for one specific contact across days while your messages to everybody else deliver normally.
Can I tell whether a number has WhatsApp before sending?
Yes. WhatsApp exposes a check for whether an account exists for a number, and any reasonable tool will expose it to you. Running it over a list before a campaign removes a whole class of mysterious non-delivery.
How long does WhatsApp keep an undelivered message?
About 30 days. A phone that comes back online within that window receives the backlog. After it, the message is dropped and the recipient never learns it existed.
My messages say sent but nobody replies. Is that a delivery problem?
Sometimes, and it is worth eliminating first by comparing accepted counts against delivered counts. But a healthy delivery rate with no replies is a message problem rather than a delivery problem — and sustained low reply rates are one of the strongest signals WhatsApp uses when deciding to restrict a number.