A conference attendee communication plan you can actually run
What to tell attendees before the conference, during it, and after, who on your team owns each message, and how to handle room changes and questions without chaos.
A conference attendee communication plan answers four questions: what attendees need to know, when they need it, which channel carries it, and who on your team sends it and answers the replies. Write it as a simple timeline across three phases (before, during, after), give every message an owner, and decide in advance who makes the call on live changes like a moved session.
Step 1: Map what attendees need, phase by phase
Start from the attendee's point of view, not your org chart.
Before the event
- Registration confirmation. Date, venue, what happens next.
- Logistics. Travel, hotel block, parking or transit, accessibility details.
- Agenda. Sessions, how to pick tracks, where the latest schedule lives.
- Check-in. Badge pickup, what ID to bring, hours.
During the event
- Morning-of basics. Doors, registration desk, first session.
- Live changes. Room swaps, delays, cancelled or added sessions.
- Reminders. Keynotes, meals, the closing session, the evening event.
- Help. Lost badge, Wi-Fi, accessibility, first aid. Where to go and who to ask.
After the event
- Thank you. Short and specific.
- Follow-up. Slides, recordings, a survey, next year's date.
Step 2: Pick the right channel for each message
Most conferences use several channels, and each one is good at different things:
| Channel | Best for | Weak at |
|---|---|---|
| Long details: confirmations, agendas, travel, receipts | Anything urgent during the event | |
| Event website or app | The full schedule, maps, speaker bios | Reaching people who never open it |
| Text messages | Short, time-sensitive updates and quick questions | Long content or attachments people need to keep |
| On-site signs and staff | Wayfinding in the moment | Anyone not standing in front of them |
A useful rule of thumb: email for reference, text for right now. Keep texts short, and link to the full agenda instead of pasting it.
Step 3: Give every message an owner
Live updates fall apart when nobody knows who's allowed to send them, or when three people answer the same question differently. Decide ahead of time:
- Who writes and approves each scheduled message (usually marketing or the event lead).
- Who can send a live update like a room change, and who has to approve it. Keep this to one or two people.
- Who answers attendee replies, and in what hours. Registration questions, accessibility requests, and sponsor questions might go to different people.
- The escalation path for anything about safety, medical issues, or security, which should never wait in an inbox.
Write it down in one place the whole team can see on the day.
Step 4: Draft the timeline
Here's a starting point to adapt:
| When | Message | Owner |
|---|---|---|
| At registration | Confirmation (email), plus opt-in for event texts | Registration |
| 2 weeks before | Travel, hotel, agenda link (email) | Event lead |
| 1 week before | Short text: dates, venue, check-in hours | Event lead |
| Day before | Text: badge pickup, parking or transit | Ops |
| Each morning | Text: doors, first session, where to get help | Ops |
| As needed | Text: room changes, delays | Ops (one approver) |
| Last day | Text: closing session and thank you | Event lead |
| After | Email: slides, recordings, survey | Marketing |
The event communication plan tool builds a timeline like this for your dates, with message drafts you can edit.
Step 5: Write live updates that people can act on
A live update should make sense to someone glancing at their phone between sessions: what changed, where to go, and when.
If the change affects only some attendees, like a workshop with limited seats, send it only to them.
Step 6: Plan for replies
Texts invite replies, and that's a feature: people ask about parking, dietary needs, or lost badges in seconds. Plan for it:
- Staff the inbox during event hours, and say in your first text that people can reply.
- Agree on standard answers for common questions so everyone answers the same way.
- Route anything urgent to the escalation path, not the inbox.
Running the text part in Text My Event
Conference text messaging in Text My Event covers the "text for right now" layer of this plan:
- Individual texts. Each attendee gets their own message, not a group thread, so nobody sees anyone else's number and replies come only to your team.
- A shared inbox. Add teammates as co-hosts. They share the attendee list, scheduled texts, and replies inbox, so the person on inbox duty can answer while ops sends the room change.
- Groups. Text speakers, sponsors, staff, or a single workshop instead of everyone.
- Scheduled texts. Load the morning-of messages in advance, then edit them if something changes.
- Opt-outs handled. Anyone who replies STOP is opted out right away and skipped on later sends.
Know the limits before you plan around them: Text My Event sends to US and Canadian (+1) mobile numbers only, in English, and attendees need to have agreed to get texts about the event. For international attendees, keep email as the main channel.
For timing beyond conferences, see when to send event reminders.
Run this for your next event.
Schedule your texts in minutes. Try it with 10 free texts to your own phone. No app for guests, no credit card.
Start freeWritten by the people who build Text My Event, and checked step by step against the product as it works today.