Pre-event attendee communication: what to send, when, and what to stop sending

Most attendees don't miss information because nobody sent it. They miss it because it was the fourth email that week, it looked like the other three, and the room change sat under a sponsor banner in paragraph six.

Pre-event communication works when every message has one job and arrives when the attendee needs it. This guide gives you a simple schedule for registered attendees, from the confirmation to the morning of the event, and a list of messages worth cutting. It is written for agency producers, corporate event teams and congress organisers in Turkey and across Europe.

Key takeaways

• Send fewer, clearer messages: a confirmation, a calendar invite, a know-before-you-go message, a day-before reminder, and change notices only when something actually changes.
• Each message should answer one question the attendee has at that moment. Put the answer in the first lines, not in an attachment.
• Keep logistics and promotion apart. Turkish rules on commercial electronic messages, UK guidance on service messages and Gmail's sender guidelines all treat a promotion inside a service message as a problem.
• Stop inviting people who have already registered, and stop sending the same message on three channels at once.
• Agree one communication plan with the client, venue and hotel, so attendees don't get five versions of the start time.

What does pre-event attendee communication include?

It covers every message a registered attendee receives between signing up and walking in: the confirmation, calendar invites, logistics, reminders, change notices and any day-of alerts by email, SMS, WhatsApp or app push.

It is a different job from event marketing. Marketing persuades people to register. Pre-event communication helps people who already said yes to turn up at the right place, at the right time, with what they need. Treating the two as one stream is where most of the noise comes from.

What should you send, and when?

Start with five messages, and add more only when you can name the question each new one answers. The timings below are a sensible starting point, not a rule. Shift them for multi-day congresses, travel-heavy events or very short lead times.

The confirmation

The confirmation is the message attendees search for later, so write it for that moment. Use a subject line they can find ("Your place at event, 14 November, Istanbul"), and put the essentials in the body, not only in a PDF. If they will need a QR code at the door, include it in the email itself. Our guide to keeping check-in queues short explains why a code people can find in seconds matters at the entrance.

The calendar invite

A calendar entry does more work than a reminder email, because it sits in the place people actually plan their day. Send it as a proper invite or .ics file, and keep the same event identifier when you update it. Under the iCalendar scheduling standard (RFC 5546), an update with the same UID and a higher sequence number replaces the earlier version. Send a fresh invite with a new identifier and many calendars will show two entries, one of them wrong.

Know-before-you-go

This is the long message, and the only one that should be. Organise it by the questions attendees ask: How do I get there? Where do I go when I arrive? What is on, and when? What should I bring? Who do I contact? Short headings help people scan it on a phone.

Segment it. A speaker needs rehearsal times and the technical contact. An exhibitor needs build-up hours and the loading bay. A hotel guest needs transfer times; a local attendee needs parking. One generic message forces every group to dig for their own part.

The day-before reminder

Keep it short enough to read at a red light. Doors-open time, address, map link, QR code, and anything that has changed since the last message, marked clearly at the top. If nothing has changed, say so in one line; that is useful information too.

Day-of alerts

Use SMS, WhatsApp or app push only for things that affect the next hour: a different entrance, a room change, a delayed start, a closed road. If you send day-of messages for routine content, people learn to ignore the channel exactly when you need it.

Why keep logistics and promotion in separate messages?

Because a logistics message with a sales pitch inside it stops being a logistics message. Regulators and inbox providers both see it that way, and attendees notice too.

• Turkey. Under the regulation on commercial communication and commercial electronic messages, notifications about an ongoing membership, purchase, delivery or similar status don't need prior consent, but they cannot promote any goods or services (Article 6). Promotional messages need consent, which is managed through İYS, the national message management system.
• UK. The ICO treats "service messages" (administrative or customer-service messages with no promotion) as outside direct-marketing rules, and says a service message that includes promotional elements counts as direct marketing even if that is not its main purpose. Branding and logos alone don't change that.
• Inbox providers. Gmail's sender guidelines say not to mix different types of content in one message, and to send each category of message from the same From address. Gmail and Yahoo both expect bulk senders to keep spam complaints below 0.3% and to offer one-click unsubscribe on marketing mail.
• WhatsApp. Meta sorts business message templates into utility, marketing and authentication. Utility templates have to be non-promotional, and a template that reads like marketing can be reclassified.

