Create Approved WhatsApp Templates
WhatsApp doesn't let you send arbitrary messages at scale — every outbound template has to be approved first. On this page you'll build those templates (content, variables, and buttons), submit them for review, and reuse the approved versions across WhatsApp campaigns and automations.
Entry pointGrowth → Library
| Article summary | Details |
|---|---|
| Best for | Anyone running WhatsApp campaigns |
| Main outcome | Approved WhatsApp templates ready for campaigns and automations |
| Requires | A connected WhatsApp sender and template content |
| Related reports | WhatsApp campaign performance |
Open WhatsApp Templates
- Go to Growth.
- Open Library.
- Choose Whatsapp Templates.
- Review existing templates.
Create A WhatsApp Template
- Choose the action to create a new WhatsApp template.
- Select the WhatsApp account if prompted.
- Add template content, variables, and buttons as needed.
- Save and submit for review when ready.
Good Template Habits
- Write in clear, customer-facing language.
- Keep variables easy to understand.
- Match each template to one campaign purpose.
- Don't schedule a campaign on a template that's still pending approval.
Common Issues
| Issue | What to check |
|---|---|
| Template is not available in Campaigns | Confirm it is approved and belongs to the selected sender |
| Variables fail | Check variable names and example values |
| Template is rejected | Edit the content and resubmit |
Most problems here come down to the sender or the approval. If no WhatsApp account appears when you create a template, ask your admin — the WhatsApp sender has to be connected at the workspace level first. Rejected templates aren't a support issue either; edit the content and resubmit.
If a template shows as approved but still doesn't appear when you build a campaign for that same sender, contact Brixi support with the template name, the sender, and a screenshot of its approval status.
Reporting Impact
Because approved templates are reused across sends, WhatsApp campaign reporting stays consistent — performance reflects the template itself rather than one-off copy.