Reading the Beacon Messenger dashboard: sent, delivered, failed, skipped

What the four This month numbers on the Beacon Messenger home page count, why they rarely add up to the same total, and what to do when failed or skipped climbs.

The Beacon Messenger home page opens with four numbers under the heading This month: Messages sent, Delivered, Failed and Skipped. They look like a funnel. They are not quite one, and reading them as if they were leads to the wrong worry. This post explains what each tile counts, why they do not sum, what the recent messages table adds, and which number deserves attention when it moves.

The month is a UTC month

All four tiles cover the current calendar month in UTC, starting at midnight on the first. A store in Buenos Aires sees the counters reset at 9 pm on the last day of the month, not at midnight local time. The reset is not a bug and it is not tied to your billing date; it is simply the period the monthly message limit is counted in, so the dashboard shows the same window.

Messages sent

The first tile is the one the plan limit applies to. It counts messages Beacon Messenger handed to WhatsApp successfully this month. It is kept as a running counter that increments at the moment a send is accepted, rather than being recomputed from the message log, which is why it matches the limit exactly and why a message that later fails on the WhatsApp side still counts here: it was sent, and the send is what uses up the allowance.

Under the number the tile shows the limit for your plan, for example of 500 on Starter, or Unlimited. A progress bar below the tiles shows the percentage used, with a reminder that Beacon Messenger never sends past the limit and never charges usage fees. When the limit is reached the bar is replaced by a banner saying automations are paused until next month and that new messages are logged as skipped. The free plan post covers why the app is built to stop rather than to bill overage.

Delivered

Delivered counts messages created this month whose current status is delivered or read. The small text under it shows how many of those are read. A message starts as sent, moves to delivered when WhatsApp confirms it reached the phone, and to read when the customer opens it, if their read receipts are on. Each step arrives as a separate status update from Meta, usually within seconds but sometimes minutes later, which is the first reason the tiles do not sum: a message sent thirty seconds ago is in Messages sent but not yet in Delivered.

The gap between delivered and read is not a problem to fix. Customers with read receipts off never produce a read status, and a message that was delivered and acted on (an order confirmation glanced at in a notification) can stay at delivered forever. Treat read as a floor on how many people saw the message, not a ceiling. The message log post covers finding one message and reading its status history.

Failed

Failed counts messages that were sent and later rejected by WhatsApp. The number was in Messages sent first; a failure is a status change, not a different kind of message. Typical causes are a phone number that is not on WhatsApp, a customer who has blocked the business number, a template that was paused by Meta, or a quality or messaging limit on the business account. The message detail page shows the error code and text from Meta for each one.

A failed message does not refund the send against the monthly limit. The attempt was real and WhatsApp counted it too. What matters is the rate: a handful of failures on a few hundred sends is normal churn of wrong numbers. A sudden run of failures in one day almost always points at the template or the account rather than at customers, and it is worth opening the newest failed message to read the error before anything else.

Skipped

Skipped is the tile most often misread. These are not failed sends; they are orders or events where an automation ran and decided, before calling WhatsApp, not to send. Nothing left the app and nothing was counted against the limit. The hint under the number lists the usual reasons: no phone, no consent, over limit.

  • No phone number on the order, or a number that cannot be normalised to international format; see the no phone number post.
  • No marketing consent, for automations that require it such as the abandoned checkout reminder. Transactional messages do not check this.
  • Monthly limit reached, in which case every subsequent event this month is skipped with that reason.
  • Automation disabled, or no template chosen for it, or the template no longer found on the WhatsApp account.
  • WhatsApp not connected, which happens after a token expires or a disconnect.
  • Duplicate: the same event was already handled, so the second copy is dropped rather than sent twice.

Because each skipped message records its reason, the tile is a diagnostic. Open the messages page, filter to skipped, and the reasons tell you whether the fix is in checkout (collect phone numbers), in consent (see the consent post), in your plan, or in the automation settings. Skipped for no consent is usually fine and expected; skipped for no template or not connected means an automation you think is running is not.

Why the four numbers do not add up

What each tile counts
TileCountsUses the monthly limit
Messages sentSends accepted by WhatsApp this month, including ones that later failedYes
DeliveredMessages from this month now at delivered or readAlready counted in sent
FailedMessages from this month now at failedAlready counted in sent
SkippedEvents where the automation chose not to sendNo

So Delivered plus Failed is at most Messages sent, with the difference being messages still at sent and waiting on a status update, plus any queued messages that have a delay configured and have not gone out yet. Skipped sits beside the other three, not inside them. A dashboard reading sent 312, delivered 290, failed 9, skipped 41 describes 312 real sends of which 13 are still in flight, and 41 events that never became sends.

The recent messages table

Below the tiles the home page lists the eight newest messages: the automation and order number, the recipient name and number, a status badge and a relative time such as 4 min ago. It is the fastest way to confirm that an order you just placed as a test actually produced a message, and to see at a glance whether the newest entries are green or not. The View all messages link opens the full log with filters.

A pattern worth recognising: several consecutive rows all skipped with the same reason. That is one of the configuration skips above, and it will continue until the cause is fixed. Several rows all failed with the same error code is a WhatsApp account or template issue. Mixed statuses in no particular order is a healthy store.

Status and plan asides

To the right of the tiles the Status card shows whether WhatsApp is connected and on which number, whether the chat button is on and how many agents it has, and how many automations are enabled, by name. If Skipped is climbing, this is the first place to look: a disconnected account or an automation with no template shows up here without opening the messages log.

The Plan card repeats the plan name and the limit. Until WhatsApp is connected, the chat button is on and at least one automation is enabled, a Get set up checklist sits above the tiles and the numbers are all zero, which is the dashboard telling you nothing can happen yet rather than that something went wrong.

What to watch, in order

  1. Skipped reasons other than no consent. They mean an automation is not doing what you think.
  2. Failed as a share of sent. A few percent is normal; a spike in one day is a template or account problem.
  3. Messages sent against the limit, around the 80% mark. Past that the app will start skipping, and the first you hear of it from customers is silence.
  4. Delivered as a sanity check. If it stays far below sent for more than a few minutes, status updates from Meta are not arriving and the webhook configuration needs checking.

Frequently asked questions

Why does the dashboard show fewer sent messages than my WhatsApp Manager?

WhatsApp Manager counts every conversation on the business number, including replies and messages sent by other tools or by hand. The dashboard counts only messages Beacon Messenger sent this UTC month. Agent replies through the chat button are also not automations and are not in the tile.

Do skipped messages count against my monthly limit?

No. A skipped message is one the app decided not to send, so no call was made to WhatsApp and nothing is counted or billed. Only accepted sends increment the counter, including sends that later fail on the WhatsApp side.

When does the This month counter reset?

At midnight UTC on the first day of each calendar month. It is not tied to the date you subscribed. Stores far from UTC see the reset in the evening or early morning of their local last or first day.

A message shows as sent but never delivered. Did the customer get it?

Probably not yet. Sent means WhatsApp accepted it; delivered means it reached the phone. A phone that is off or without data holds the message at sent until it reconnects. If it never moves, the number may not be on WhatsApp, in which case Meta usually reports a failure after some time.

More guides