Event Reminder Emails: Sequence and Examples
An event reminder email is an automated message sent between registration and event start that keeps a registrant committed and prepared. A complete sequence uses four to six sends — instant confirmation, a one-week nudge, a one-day reminder, a start-time alert, and a follow-up — each carrying the join link and the single next action.
Why the reminder sequence carries the whole event
Registration is not attendance. For free virtual events, the gap between the two is brutal: show-up rates commonly land somewhere in the range of 35-50% of registrants, and the number climbs or collapses almost entirely on the strength of your reminder sequence. Paid and in-person events fare better because money and travel create commitment, but the pattern holds.
The good news is that this is the cheapest lever you have. You already paid to acquire the registrant. Adding two well-timed messages costs nothing and reliably pulls attendance up several points. Every reminder should do three jobs: restate the value, remove a friction, and make joining a one-tap action.
The full sequence, send by send
| # | Timing | Purpose | Primary CTA |
|---|---|---|---|
| 1 | Immediately on registration | Confirm, deliver calendar file and join link | Add to calendar |
| 2 | 7 days before | Re-sell the value, share the agenda or speaker | Read what you will learn |
| 3 | 1 day before | Logistics: time zone, link, what to bring | Confirm your spot |
| 4 | 1 hour before | Urgency and the link, nothing else | Join now |
| 5 | At start time (optional) | Catch late joiners; skip for in-person | We are live |
| 6 | 2-4 hours after | Replay, resources, next step | Watch the recording |
Short registration windows compress this. If someone signs up two days before the event, they should skip send 2 entirely and drop straight into the one-day reminder. Build that branch into the automation rather than letting people receive a seven-day notice about an event happening tomorrow.
Send 1: the confirmation that does real work
Most confirmations waste their best asset — they get opened at rates far above anything else you will send, often in the 60-80% range, and then say nothing but thank you.
Put these five things in it: the event name, the date and time with the time zone spelled out, an .ics calendar attachment or add-to-calendar links, the join link itself, and one sentence on what the attendee should expect to walk away with. If there is prep work — a worksheet, a survey, an account to create — this is where it goes, not in the one-day reminder when nobody has time.
Subject line examples
- You are in: [Event name], Thursday at 2pm ET
- Confirmed — here is your join link for [Event]
- [Event] is on your calendar. Two things to do first.
Send 2: the value reminder, one week out
A week out, nobody remembers what they signed up for. This email is not a reminder — it is a second sell. Lead with the outcome, not the logistics.
Formats that work: a three-bullet agenda; a short quote from the speaker; one surprising thing you will cover; or a two-sentence note from the host written in plain first person. Keep the join link present but secondary. If registration is still open, this is also your best forward-to-a-colleague moment — add an explicit line asking for it.
Send 3: the day-before logistics email
This is the highest-leverage send in the sequence and the one most teams write carelessly. Strip it to essentials:
- Exact time in the reader's likely time zone, or list two or three zones. Time zone confusion is the single most common reason people miss virtual events.
- The join link, as a button and as visible plain text — corporate mail clients sometimes strip buttons, and some people forward the message to a phone.
- What to have ready: headphones, a document, an account login.
- What happens if they cannot make it: state plainly that a recording is coming. Counterintuitively this raises attendance, because it removes the anxiety that drives people to just skip.
- A reply-to that a human monitors. People do reply to these with questions.
Send 4 and 5: the hour-of nudges
The one-hour email should be the shortest thing you send all quarter. One line of context, one button, one link in text. No header image, no navigation bar, no footer full of social icons — many people open this on a phone while walking to a desk.
The at-start-time send is optional and depends on your audience. For internal or B2B webinars it reliably picks up a slice of late joiners. For consumer events it can read as pushy. Test it once and keep it or kill it based on what happens, not on opinion. If you send both, suppress send 5 from anyone your platform already shows as joined.
Send 6: the follow-up that converts
Split your post-event list into two segments and write two versions. Attendees get the recording, the slides, any promised resource, and the specific next step — a demo, a trial, an offer that was mentioned live. No-shows get a warmer version: sorry you missed it, here is the replay, here are the two things people asked about most.
Send within a few hours while intent is still hot. If your recording is not ready, send a short holding email at four hours and the recording the next morning rather than waiting three days for a perfect asset.
Building it as automation, not manual sends
All six messages should live in one triggered workflow keyed to the registration event, with relative-to-event-date timing rather than fixed dates. That way the same sequence powers every event you run and you only swap the copy. Our guide to email automation workflows walks through the trigger and delay structure, and the email template library gives you reminder layouts you can drop the details into.
Two operational rules. First, reminders are transactional in nature — someone asked for them — so they should not be suppressed by marketing frequency caps, but they still need a working unsubscribe path if you are sending in a marketing context. Second, always suppress cancelled registrants and, where possible, people who have already joined. Nothing damages trust like a reminder to attend something you are currently attending.
Frequently asked questions
How many reminder emails should I send before an event?
Four to six for a typical virtual event: confirmation, one week out, one day out, one hour out, and a follow-up. Add a start-time nudge if your audience responds well to it.
Do event reminder emails hurt my unsubscribe rate?
Rarely, if the timing is tight to the event and each message is short. Complaints come from vague, repetitive reminders, not from frequency. Keep the sequence contained to the registration window.
What should the subject line of a reminder email say?
Put the time and the event name in it. Subject lines like "Starting in 1 hour: [Event name]" outperform clever ones here because the reader is scanning, not browsing.
Should no-shows get the recording?
Yes. No-shows still raised their hand, and the replay email is often your best re-engagement message. Write a separate version for them rather than reusing the attendee email.
How do I stop people from missing the event because of time zones?
Spell out the time zone in every subject line and body, list two or three major zones, and attach a calendar file at registration so the reader's own calendar does the conversion.
Want reminder sequences that fire on their own, with unlimited contacts and 99% inbox deliverability behind them? Build your event automation with IGSendMail.