Messaging your attendees

Between selling a ticket and opening the doors there is almost always something people need to be told. The room moved, the parking is different from what the venue's website says, bring a laptop, the start time is not the doors time. Getting that to the right people reliably is a surprisingly large part of running an event well.

Reminders

Event reminders go out to ticket holders ahead of the date, in the event's own timezone.

The timezone detail is the part that goes wrong elsewhere, and it is worth dwelling on because it is invisible until it is embarrassing. A reminder scheduled "at 9am" without reference to a timezone arrives at 3am for anybody in another country — and for an event selling across Europe, that is a meaningful share of your attendees. A 3am push is worse than no reminder at all: it is the thing people mute.

Reminders matter because a ticket bought three months ago has been forgotten. Reminder emails are consistently among the highest-value messages an event sends, measured in people who actually show up.

Your own message

You can send your own message to attendees — a room change, a parking note, what to bring, a schedule update.

Two properties are worth knowing. It goes out as a properly branded email rather than a plain-text blast, so it looks like it came from your event and not from a compromised account. And it reaches everyone holding a ticket, not only the person who paid. On a booking for six that is the difference between one informed person and six.

Replies come back to you

Attendees can message you about their booking, and you answer in the same place.

Neither side has to publish a personal address, which is the immediate benefit — you are not putting your own inbox on a public event page, and you are not giving out a mobile number. The more useful property is that the conversation stays attached to the booking it is about. Whoever picks it up can see what was bought, when, and for how many, without asking the attendee to repeat information they already gave you.

That also means the conversation survives your team. Somebody covering for a colleague can see the history; a question answered by your box office does not vanish because it lived in one person's mail client.

You can turn it off

Attendee messaging is enabled per event and can be switched off. Not every event wants an open channel, and an inbox nobody is watching is worse than no inbox at all — it collects genuine questions, answers none of them, and gives people a reasonable grievance.

Turn it on if somebody will read it. If your event is small and your email is on the page anyway, that is a legitimate choice too.

Writing a message people read

• Put the change in the subject line. "Room change: now Hall B" beats "Important information about your booking", which is what every phishing email also says.
• Send once, properly. Three corrections to the same detail train people to ignore the fourth.
• Lead with what they must do differently. Most attendees read the first line and stop; put the action there and the context after.
• Do not use it for marketing. Attendees gave you their address to attend your event. A promotional blast to a ticket-holder list is both bad practice and, in the EU, a consent question you probably do not want to answer.

One practical limit

Email is the real capacity ceiling on any ticketing platform, this one included. Web infrastructure scales more or less indefinitely; outbound mail is rate-limited by providers and by reputation, and it is the constraint that bites first.

For ordinary events this never comes up. If you are planning a very large send — tens of thousands of recipients at a fixed moment — plan it in advance rather than discovering the ceiling on the day. A message that takes two hours to deliver is fine when you sent it a week early and a serious problem when you sent it an hour before doors.