This is not legal advice, and the rules differ across EU countries, so check with your legal team for your situation. The practical habit is the same everywhere: confirmation, invite, logistics and reminders stay plain and factual. The sponsor showcase, the early-bird for next year and the newsletter go in separate, consented marketing messages.

What should you stop sending?

Most event inboxes improve more from removing messages than from writing better ones. Start with these.

• Invitations to people who already registered. Nothing says "nobody is tracking this" like a "Don't miss out, register now" email to someone holding a ticket. Suppress registered attendees from every invite and reminder-to-register.
• The same message on three channels at once. Email, SMS and WhatsApp with identical text at the same minute feels like an alarm. Pick a primary channel for each message type and use a second channel only for urgent changes.
• Countdown emails with nothing new. "Only 10 days to go!" adds no information. If a reminder can't name something the attendee should do or know, skip it.
• Critical details only in attachments. PDFs are hard to read on a phone and easy to lose. Keep the essentials in the body; attach the full programme if you like.
• Messages nobody can reply to. A no-reply address on a logistics email turns a simple question into a support ticket. Give a monitored address or a named contact.
• Messages to people who cancelled or are still waitlisted. Send them their own status, not the attendee schedule.

Who should own the communication plan?

One person, with one plan everyone else signs up to. On agency projects, attendees often hear from the agency, the client's internal comms team, the venue and the hotel, each with its own template. If the venue says doors open at 08:30, the agency says 09:00 and the client's intranet says 09:15, attendees will pick one, and some will pick wrong.

Write the plan as a simple table: message, audience segment, channel, send date, sender, and who approves the copy. Share it with the client and suppliers before registration opens, and agree that nobody else emails attendees about logistics. When something changes, update the source of truth first and let every message pull from it.

How do you know your messages are working?

Look at what happens at the door and the help desk, not just at open rates. Useful signals:

• Questions to the help desk or inbox. If many people ask where to park, the know-before-you-go message didn't answer it clearly, or arrived too late.
• Arrivals without a QR code. A high share means the code is hard to find. Move it higher in the confirmation and the day-before reminder.
• No-shows by segment. Compare registered against checked-in by ticket type or source. A group with unusually low attendance may need a different reminder, or a different channel.
• Unsubscribes and complaints from logistics messages. Attendees shouldn't want to unsubscribe from information about an event they chose to attend. If they do, something promotional has crept in, or you are sending too often.

How eventIQ helps

In eventIQ's Experience Engine, communication runs from the same attendee record as registration and check-in. Registration sends a branded confirmation with the QR code, calendar invite and event details as soon as someone signs up, followed by reminders at intervals you set. In Event Marketing, reminders follow registration status, so people who have registered stop getting invitations. In the event app, push notifications go to segments by registration type or session choice, which keeps day-of alerts relevant.

FAQ

How many emails should you send before an event?

For most single-day events, four messages cover it: a confirmation, a calendar invite, a know-before-you-go email about a week ahead and a short reminder the day before. Add change notices only when something actually changes. Multi-day congresses and travel-heavy events may need one more planning message.

Do event confirmation emails need marketing consent?

Generally no, as long as they are purely about the attendee's registration. In Turkey, notifications about an ongoing purchase or membership don't need prior consent but can't promote anything; in the UK, the ICO treats purely administrative messages as service messages. Once you add promotional content, the message is treated as marketing. Check local rules with your legal team.

Should you use WhatsApp or SMS for event reminders?

Use them for short, time-sensitive messages: the day-before reminder or a day-of change. Keep email for the confirmation and the detailed logistics. On WhatsApp, messages you start outside a customer-service window have to use approved templates, and reminder templates need to stay non-promotional to count as utility messages.

What should a know-before-you-go email include?

How to get there and where to park, which entrance to use and where to pick up badges, agenda highlights, what to bring, dress code, accessibility information and a contact for questions. Segment it so speakers, exhibitors and hotel guests each get the details that apply to them.

Start with the message you already send

Open the last confirmation email your team sent and read it on a phone. If the date, time, venue and QR code aren't visible without scrolling, fix that first. Then list every message your attendees got for that event and cross out any you can't explain in one sentence. If you'd like to see how this runs from one attendee record, take the Experience Engine tour.