Why templates exist at all
If a customer messaged you in the last 24 hours, you can reply however you like. Outside that, WhatsApp requires a pre-approved template — that is what keeps the platform from turning into SMS spam. Get the format right and approval takes minutes; get it wrong and you wait, then get rejected.
A builder that shows the phone, not a form
Compose the header, body, footer and buttons, and see exactly what the customer will receive as you type. Variables are inserted with a click and numbered for you, so the parameters you send later always line up with the template you submitted.
- Text, image, video or document headers
- Body text with numbered or named variables
- Footer text, and up to three buttons
- Call-to-action buttons that open a URL or dial a number
- Quick-reply buttons that feed answers back into your automations
The three categories, and why picking right matters
Meta sorts every template into marketing, utility or authentication. The category decides both the review standard and what you are charged when the template is sent. Choosing “marketing” for what is really an order update costs you more; choosing “utility” for a promotion gets it rejected.
- Marketing — offers, launches, re-engagement. Highest rate, strictest review.
- Utility — order updates, appointment reminders, payment confirmations. Lower rate.
- Authentication — one-time passcodes only, in a fixed format Meta specifies.
“Your order #1042 has shipped” → Utility.
“30% off this weekend only” → Marketing.
“482913 is your login code” → Authentication.
One-time passcodes, formatted the way Meta demands
Authentication templates have a rigid structure — the code appears in the body and on a copy button, with specific wording you cannot vary. Get it slightly wrong and it is rejected. The builder produces the correct structure for you. For privacy, when an authentication template is sent, the conversation records that a code was sent rather than storing the code itself.
- Correct authentication structure generated automatically
- Security disclaimer and expiry wording handled
- Codes are never left sitting in your team's inbox
Submit, track and keep in sync
Submit for review from inside the app and watch the status change from pending to approved or rejected. Sync pulls the current state from Meta whenever you want, so what you see matches what they hold. Delete templates you no longer use, and duplicate an approved one as the starting point for the next.
- Submit for review without leaving the app
- Approval status synced from Meta
- Duplicate an approved template to make a variant
- Delete templates you no longer send