Buddy for events
The keynote moved rooms. Every ticket holder knew in minutes.
A schedule change by email gets opened after the session has moved. On WhatsApp, ticket holders read it between sessions, and their questions land in one inbox, not at a packed help desk.
For production, marketing and attendee teams at conferences, festivals, meetups and workshops
Production, marketing and the help desk, all on the same channel.
Production: changes that land before the session
A room moves at 11:40. By 11:50 everyone on that track has read it, and anyone with a question has already asked.
Read within the hourMarketing: the next event sells to this one's crowd
Past attendees hear about early access first, read it within the hour, and book before the public sale even opens.
"Is there parking at Hall B?"Question"Yes, I'll be at the workshop"Interested"My badge hasn't arrived"Follow upHelp desk: every question in one inbox
Questions, confirmations and badge problems arrive sorted by what the attendee means and get answered in the same thread. No more running between the desk and three inboxes.
The keynote moved to Hall B at 11:40.Your email about it was opened at 3pm. Your WhatsApp message was read in ten minutes.
Your attendees don't miss the session. They miss the email.
Schedule changes go out by email, room updates on a screen in the lobby, the feedback form a week later. Meanwhile every ticket holder checks WhatsApp between sessions and replies in seconds.
From ticket checkout to their WhatsApp in three steps.
One tick at checkout. Everything after that happens inside Buddy.
Opt in at checkout
A ticket holder ticks "Updates on WhatsApp" in the widget on your ticket page, or scans the QR on their badge. Buddy records the consent and where it came from.
Theo LaurentWebsite widget · checkout · just nowHana SatoQR on badge · Day 1Marcus ReidImport · said yes last yearGroup by track and ticket
Tags become audiences: day 1 ticket holders, the workshop track, priority passes, everyone who came last year.
Day 1 · main stageUpdatesWorkshop trackRemindersAttended last yearEarly accessOpted outNever messagedSend, automate, answer
The welcome sends itself. The room change goes out as a WhatsApp message. Every reply comes back to one inbox.
Hana replied "See you there" → stopFour messages ticket holders read in the first week.
Each one is an approved template with the ticket holder's name in it, and every reply comes straight back to the help desk.
Northlight ConferenceBusiness accountNorthlight ConferenceBusiness account
Northlight ConferenceBusiness accountNorthlight ConferenceBusiness accountPlays you set once and leave running.
Ticket holders who always know where to be.
A welcome when they opt in, a reminder the morning of, a room change the minute it happens. Each one goes to the track it concerns and stops when they reply.
Theo LaurentIn Hall BEarly access for the people who came last time.
Tag past attendees, open tickets to them first, and see who read and clicked before the public sale.
Ticket holders opt in at checkout and can opt out with one word. Buddy keeps both on record.
"Is there parking at Hall B?"QuestionEvery reply, sorted by what attendees mean.
Interested, question, follow up, not now. The help desk answers in the thread.
Consent on record for every ticket holder.
Every opt-in is recorded with where and when it happened. One word from an attendee stops every message, and that is recorded too.
Theo LaurentOpted inRoles for production, marketing and the help desk.
Invite the team. Each person sees only what they need.
Number health, at a glance.
WhatsApp's quality rating and messaging limits for your number, inside Buddy.
What every event team asks before messaging a thousand phones.
Anything else, ask Sarah.She reads and replies to every message.
Can an event message its ticket holders on WhatsApp?
Yes. Buddy is built on the official WhatsApp Business Platform and every message is permission-based: each opt-in is recorded with its source, and opt-out is honoured on the spot. Only ticket holders who said yes hear from you.
How do ticket holders opt in?
They tick the box in the widget on your ticket page, scan the QR code on their badge, or sign up on your opt-in page. People who said yes at a past event can be imported with that consent recorded.
Can we send a change to one track or ticket type only?
Yes. Tag ticket holders by day, track or ticket type and each tag becomes an audience. A room change goes only to the people it affects, and you see who it reached and who read it, minute by minute.
Does it work with our ticketing platform?
Ticket holders join through the widget on your ticket page, the opt-in page or a QR code, and you can import people who already agreed. Your developers can also add attendees from your own system with one API call the moment they opt in.
Can the whole team answer replies?
Yes. Every reply lands in one inbox, sorted by what the attendee means, and you can invite production, marketing and the help desk with their own roles. Nothing sits on one person's phone.
What does WhatsApp charge for these messages?
Meta charges for business messages by type and by the attendee's country. Your Buddy plan is separate from that.
A full hall, and a quiet help desk.
Join the waitlist and tell us about your next event. We'll send back the plays that fit it.