WhatsApp for events and communities: reminders, updates and groups

WhatsApp for events and communities works best as two tools side by side: a group or Community for members to talk among themselves, and a consented broadcast for the updates everyone must see, such as registration confirmations, reminders, venue changes and follow-ups. Broadcasts go to each person privately, through approved templates, so nothing gets buried in chat.

This playbook is for conference and meetup organisers, member associations, churches, NGOs, alumni networks and professional communities. It compares groups, Communities and broadcasts, then sets out eight plays with the trigger, the likely Meta template category, sample copy, how to run each one in Buddy today and the metric to watch.

Why use WhatsApp for events and communities?

Because it is where your attendees and members already spend their day. WhatsApp has more than 3 billion monthly users, according to Meta, across almost every country your community is likely to reach, from Lagos and London to São Paulo, Dubai and Mumbai. Event information is also time-critical in a way most marketing is not: a doors-open time read the next morning is useless.

The usual problem is not reach but noise. Most communities already have a WhatsApp group, and within weeks the important update is buried under greetings, side threads and memes, and half the members have muted it. The fix is not another group. It is a separate, quieter channel for the things that matter.

WhatsApp groups, Communities or broadcasts: which should you use?

Each tool does a different job. Groups are shared conversations where everyone sees every message and every member's number. Communities, in the WhatsApp app, bring several groups together under one umbrella with an announcements group that admins use to reach all members (WhatsApp Help Center). A broadcast through the WhatsApp Business Platform, which Buddy calls a WhatsNew, sends a private message from your business number to each person who opted in.

WhatsApp limits how many people a group or Community can hold and changes those limits from time to time, so check the current figures in the WhatsApp Help Center before you plan around them. Broadcasts through the Business Platform are limited differently: new accounts start at 250 unique recipients in 24 hours and move up tiers as quality stays good (Meta messaging limits).

Our recommendation for most organisers: keep the group for conversation if members value it, and move everything that must be seen (confirmations, reminders, changes, calls to action) into WhatsNews. You get reporting, private replies and a clean record of who agreed to hear from you.

What are the rules for event messages on WhatsApp?

You need opt-in before a business sends anything. Meta's Business Messaging Policy requires that people give you their number and agree to receive messages, and its opt-in guidance says the wording must make clear they are agreeing to messages from your organisation on WhatsApp. Ticking "I agree to the terms" at checkout is not the same as agreeing to WhatsApp updates. In the UK and EU, the ICO explains that pre-ticked boxes and silence are not valid consent.

Once someone has opted in, you can reply freely for 24 hours after they message you. Anything else must be an approved template (Meta). Meta's categorisation guidance treats messages that follow up on something the person did or asked for, and that sell nothing, as utility. Promotion, awareness and re-engagement are marketing, and a mix of the two counts as marketing.

Meta makes the final decision at review. Our guide to WhatsApp message templates covers how to write each type so it is approved first time.

The events and community playbook: eight plays

1. Collect opt-ins at registration and at the door

• Trigger: someone registers, scans a QR code on a badge, poster or welcome card, or taps a link on your event page.
• Category: the welcome is a template because they have not messaged you yet. If it promotes anything, it is marketing.
• Sample copy: Hi {{1}}, you're on the City Makers WhatsApp list. We'll send event reminders and changes here, and a monthly round-up. Reply STOP to leave.
• In Buddy: your hosted opt-in page and QR code, or the Buddy Embed form (beta) on your event site, plus a "When someone subscribes" automation that sends the approved welcome template. Every opt-in is logged with date and source.
• Metric: the Audience growth chart on your Dashboard, the source recorded on each contact, and opt-in rate against registrations.

2. Let people choose what they hear about

• Trigger: the welcome message asks people to reply with a word: SUMMIT, MEETUPS or VOLUNTEER.
• Category: their reply opens the 24-hour window, so your confirmation is a service message.
• Sample copy: Reply SUMMIT for conference updates, MEETUPS for monthly events, or VOLUNTEER to hear when we need help.
• In Buddy: one automation per word on "When a message comes in" with that keyword, using "Add a tag" and a short confirmation. Tags then decide who gets each WhatsNew.
• Metric: how many subscribers carry each interest tag, and how that changes over time.

3. Registration and ticket confirmation

• Trigger: someone buys a ticket or registers.
• Category: utility.
• Sample copy: You're registered for {{1}} on {{2}}. Doors open at {{3}} at {{4}}. Your ticket is in your email. Reply here with any questions.
• In Buddy today: export registrants who agreed to WhatsApp messages from your ticketing tool, import them by CSV with an event tag, and send a WhatsNew with your utility template. Sending instantly on each registration needs your ticketing platform to call the Buddy API: adding subscribers works today, and sending approved templates arrives with the public beta from 12 October 2026. No ticketing integrations are live in Buddy Connect yet.
• Metric: delivered rate on the WhatsNew detail page, which catches mistyped numbers early.

