100%
Integrations › WhatsApp

WhatsApp message templates

Writing one template per message and language, getting Meta's approval, and what happens when Meta calls a template marketing.

WhatsApp delivers a message a business starts only when it uses a template Meta has approved. On Back Office › Integrations › WhatsApp, the store writes one template for each message it wants to send by WhatsApp, in each language it wants to send it in. Writing templates needs Back Office configuration permission.

The messages

MessageSent whenVariables
Payment linkPay links from the call center, the orders list and the delivery screen{{1}} business name, {{2}} payment link
Payment receivedA pay link is paid; an operator sends a card-by-phone approval{{1}} business name, {{2}} amount, {{3}} order number
Reservation confirmationThe booking is made{{1}} business name, {{2}} date and time, {{3}} party size, {{4}} confirmation code, {{5}} booking page link
Reservation reminderBefore the sitting{{1}} business name, {{2}} date and time, {{3}} party size, {{4}} booking page link
Table readyThe host stand calls the party{{1}} business name
Order receivedAn online order is placed{{1}} business name, {{2}} order number
Order readyThe first kitchen display bump, or Mark Ready And Notify on the orders list{{1}} business name, {{2}} order number
On the wayA delivery is dispatched with a driver{{1}} business name, {{2}} order number

The variables are filled in by AmigoPOS when the message is sent; the rest of the wording is the store’s.

Writing and submitting

  1. Start a new template and choose the message and the language. Suggested wording appears: edit it freely.
  2. Keep every variable, from {{1}} up to the last one, and don’t start or end the text with a variable — Meta rejects that. The limit is 1,024 characters.
  3. Submit it. The row shows Pending while Meta reviews it — usually minutes, sometimes up to a day — and then Approved or Rejected with Meta’s reason.
Image needed · wa-15
Capture: The template editor: message and language drop-downs, the wording and the list of variables.

Status changes arrive by themselves through the webhook; Refresh From Meta reads them all again on demand.

Image needed · wa-14
Capture: The templates table on the WhatsApp page: an approved row, a pending row and a row flagged as marketing with Use Anyway.

Utility or marketing

Every template is submitted as a utility (transactional) message, but Meta decides the category. If Meta classes one as marketing — which costs more and which WhatsApp does not deliver to US numbers — the row is flagged and AmigoPOS holds it back: those messages go by text instead, or not at all for messages that are WhatsApp-only. Rewrite it in plainer, transactional words, or tick Use Anyway to send it regardless. Meta can also re-label an approved template later; the flag then appears by itself.

Keep the wording plain: what happened, the order or the booking, the link. Offers, “come back soon” and emojis push Meta towards marketing.

Languages

Write the same message in several languages to reach visitors in their own. AmigoPOS sends the template in the customer’s language when it knows it — a reservation guest’s language, or the one the operator picks on the pay link screen — otherwise in the store’s language, then the closest language, and failing that the oldest approved one, so a customer who reads English still gets the message.

Editing and deleting

  • Editing an approved template sends it back to Meta for review, and Meta allows about one edit a day. Its message and language can’t change: create a new template instead.
  • Deleting a template (press twice to confirm) removes it from Meta as well.
  • After connecting a different WhatsApp Business Account, every template is a draft again: submit each one once more.