Do I have to create a new template every time I send an announcement?

You want to send a registration confirmation to parents, or a schedule reminder to patients. And up comes the question almost everybody asks on day one: "do I have to make a new template every time, even for every person?" The answer is far lighter than people fear.

One question decides everything

Before thinking about templates at all, ask yourself one thing: did this person message you first within the last 24 hours?

• Yes. You are replying inside a running conversation. Type whatever you like, at any length, with emoji, with links. No template is needed at all.
• No. You are starting a conversation with someone who has gone quiet. Here WhatsApp requires an approved template. That is Meta policy, not a WACO limitation.

The full rule is in my message was rejected but I could reply yesterday.

A real example: a registration confirmation

Say the message confirms a child class enrolment, with the name, the class, the fee, the schedule, the location, and a group link. Template or not? It depends on how you send it:

• A parent has just written "I would like to enrol for the Cloud class" and an admin replies with that confirmation. Type it freely, no template.
• You send the same confirmation to 40 parents at once from your enrolment records, most of whom have never messaged you. That is a broadcast, and a broadcast always needs a template.

If you do need a template, you need ONE, not one per child

This is the misunderstanding that causes the panic. You do not create a new template per child. You create one, and the parts that change become variables, filled in automatically at send time:

Hello 👋
The registration for {{1}} has been received for the {{2}} class.
The fee is {{3}}, payable to {{4}} in the name of {{5}}.

Schedule: {{6}}, {{7}}
Location: {{8}}
Activity updates via the group: {{9}}

On sending, {{1}} becomes "Zeana", {{2}} becomes "Cloud", {{3}} becomes the fee, and so on. This one template serves the whole intake, hundreds of parents, registered once. The built-in broadcast feature fills these variables from each contact record automatically.

Pick the right category

A registration confirmation like this belongs in the utility category, which is cheaper to send, because the content serves the recipient rather than selling to them. Keep the wording neutral and slip no promotion into it, or it will be forcibly moved into the marketing category. Other causes of rejection are in Meta rejected my template.

Pick the template's language

The template designer has a Template language field, just under the name. It is not the language of your dashboard — it is the language of the message body your customers will receive. It defaults to Indonesian.

For the Notification and Marketing categories the language code is only a label: your message is delivered exactly as written and approved, whatever the code says. It starts to matter only if you later create templates with the same name in several languages — that code is how Meta picks the right one.

Need a language that is not in the list? The API accepts any valid Meta language code — send the bahasa field when creating a template (API guide).