Finding one WhatsApp message in the Beacon Messenger log

How to find one WhatsApp notification in the Beacon Messenger log: what the search box matches, the status and automation filters, and when Retry appears.

The question arrives in the support inbox as a single line: did order #1042 get its WhatsApp? Sometimes it is the customer asking, sometimes a colleague, sometimes you at eleven at night wondering whether the shipping template went out before the carrier picked up. The answer is on the Messages page of Beacon Messenger, and it takes about ten seconds to find once you know what the search box actually matches and what the two filters next to it do. This post is that ten seconds, written down.

What the page shows

The Messages page lists every message the app has attempted for your shop, newest first, fifty to a page. Each row carries the automation that produced it (order confirmation, shipping update, cash-on-delivery check, abandoned checkout, or a test message), the phone number it went to, the customer and order it belongs to, the template that was used, the current status, and the timestamps of when it was created and last updated. A row with something to explain shows more: the skip reason for a skipped message, the error code and text returned by WhatsApp for a failed one, the customer's reply if there was one, and the WhatsApp message id that Meta assigned.

At the top of the list is a count of messages matching the current filters and, when there is anything waiting, a second figure such as 3 scheduled. Scheduled messages are the ones sitting in the delay queue, typically abandoned checkout reminders that have not reached their send time yet. They are not in the log until they are attempted, which is why a reminder you expect to see can be in the count but not in the table.

What the search box matches

The search field says Order, customer or phone, and it means exactly those three things, matched in three different ways.

  • Order name. Type 1042 or #1042 and the search matches order names that contain it, case insensitive. Because it is a contains match, 104 also finds #1040 through #1049, which is occasionally useful and occasionally surprising.
  • Customer name. A contains match on the name stored with the message, so a first name, a surname or part of either works. Accents have to match the way the customer typed them at checkout.
  • Phone number. The app strips everything that is not a digit from what you typed and looks for that digit string inside the recipient number. So +54 9 11 2345-6789, 5491123456789 and 2345 6789 all find the same message, and you can paste a number straight out of a WhatsApp conversation, spaces and brackets included.

The three run together as one search, so a term is matched against all three fields at once. Typing a short number such as 11 therefore finds orders #1100 to #1199 as well as every Buenos Aires phone number; add a few more digits and the list collapses to what you meant.

The two filters

Next to the search are Status and Automation. Status has six values, and they are the six states a message can be in: queued, meaning accepted by the app and about to be sent; sent, meaning WhatsApp accepted it; delivered and read, which arrive later as WhatsApp reports them; failed, meaning WhatsApp rejected it or the request errored; and skipped, meaning the app decided not to send it at all and recorded why. The delivery guide explains how a message moves between the first four.

Automation narrows the list to one trigger. Combined with Status it answers the operational questions directly: failed plus shipping update is your list of customers who did not get a tracking link today; skipped plus cash on delivery shows every COD order the app chose not to message, each with its reason. The filters and the search stack, so failed, shipping update, and 1042 finds the one row you were asked about.

Three questions and the search that answers them
QuestionSearchStatusAutomation
Did #1042 get its shipping message?1042AllShipping update
What went to this phone number?the number, any formatAllAll
Which COD checks were skipped this week?emptySkippedCash on delivery

When Retry appears, and what it does

A Retry button shows on a row when three things are true: the status is failed or skipped, the app still has the order context it built the original message from, and the message came from a real automation rather than a test. Retry does not resend the same request. It rebuilds the message from the stored context against the current template, so if the failure was a rejected template that you have since fixed, or a skip caused by a missing phone number you have since added to the order, the retry picks up the fix.

The retry runs immediately and is marked as the final attempt, so there is no further automatic retrying behind it; if it fails again you will see a fresh error on the row and can decide what to do with the facts in front of you. The result comes back as a toast: Message sent, or a note that the message is still skipped or still failed and that the details are on the row. Retrying a skipped message is the one place where the app will send something it previously chose not to, so it waits for a person to press the button.

Who looked at what

Every view of the Messages page is written to the access log, including the search term and filters that were active, because the page shows phone numbers and names. That is covered in detail in who viewed customer phone numbers. The practical upshot for a support team: searching for a customer's number to answer their question is normal and expected, and it leaves a record that says exactly that.

If a message you are certain should exist is not in the log at all, with any filter, the app never attempted it, and the reasons live elsewhere: the order did not meet the trigger conditions, the automation was off, or the webhook did not arrive. Which orders trigger messages is the checklist for that case. The log is the record of what the app tried; the absence of a row is the clue that it never got that far.

Frequently asked questions

Can I search the message log by email address?

No. The log search matches order name, customer name and phone number digits. Find the order in Shopify by email first, then search the log by the order number, which is usually faster anyway.

Why does a scheduled abandoned checkout reminder not appear in the log?

Messages waiting for their delay are counted as scheduled at the top of the page but are not log rows yet. A row is written when the app actually attempts the send, with whatever status that attempt produced, including skipped if the checkout was completed in the meantime.

Why is there no Retry button on a failed test message?

Test messages are sent from the connection checklist and exist only to prove the connection works, so retrying one from the log would not tell you anything new. Send another test from the settings page instead. Retry is reserved for failed or skipped messages produced by a real automation that still have their order context.

Does retrying a message send a duplicate if the first one actually arrived?

Retry is only offered on rows in failed or skipped status, which are messages WhatsApp never accepted or the app never sent. A message that reached sent, delivered or read cannot be retried from the log, precisely to avoid sending the customer the same notification twice.

More guides