Message not delivered
How to read a failure — opt-outs, bad numbers, the 24-hour window — and where every error code is explained.
First: read the exact status
Open the campaign (or conversation) and the recipient's row. The status tells you which of these you are in:
- Stuck at Sent — the network has the message but no delivery confirmation came back. Usually a phone that is off or out of coverage. Give it a day before worrying; many arrive when the phone returns.
- Failed with an error code — the network refused the message. The row shows the code and a short reason; the Best Practices page has a searchable explanation for every code.
The common causes, most likely first
- The contact opted out. A STOP/UNSUBSCRIBE reply opts a number out for your whole organization, permanently and by design. Opted-out contacts are skipped at send time — check the contact's consent record.
- The number is not reachable — wrong format, a landline, or no WhatsApp account. The audience import scores reachability for exactly this; invalid numbers can be excluded from any campaign.
- Wrong route — on WhatsApp there is no SMS fallback: if the app cannot deliver, the message fails (on RCS channels the same message may have fallen back to SMS instead).
- The 24-hour window closed. Free-form replies from the Inbox only work within 24 hours of the contact's last message. Past it, send an approved template.
Still stuck?
Note the error code and the affected numbers, and contact support — the fastest fix is a message that includes the code.
Last reviewed September 12, 2026
Was this page helpful?