A good message sent to the wrong person or at the wrong time is still poor communication. Begin with a map of attendee touchpoints; write the copy and configure automation only after the process is clear.
What an event communication plan contains
A plan is not a newsletter calendar. It is an operational document in which every message has:
- an objective;
- a recipient segment;
- a trigger or sending moment;
- a primary and, where necessary, backup channel;
- an owner for content and approval;
- an expected attendee response;
- a measure of the intended outcome.
Promotional communication should generate interest in the event and encourage people to register. Attendee communication guides those who are already interested or registered through the successive stages: confirmation, payment, preparation, entry, participation, and follow-up. The two processes should be consistent, but their objectives and legal bases must not be confused.
Event attendee communication matrix
This example shows the structure. Actual timing depends on the event and audience.
| Stage | Recipient | Message | Channel | Trigger | Owner | KPI |
|---|---|---|---|---|---|---|
| Registration | New registrant | Status and next step | Form submission | Registration team | Delivery and process completion | |
| Payment | Attendee with a pending payment | Status and secure return to payment | No payment provider confirmation | Finance/registration | Payment statuses resolved | |
| Preparation | Confirmed attendee | Agenda, travel, accessibility | Email + website | Information approved | Attendee support | Clicks and fewer questions |
| Before entry | Valid ticket holder | Code and correct entrance | Email/SMS | Event approaching | Check-in team | Code use and exceptions handled |
| During event | Attendee in affected session | Room or time change | App/SMS/screens | Approved change | Event lead | Correct audience reached |
| After event | Attendee marked present | Materials and survey | Attendance confirmed | Programme/marketing | Downloads and useful responses |
Include emergency messages and the criteria for sending them in the plan. This ensures that the team knows when to send them and who is responsible.
Before the event: manage the attendee relationship
The relationship with attendees begins on the event website. This is where they should find up-to-date information about the programme, venue, terms of participation, accessibility, and answers to frequently asked questions. Social media can direct attention to the website and build a community, but it should not be the only place where critical information is published.
After registering, an attendee needs to know:
- their current status;
- whether and how to pay;
- what happens next;
- where to correct data or obtain support;
- when the ticket and practical information will arrive.
Send subsequent messages according to the attendee's status and role, not to the entire database. Speakers should receive information about rehearsals and presentation requirements; workshop attendees need details about the room and materials; partners need organisational information; and people on the waiting list need to know the rules for releasing places.
Invitations should answer recipient intent. Our separate event invitation guide provides a template and writing rules.
Channels: website, email, SMS, app, and social media
Event website
Use it as the durable source of truth. Keep the programme, speakers, travel, accessibility, contact, and FAQ current. Messages should link to the relevant section rather than a generic home page.
Email is suitable for confirmations, tickets, agendas, documents, longer instructions, and materials. Use a recognisable sender, an unambiguous subject line, and one primary action. Configure sending correctly, provide a plain-text version and an unsubscribe option where required, and make it possible to reply or obtain help. Also pay attention to deliverability. Even a well-prepared email will not serve its purpose if it lands in spam or is rejected by the recipient's server. Deliverability is affected by factors including sender-domain configuration, sender reputation, and how the message is constructed.
SMS
Text messaging works best for short, urgent communications such as an entry code, a reminder, or information about a change affecting a specific group of attendees. For important information, do not rely solely on SMS—communicate it through another channel as well. See the event SMS guide for a detailed schedule and examples.
App and push notifications
An app can be useful when attendees use a personalised agenda, event map, networking features, or real-time programme updates. Notifications should be tailored to the attendee's situation and needs. However, an app should not be introduced simply because the event is large—it should genuinely make participation easier.
Social media
Social media supports event promotion and ongoing contact with audiences. It should not be the only place where important organisational information is published, because not every attendee follows the account and post reach depends on the platform.
During the event: operational communication
Attendees should know where to find current information and support. Establish one process for reporting changes and one role that approves the message before publication.
When something changes, state:
- what changed;
- who is affected;
- the new location, time, or action;
- whether other details remain unchanged;
- where help is available.
Do not soften a problem until the message becomes unclear. If a session is delayed, say so and give a time for the next update. For safety issues, follow venue and emergency-service procedures; marketing communication cannot replace crisis instructions.
After the event: materials, feedback, and next step
Start follow-up from attendance status. Someone who did not arrive should not receive “thank you for attending.” An attendee marked as present may receive:
- a thank-you message referring to the actual event;
- materials the organiser has the right to share;
- answers to unresolved questions;
- a focused survey tied to decisions;
- a relevant next step aligned with the event objective.
Do not artificially spread materials across multiple emails to increase contact frequency. Send them when ready and useful. Do not promise recordings or slides before confirming speaker permission.
Segmentation: the right message to the right person
Useful criteria include:
- attendee role;
- language;
- ticket type and payment status;
- selected sessions or services;
- registration and attendance status;
- accessibility requirements;
- consent and communication preferences.
Segmentation should be based on a single, up-to-date attendee database. A change in registration, payment, selected session, or attendance status should immediately affect which messages that person receives. This removes the need to update separate mailing lists manually and makes it easier to avoid sending a message to the wrong recipient.
Collect only data with a defined purpose. Every segmentation rule should be testable. Before sending, check group size, sample recipients, and exclusion conditions.
Automation with human control
Automate predictable events: registration confirmation, status change, payment receipt, ticket delivery, or follow-up after attendance is recorded. Do not automate solely by date when current status matters.
Each scenario should specify:
- trigger;
- inclusion and exclusion conditions;
- language template;
- sender and channel;
- error behaviour;
- ability to stop sending;
- testing owner.
Test normal and exceptional journeys: new registration, cancellation, failed payment, changed email, missing telephone number, and message resend.
How to measure event communication
Match the metric to the message objective. Delivery does not mean understanding, and a click does not mean completed registration.
Measure, where relevant:
- delivery rates and sending errors;
- clicks on links and buttons;
- completed registrations or payments;
- ticket use and actual attendance;
- common, recurring attendee questions;
- opt-outs, complaints, and messages sent to the wrong people;
- attendee responses that can help improve future events.
After the event, review the process with its owners: which attendee questions recurred, which information was outdated, and which automations need improvement.
Event communication checklist
- Every message has a defined objective, audience, and person responsible for preparing it.
- The event website contains up-to-date information.
- The communication channel matches the urgency and type of information.
- Messages are sent according to the attendee's current status.
- Important information is also communicated through an additional channel.
- Consents and legal bases for communication have been reviewed.
- Automated messages account for exceptions and possible errors.
- All language versions have been tested.
- Links, forms, and subsequent messages work correctly.
- Communication effectiveness is evaluated by outcomes, not only the number of messages sent.
Conclusion
Effective attendee communication requires up-to-date data, appropriate audience segmentation, and the right choice of channels. The CONREGO communication module allows registration to be combined with email and SMS. Technology alone is not enough—the organiser must know to whom, when, and for what purpose each message should be sent.