A message was not delivered
Work the causes in order — the first four explain the large majority of failures and can be checked from the console in under two minutes.
- Status — queued, sent, failed or rejected. Each points at a different layer.
- Consent — a marketing send to an opted-out contact is blocked before dispatch.
- Sender and template — sender registered for that country, template approved for that category.
- Window — on WhatsApp, non-template sends outside the 24-hour window are rejected.
- Escalate — with the message ID and timestamp, support can trace to carrier level.
Reading statuses
*Queued* is a throughput issue. *Sent but never delivered* is usually handset or carrier. *Rejected* is almost always sender, template or consent — a configuration problem on your side.
Steps at a glance
- Read the delivery statusOpen the conversation and check whether the message is queued, sent, failed or rejected.
- Check consentA marketing message to an opted-out contact is blocked before it leaves the platform.
- Check the sender and templateConfirm the sender is registered for the destination country and the template is approved for the category used.
- Check the messaging windowOn WhatsApp, a non-template message outside the 24-hour window is rejected.
- Escalate with the message IDIf all four are clean, raise a ticket with the message ID and timestamp for carrier-level tracing.
Next step
Bring this to your enterprise stack
See how a dedicated Arino One instance — deployed in your region (EU, NA or APAC) — would sit inside your operation. Architecture, DPA, and rollout plan walked through live.