A WhatsApp template has to be approved on the WhatsApp side before you can send it. Pick the category that matches the message (utility, marketing or authentication), write plain wording with numbered variables, give a sample for each variable and submit at least a week before you need it. Sociana then sends it through your provider account.
Who this guide is for
You are a conference secretariat, an association’s programme manager or an agency producer who has been told to “send it on WhatsApp”. You have a registration list and an announcement to make, and you have just learned that a message cannot simply be typed and sent to 800 people. This guide explains the approval step and how to pass it first time.
Why templates exist
WhatsApp separates conversations a user starts from messages a business starts. A business can open a conversation with a user only with a pre-approved template, so the platform can keep the channel from filling with spam. For an organiser the consequence is practical: wording, variables and category are fixed before the send, and every change needs a new approval.
The rule that matters most for event teams is in Sociana’s WhatsApp feature page: a template has to be approved on the WhatsApp side before the organiser can send it. Delivery and read status then come from the provider’s own records, and no delivery rate is promised.
Which category fits which event message
| Message | Typical category | Why | Wording note |
|---|---|---|---|
| Login code | Authentication | Delivers a one-time code | Code only, no extra text |
| Registration confirmation and ticket | Utility | Responds to a transaction | Include the event name and the reference |
| Invoice or payment receipt | Utility | Responds to a payment | Amount and invoice number as variables |
| Schedule change on the day | Utility | Concerns something the guest signed up for | Time, place, what changed |
| Early-bird or sponsor offer | Marketing | Promotes | Opt-in needed; keep separate |
| Thank-you with photos link | Utility or marketing depending on content | Check with your provider | Keep it informational |
Providers apply Meta’s categories to your template, so a utility template that reads like an advertisement can be re-categorised or rejected.
Step by step
Step 1: List the messages you actually need
Most conferences need five: login code, registration confirmation, reminder, day-of change and a thank-you. Resist templating every possible message; each is a separate review.
Step 2: Choose the category honestly
Write the message first, then ask what it is. If it responds to something the guest did, such as registering or paying, it is utility. If it invites someone who has not acted, it leans towards marketing. Authentication is for codes. Do not disguise marketing as utility; it is the commonest reason a template is rejected or re-categorised.
Step 3: Write the wording in plain language
Say who you are, what happened and what to do. One action per message. Do not shout, do not use all capitals and avoid exaggeration. For an association: “Hello [name], your registration for [event] on [date] is confirmed. Your entry QR is in the app: [link].” In the template itself each bracket becomes a numbered variable. Use your own copy, not this line, and keep to the brand voice.
Step 4: Use variables with clear samples
Variables are numbered placeholders. The review wants a sample value for each, so a reviewer can see the final message. Avoid starting or ending the template with a variable, and do not stack variables with nothing between them. Keep the number of variables small.
Step 5: Add buttons only if you need them
A link button, such as “Open the app”, is clearer than a pasted URL. Use the same domain as your brand; avoid link shorteners, which look suspicious in review.
Step 6: Submit early and in batches
Review time varies. Submit every template at least a week before the first send, keep a second wording of each in reserve and do not announce the send date until the template is approved. Submitting four templates together lets you fix a pattern in one go if one is returned.
Step 7: Handle a rejection calmly
Read the reason. Common causes: the wording looks promotional in a utility template, the variable samples are missing, the content does not match the category, or the template includes a link to an unrelated domain. Change one thing at a time and resubmit.
Step 8: Test, then send
Send to three internal phones, check the variables render, then send to the list. After the send, read the provider’s delivery status and keep the log.
A submission log
Keep a simple log of every template you submit. Record the name, the category, the date submitted, the wording, the sample values, the result and, if rejected, the reason and what you changed. After two events you will have a library of wordings that passed and a list of phrases that did not.
Share the log with your agency or provider contact so a colleague can reuse a template without starting over. Version the names: “registration_confirmed_v2”, not “new_template_final”. When an event changes, copy the nearest approved template and change one thing at a time, which makes a rejection easy to diagnose. The WhatsApp template library is a good place to keep the approved wordings.
Pitfalls
- Mixing marketing into a utility template. Keep offers out of confirmations.
- Changing wording after approval without resubmitting. Each change is a new template.
- Variables that look blank. Test with realistic samples, including long names.
- Using a personal WhatsApp account. Business messages go through the provider’s account.
- Forgetting opt-in. Message only numbers you hold for this purpose.
India and SAARC notes
Indian attendees expect event confirmations and tickets on WhatsApp, so authentication and utility templates are worth the effort. Write in English plus the regional language where your audience prefers it; each language version is its own template. For events in other SAARC countries, check that your provider supports sending to those numbers and which local rails apply for any payments. India’s WhatsApp-first norms mean the provider relationship matters: ask about Indian support hours before you sign.
How Sociana handles this
Sociana connects to WhatsApp at organisation level: provider accounts, approved templates, configurable OTP, ticket and invoice messages, sender configuration and a fallback setting. The provider account belongs to your organisation, and messages go out under its sender configuration. For the APMI 3rd Annual Conference the registration list acted as the whitelist and ticketing included Razorpay payment, the kind of setup where confirmation and invoice messages are natural utility templates; see the APMI case study. EEMA Connect uses phone or email OTP across its occasions; see EEMA Connect. Draft your wording in the WhatsApp template library and preview it in the template preview demo.
Sociana does not control WhatsApp approvals, provider charges or delivery rates; those are set by WhatsApp and the provider contract.
FAQ
How long does approval take?
It varies, so plan for days rather than minutes. Submit early and keep a reserve wording.
Can we reuse a template for every event?
A template without event-specific text can be reused across occasions. A template with the event name in the body needs variables or a new approval.
Why was my utility template re-categorised as marketing?
Usually the wording promoted something. Remove offers and calls to buy from utility messages and keep them in a separate marketing template.
Can Sociana approve templates for us?
No. Approval happens on the WhatsApp side. Sociana connects the approved template to your occasion.
Related reading
Glossary: no-login voting, whitelist, occasion code. Occasion hubs: conferences, association events, dealer and partner meets. Related guides: bulk WhatsApp event invitations and WhatsApp OTP vs SMS OTP.