WhatsApp template language: why name alone is not enough

A template is a name plus a language. What happens when the pair goes missing, why only approved templates are listed, and how COD replies pick a language.

A WhatsApp message template is not identified by its name. Meta identifies it by the pair of name and language, and the same name can exist in English, Spanish and Portuguese at once, each with its own approval status. Most of the confusing moments merchants have with templates come from treating that pair as one thing. This post explains how Beacon Messenger stores and looks up templates, why the automation screen shows the language next to every name, what happens when the pair it expects is no longer there, and how the language of a cash-on-delivery template decides the language of the reply your customer gets.

A template is a name plus a language

In WhatsApp Manager you create a template called order_confirmation and pick a language. If you later add a Spanish version, you do not get a second template; you get a second language under the same name, submitted and approved on its own. Meta can approve the English version and reject the Spanish one on the same afternoon. When an app sends a message, it has to say which language it means, and if it asks for a pair that does not exist the message simply does not go.

Beacon Messenger therefore never stores just a template name on an automation. When you pick a template for order confirmations, shipping updates or the cash-on-delivery check, the app records both the name and the language code, and it sends with exactly that pair every time. The dropdown makes this visible: each option reads as name, then the language in brackets, then the category, for example order_confirmation (es_AR) · UTILITY. Two languages of the same name are two rows, and you choose one.

Only approved templates are offered

The dropdown lists templates whose status is APPROVED and nothing else. A template that is pending, rejected or paused is not hidden to be unhelpful; it is hidden because sending it would fail, and a dropdown that offers things that cannot be sent is worse than a short one. If you have just created a template and do not see it, the usual reason is that Meta has not approved it yet. Approval normally takes minutes to a few hours, occasionally longer. When a previously working template loses its status, for example after a quality downgrade, the behaviour is covered in what to do when a WhatsApp template is rejected or paused.

Templates are fetched from Meta in pages of up to a hundred, with the fields the app needs: name, status, category, language and the components that define the body and buttons. The list is cached on your shop record so the automation screen loads quickly, and refreshed when you ask for it or when a lookup fails, which is the next section.

What happens when the pair is missing

When an order comes in, the app looks up the stored name and language in the cached list. If the pair is there, the message is built and sent. If it is not, the app does not give up immediately: it refreshes the template list from Meta once, saves the fresh list, and looks again. Templates approved since the last refresh are found this way without anyone touching the settings.

If the pair is still missing after the refresh, the message is skipped and the message log records it with the reason template_not_found. Nothing is sent in a different language as a fallback, and no plain-text message is sent instead, because outside the customer service window WhatsApp only allows templates. A skipped message is visible, which is the point; a message quietly sent in the wrong language would not be.

Why a configured template stops being found
What changed in WhatsApp ManagerWhat the app seesWhat to do
Template deletedPair missing after refresh; skipped as template_not_foundPick another approved template on the automation
Template renamedOld name missing; new name appears under its languageRe-select the template; the stored pair does not follow a rename
Language version removedOther languages of the name still present, the stored one is notPick the remaining language, or recreate the version
Status changed to paused or rejectedPair present but not APPROVED; not offered, sends failFix the template or switch; see the rejected-template guide
New language version addedAppears as an extra row after refreshNothing, unless you want to switch to it

Renaming is deleting, from the app's point of view

Meta does not let you rename a template in place; a new name is a new template that goes through approval again. From the app's side the old pair disappears and a new one shows up, and the automation keeps pointing at the old pair until you change it. The practical rule: after any change to a template's name or languages in WhatsApp Manager, open the automation in Beacon Messenger, confirm the dropdown still shows the pair you expect, and send yourself a test message before the next real order.

Cash on delivery: the template's language sets the reply language

The cash-on-delivery automation is where language matters twice. The outgoing template asks the customer to confirm the order, and the customer answers. The app understands confirmations and cancellations in several languages at once: yes, confirm, si, sí, confirmo, sim, oui, ja, a thumbs up or a check mark all count as a confirmation, and no, cancel, cancelar, não, non, nein or a thumbs down count as a cancellation. That part is language-agnostic by design, because customers answer in whatever they speak, not in the language you wrote the template in.

The acknowledgement the app sends back is not language-agnostic. It is picked from the language of the COD template you selected: a template in es_MX or es_ES gets a Spanish acknowledgement, pt_BR gets Portuguese, hi gets Hindi, and anything else gets English. So if you serve two markets with two languages, the clean setup is two COD templates, one per language, and the app will answer each customer in the language of the template they received. The rest of the COD flow, including the beacon-cod-confirmed and beacon-cod-cancelled order tags, is in cash-on-delivery confirmation over WhatsApp.

A checklist for multi-language stores

  1. Create each template once per language under the same name, and wait for every language to show APPROVED in WhatsApp Manager.
  2. In Beacon Messenger, open each automation and check the language code in brackets next to the template name. Pick the one that matches the market the automation serves.
  3. For cash on delivery, remember the acknowledgement follows the template language. If a market needs an answer in Spanish, the COD template must be a Spanish one.
  4. After any rename, deletion or new language in WhatsApp Manager, re-open the automations and re-select. The stored pair never updates itself.
  5. Watch the message log for template_not_found after changes. One skipped message is a signal; a morning of them is a template you forgot to re-select.

Frequently asked questions

Why does the template dropdown show the same name several times?

Each row is a different language of that template. WhatsApp approves every language separately, and the app sends with a specific name and language pair, so you pick the exact version you want. The language code is shown in brackets after the name.

My template is approved but does not appear in Beacon Messenger. Why?

The list is cached on your shop. Reload the automation page to refresh it, and check that the status in WhatsApp Manager is APPROVED rather than pending or paused, since only approved templates are offered. If a language was added recently, it appears as a new row after the refresh.

What does template_not_found in the message log mean?

The stored name and language pair was not in Meta's list even after a fresh fetch. It usually follows a rename, a deletion or the removal of one language version. Open the automation, pick an approved template again and resend a test message.

Does the app translate the cash-on-delivery acknowledgement?

No. It picks a built-in acknowledgement in English, Spanish, Portuguese or Hindi based on the language code of the COD template you selected, falling back to English for any other code. The customer's own reply is understood in all of those languages regardless.

More guides