Skip to main content
After you send a WhatsApp message, Meta reports its progress: sent (it left Meta’s servers), delivered (it reached the customer’s phone), read (the customer opened the chat with it on screen) or failed (it couldn’t be sent or delivered, with an error code). A message can also be held while WhatsApp checks early feedback on a new template. If WhatsApp can’t deliver a message, it keeps trying for 30 days, or 10 minutes for authentication templates, and then drops it.
In Flowella. Supported. The Inbox shows each status as ticks under your message, and the failure reason under a failed one. The template’s Send log, Results and HubSpot’s Message Read and Message Sent triggers use the same statuses. See Delivery ticks on your messages.

What each status means

Meta sends read only after delivered. If the customer has the chat open when the message arrives, Meta can send read without a separate delivered. Meta also reports played, the first time a customer plays a voice message. Flowella doesn’t show it.

Why a message stays on one tick

One tick means Meta sent the message but the customer’s phone hasn’t received it. Common reasons:
  • The phone is off, has no signal or has no data.
  • WhatsApp is closed and the phone is restricting it in the background.
  • The customer hasn’t opened WhatsApp for a while.
WhatsApp keeps trying for up to 30 days (10 minutes for authentication templates). If the message isn’t delivered in that time, WhatsApp drops it without a further status. Treat a message that’s had no delivered status for 30 days as not delivered. A message that stays on two grey ticks was delivered but not yet read. Meta doesn’t document how a customer’s own read-receipt setting affects the read status, so treat a missing read as unconfirmed, not unread.

Order and timing

  • WhatsApp doesn’t guarantee that messages arrive in the order you sent them. If order matters, wait for delivered before you send the next one.
  • A failed status can arrive a little after the send, not straight away.
  • Meta refuses some messages as they’re sent, for example a template whose values don’t fit it, or a send above your number’s throughput. Those fail at once, with no sent status.

Pricing and statuses

Since 1 July 2025, WhatsApp charges per delivered message. Meta adds pricing details to the sent status and to one of delivered or read. Flowella counts a message towards your allowance only when Meta marks it billable. A failed or dropped message isn’t charged. See Pricing and categories.

Customer edits, deletions and reactions

Customers can react to your messages with an emoji, and they can edit or delete messages they sent you. Meta tells businesses about edits and deletions only on co-existence numbers, which are also used in the WhatsApp Business app. On those numbers, Meta currently reports edits as an unsupported message rather than an edit, while it restores edit support. On other numbers, the Inbox keeps the original message even if the customer edits or deletes it in WhatsApp.

Messages not delivered

Work out why a message didn’t arrive.

WhatsApp error codes

What each failure code means.

Template pacing and pausing

Why WhatsApp holds some messages.

Results

Delivery, read and failure rates over time.
Checked against Meta’s Status messages webhook, Service messages and Template pacing pages on 18 November 2026.
Last modified on November 18, 2026