COD reply not tagged: how Beacon Messenger matches replies

A customer answered the cash-on-delivery message but the order has no tag. The five checks a WhatsApp reply must pass, which words count, and where to look.

The cash-on-delivery check is the one automation where the customer talks back, and that is also why it is the one that raises support tickets. The message went out, the customer wrote yes, and an hour later the order still has no beacon-cod-confirmed tag. Nothing is broken in most of these cases. A reply has to pass five checks before Beacon Messenger will touch the order, and each of them exists so the app never tags an order on the strength of a message it cannot tie to that order. This post walks through the five, in the order the app applies them, and ends with where to look in the message log.

1. The reply has to be a reply

WhatsApp tells the app which message a customer is answering only when the customer actually answers it: by tapping one of the template's buttons, or by long-pressing the message and choosing Reply. In both cases Meta attaches the original message's id to the incoming webhook. A fresh message typed into the thread carries no such reference, even if it says yes and arrives thirty seconds after the question.

The app does nothing with a message that has no reference. It cannot know which order the yes belongs to, and guessing (the most recent order, the only unconfirmed one) is exactly how the wrong order gets confirmed. This is the single biggest reason a reply goes unrecorded, and it is why the automation page warns when the template you picked has no reply buttons: a button tap always carries the reference, a typed yes often does not.

2. The original message has to be a COD check from your shop

With a reference in hand, the app looks up the original message in your message log by its WhatsApp id. It has to find a row that belongs to your shop and whose trigger was the cash-on-delivery confirmation. A customer who taps Reply on a shipping update and types yes is answering a message the app sent, but not a question, so the reply is ignored. The same goes for messages sent from WhatsApp Business directly rather than through an automation: they are not in the log, so there is nothing to match.

3. The number has to match

Every webhook from Meta names the phone number it arrived on. The app checks that this is the number connected to your shop before it reads anything else, and discards the event if not. If you have two numbers and the COD template went out from the one that is not connected to Beacon Messenger, the replies land somewhere the app never looks.

4. The text has to start with a word the app knows

Once the reply is tied to a COD message, the app decides what it means. It reads, in this order of preference: the payload of a tapped button, the visible text of that button, the id or title of an interactive reply, the title of a list choice, and finally the plain text the customer typed. Buttons win, which is another reason to use them: a button labelled Confirm order classifies the same way every time, whatever language the customer speaks.

Typed text is matched against two short lists, and the match is anchored to the start of the message. The first word has to be one of these:

Words the COD classifier recognises at the start of a reply
ResultRecognised first words
Confirmedconfirm, confirmed, confirmar, confirmo, yes, y, si, sí, ok, okay, sim, oui, ja, haan, ha, confirm order, ✅, 👍
Cancelledcancel, cancelled, cancelar, cancelo, no, nope, não, nao, non, nein, nahi, nahin, ❌, 👎
OtherAnything else, including a sentence that contains yes but does not begin with it

So Yes please and OK thanks are confirmations, and No, cancel it is a cancellation. I confirm, Sure, and Yes but can you deliver after 6pm are all Other, because the first word is not on the list or because the message starts with something else. Case does not matter. The anchor is deliberate: a reply like no problem, confirm it would otherwise be read as a cancellation, and the cost of a wrong tag is higher than the cost of a missed one.

5. Other is recorded, not acted on

A reply classified as Other is written to the message log against the original COD message, with the text the customer sent (trimmed to 200 characters), and nothing else happens: no tag, no acknowledgement. It is not lost. On the Messages page the original row shows a Reply badge with the classification and the text, so a Reply: other:Yes but can you deliver after 6pm line is a customer who did answer and needs a human to read it. Confirmed and cancelled replies show in the same place, which makes the badge the first thing to check when a tag is missing.

What happens when a reply passes

For a confirmed reply the app removes beacon-cod-cancelled from the order if it is there and adds beacon-cod-confirmed. For a cancelled reply it does the reverse. The removal comes first so an order never carries both tags, and so a customer who answers twice ends up with their latest answer. The app does not cancel the Shopify order, restock anything or refund anything; the tag is a signal for you, or for a Shopify Flow you build, as described in the COD guide.

Then the customer gets a short acknowledgement, in the language of the COD template you selected, confirming or cancelling with the order number. If the tag write fails, because the order was deleted or the app lost access, the failure is logged against the message and the acknowledgement still goes out, so the customer is never left waiting on your side of a problem.

A checklist for a missing tag

  1. Open Messages and find the COD row for the order. No Reply badge at all means the reply never reached the app: the customer typed a new message rather than replying, or it arrived on a different number.
  2. A badge reading other means the words were not recognised. Read the text and act on it by hand, then consider whether the template needs buttons.
  3. A badge reading confirmed or cancelled with no tag on the order means the tag write failed. The error is recorded on the same row.
  4. Check the automation page for the No reply buttons warning. Adding Confirm order and Cancel order buttons to the template, and waiting for Meta to approve them, removes most of the typed-text cases.
  5. If customers keep writing in a language whose words are not on the list, tell us. The lists are short on purpose and we add words when a market needs them.

Frequently asked questions

The customer wrote yes in the chat. Why was the order not tagged?

Most likely the yes was a new message rather than a reply to the COD message. WhatsApp only tells the app which message is being answered when the customer taps a button or uses Reply on it, and without that reference the app cannot tell which order the yes belongs to, so it leaves the order alone.

Does Beacon Messenger understand replies in Spanish, Portuguese or Hindi?

Yes, for a short list of first words in each: si, sí, confirmar and confirmo; sim; oui; ja; haan and ha for confirmations, and cancelar, cancelo, não, nao, non, nein, nahi and nahin for cancellations, plus thumbs-up, tick, thumbs-down and cross emoji. Anything else is recorded as other and left for you to read.

What does Reply: other mean on the Messages page?

The customer answered the COD message, the reply was tied to the right order, but the first word was not one the app recognises. The text is shown next to the badge so you can read it and tag or cancel the order yourself. No acknowledgement was sent for it.

Can a customer change their answer?

Yes. Each recognised reply removes the opposite tag before adding its own, so an order that was confirmed and then cancelled ends up with only beacon-cod-cancelled. The message log keeps the most recent classification on the original message row.

More guides