WhatsApp for event organisers: attendee groups, ticket support and day-of shifts
How an event team runs WhatsApp: announcement-only attendee groups, a ticket-support number with booking id required, day-of shifts, and winding the group down.
- Written by
- By WavesFlo team
- Published
- Published
- Reading time
- 2 min read
An event's WhatsApp has a short life and a sharp peak: weeks of quiet, then a rush of attendees asking about passes, venue and timings in the last 48 hours. Plan for the peak: a ticket-support number with a booking id required, an announcement-only group for attendees, a volunteer group for the day, and a date on which the group ends.
How should it be set up?
| Need | How | Note |
|---|---|---|
| Attendee notices | An announcement-only group | Organisers post; Send new messages off |
| Pass and entry queries | A number set up for tickets; Booking id required | A first-reply target in your working hours |
| Volunteers and vendors | Separate groups from attendees | Numbers are not shared with attendees |
| Day-of cover | Shifts and a cap per person | A named supervisor for the queue |
| Exhibitors | A group per exhibitor, or a community per event series | Up to 2,000 members in a community |
| After the event | Close the group on a stated date | Photos shared by link, not in the group |
How should event week run?
- Seven days out: send the logistics note in the group and pin it.
- Two days out: switch on shifts and agree who answers entry questions.
- On the day: one supervisor reads the backlog every hour.
- After: post the thank-you and the gallery link, then end the group.
What about ticket sales?
WavesFlo covers the conversations: a pass question becomes a ticket with the booking id required. It does not sell or issue event tickets, and it does not validate entry. Send attendees to your ticketing platform for that, and keep payment details out of chats.
What does the first month look like?
- Week 1: list audiences and the numbers each uses.
- Week 2: create the attendee group and the volunteer group.
- Week 3: set the ticket policy and the booking-id field.
- Week 4: run a rehearsal with the team on shift.
What are the usual mistakes?
- Attendees and volunteers in one group.
- No end date for the group.
- Entry queries answered from memory.
- No one covering the first hour of the event.
During event week the ticket and entry questions from every event number land in one inbox, split into shifts so someone covers the first hour, while the attendee and volunteer groups stay separate groups on the same numbers.
Questions
Can event organisers use WhatsApp for support?
Yes. Pass and entry questions become tickets with a booking id required and a first-reply target.
Does WavesFlo sell event tickets?
No. Use your ticketing platform for that.
How do I keep an attendee group tidy?
Turn off Send new messages so only organisers post, and take replies one to one.