Two kinds of reminder, two different readers
A reply reminder goes to guests who have not answered the invitation. Its job is to get a yes or a no, and it should make answering take one tap. An attendance reminder goes to guests who have said yes. Its job is to make sure they come, on time, to the right place, with whatever they need to get in. Mixing the two is the most common mistake in reminder emails: a guest who accepted three weeks ago and then reads “we have not heard from you” starts to wonder whether their reply was lost.
Keep them as separate messages with separate lists, and you will find that each becomes shorter and clearer, because it is written for one reader.
An event reminder email schedule that works
The exact days depend on how far ahead you invited and how much guests must arrange, but most events fit this pattern. Not every event needs every step; a small dinner may need only the reply reminder and the day-before note.
- Reply reminder — about a week before the RSVP deadline, to everyone who has not answered.
- Last call — on the deadline or the day after, to those still silent, in a more personal voice, ideally from the host by name.
- One week before — to accepted guests: date, time, place, and anything they must prepare or book.
- The day before — to accepted guests: the practical note — arrival time, entrance, parking, the pass or ticket they will show.
- The morning of — only for larger or more complex events, and only if there is something useful to say: doors open, the weather plan, where to go first.
Who gets which reminder
Before each send, split the list by what each guest has actually done. This takes a few minutes and is the difference between a reminder that helps and one that irritates.
- Not replied — the reply reminder and the last call; nothing else until they answer.
- Accepted — the week-before, day-before and morning-of reminders; never another request to reply.
- Declined — nothing before the event. They may hear from you afterwards, with a different note.
- Maybe or tentative — one gentle request to confirm, close to the deadline.
- Bounced — not a reminder at all. Find the right address and send the invitation again.
- Unsubscribed or complained — nothing, ever, from this sender. Contact them another way if it truly matters.
What to write in a reminder email
Put the reason for the message in the subject line and the most important fact in the first sentence. “Reminder: Spring Reception, Thursday 7 pm” works better than “Don’t forget!” because a guest scanning the inbox learns what they need without opening it. For a reply reminder, the first line is the question and the button to answer it; for an attendance reminder, it is the date, the time and the place.
Keep each reminder shorter than the invitation. Repeat only what the reader needs for the next step, and link to the event page for the rest. If the guest has a personal pass or QR code for the door, put it — or the link to it — where they will find it in a hurry on the night, near the top rather than below the signature.
- Reply reminder: “We would love to know if you can join us on 12 June — answering takes a few seconds.”
- Week before: “See you next Thursday. Doors open at 6.30 pm at the Garden Room, 40 Wharf Street.”
- Day before: “Tomorrow at 7 pm. Use the river entrance; your pass is below and opens on any phone.”
- Morning of: “Doors open at 6.30 tonight. It is likely to rain, so the welcome drinks have moved inside.”
Changes reach only the people they affect
A change is not a reminder, and it should not travel like one. If one session moves rooms, only the guests in that session need to know. If the start time moves, every accepted guest and every guest who has not yet answered needs to know — but the declined guests do not. If one guest’s plus-one is added, that guest needs a new confirmation, not the whole list.
Send a change as its own message, with the change in the subject and in the first line — “New time: the reception now starts at 7.30 pm” — and the old detail named so nobody can confuse the two. Then make sure every later reminder already carries the new detail. A day-before email that repeats the old time undoes the correction you sent a week earlier.
Never resend to everyone
The fastest way to make a reminder campaign look careless is to send the invitation again to the whole list. Guests who replied assume something has changed, guests who declined feel pressed, and mail providers see a burst of repeat messages to people who did not engage the first time — which is exactly the pattern that sends later messages to spam.
Before any reminder, read the delivery record of the invitation. An address that bounced needs a new address, not another attempt. An address that was delivered but never opened may deserve a reminder with a different subject line. An address that opened without replying gets the reply reminder as written. And an address that asked not to be contacted stays out of every send.
Timing, sender and tone
Send from the same sender as the invitation, so the reminder is recognised and threads naturally with what came before. Send in the guest’s daytime — for an international list, that may mean sending in waves by time zone — and avoid the hours when a message will sit under a night’s worth of newsletters. Keep the tone warm and brief; a reminder that sounds like a demand is answered less kindly than one that sounds like a host looking forward to the evening.
- Separate lists for reply reminders and attendance reminders.
- A schedule written down before the invitation goes out.
- Segments by what each guest did: not replied, accepted, declined, bounced, unsubscribed.
- The fact first, in the subject and the first line.
- Changes as their own message, only to those affected.
- Later reminders checked for the new details.
- The delivery record read before every send.