4. Countdown reminders

• Trigger: a week before, the day before and on the morning of the event.
• Category: utility, for people registered for that event.
• Sample copy: Tomorrow: {{1}} at {{2}}. Doors open {{3}}. Bring your ID for check-in. Directions: {{4}}
• In Buddy: schedule each reminder as a WhatsNew to the event tag with "Schedule for later". The Event announcement starter on the Templates page is a useful base. Keep to two or three reminders; each is a paid message.
• Metric: read rate before doors open, then turnout against registrations from your own check-in list.

5. Last-minute changes

• Trigger: the venue moves, a session is cancelled or the weather changes the plan.
• Category: utility.
• Sample copy: Change for {{1}}: we've moved to {{2}}, same time. Reply if you need directions.
• In Buddy: "Send now" to the event tag. Replies arrive privately in the Inbox instead of flooding a group, and your team can answer them within the 24-hour window.
• Metric: read rate in the first hour, and the number of "where is it?" replies.

6. Volunteer and member calls to action

• Trigger: you need six volunteers on Saturday, or member renewals open.
• Category: expect marketing. A general appeal is not a follow-up to something the person did.
• Sample copy: We need six volunteers for Saturday's clean-up, 9am to 12pm. Reply CLEANUP and we'll send the details.
• In Buddy: send a WhatsNew to the "volunteer" tag only. Add a keyword automation on "cleanup" that tags responders as "sat-volunteer" and notifies the team, so you can send the briefing to that tag. Keyword automations stay on and match any message containing the word, so a generic keyword like "yes" would also catch replies to other messages (and words like "yesterday"). Pause the automation once the event is over.
• Metric: replies and tagged responders, against the number you needed.

7. Follow up after the event

• Trigger: the day after the event.
• Category: utility if it only shares the slides or replay of the event they attended; marketing if it also pushes the next event.
• Sample copy: Thanks for coming to {{1}}. Slides and the recording are here: {{2}}. How was it? Reply with one thing we should change.
• In Buddy: a WhatsNew to the event tag. Replies are sorted on the Responses page into Interested, Question, Purchased, Follow up and Not now, and an automation on "When a reply is categorized" as Question can notify the team.
• Metric: reply rate, and the themes in replies.

8. A regular community digest

• Trigger: the same day and time each week or month.
• Category: marketing.
• Sample copy: This month at City Makers: two workshops, a new reading list and a members' social on the 28th. Details: {{1}}
• In Buddy: start from the Weekly newsletter or Community update starters, and schedule to everyone subscribed or to an interest tag.
• Metric: read and click rates over time, and opt-outs on the Consent page. Rising opt-outs mean you are sending too often.

What works today, and what needs an integration?

How much does WhatsApp cost for events?

Meta charges per delivered template message, and the rate depends on the category and the recipient's country (Meta pricing). Marketing templates are always charged; utility templates are charged outside the 24-hour window. From 1 October 2026 Meta also charges for service replies and utility messages sent inside the window, with service replies at the utility rate (Meta). See our breakdown of the October 2026 pricing change.

For events this means: keep reminders utility, keep them few, and do not mix an early-bird offer into a logistics message. Meta bills fees directly to your WhatsApp Business account, and Buddy does not add a markup; Buddy's own plans are on the pricing page. If you are expecting to message a large list for the first time, check your messaging limit tier and quality rating on Buddy's WhatsApp health page a few weeks ahead. Quality drops when people block or report you (Meta), which is one more reason to send only what people asked for.

How do you set up WhatsApp for your next event?

1. 1Connect your organisation's number to Buddy from Settings, WhatsApp, using Meta's Embedded Signup.
2. 2Create and submit your templates: welcome, registration confirmation, reminder and change (utility), plus one digest or announcement (marketing). Review can take up to 24 hours.
3. 3Add your opt-in link to the registration confirmation page and email, and print the QR code on badges and signage.
4. 4Build the welcome automation and the keyword automations for interest tags.
5. 5Schedule your reminders as soon as the event date is fixed, and brief whoever will answer the Inbox on the day.
6. 6After the event, compare reads, replies and opt-outs with turnout. The communities solution page and the WhatsApp marketing platform guide show how the rest of the channel fits together.

Want to go deeper on automation? Our guide to WhatsApp auto-replies and automation covers welcome flows, keywords and escalation to a person, and the WhatsApp opt-in guide has sample consent wording for registration forms.

Frequently asked questions