Guest reminders: what to say and when to send them

One message, one primary action

Before drafting, complete this sentence: after reading this, the person should be able to do this. Maybe you need them to RSVP, check their invitation, or know that the entrance moved. If four distinct actions pop up, separate the urgent from what can wait. A reminder shouldn't turn into a second invitation rehashing the entire background of the event. Repeat the essential details so it makes sense on its own, but cut out anything that doesn't impact an immediate decision.

Also, distinguish between a reminder and an announcement. Reminding someone of a previously shared time is different from changing it. If there's an update, put it right at the top and say it plainly: the arrival time has changed. Don't bury it beneath celebratory greetings or assume people will compare two versions side by side. That clarity is especially critical when someone reads a quick notification or coordinates rides with others on the go.

Group recipients by what they need to know

Not everyone needs the same message. Those who have already confirmed need arrival instructions; those who are still pending need an easy way to RSVP; those who can't attend rarely need more logistics. Before sending, review your guest list and update recent replies. If multiple people are organizing, agree on who handles follow-ups so guests don't receive two different reminders on the same afternoon.

Segmenting can be very simple: three temporary lists or filters within your guest roster. There's no need to build complex profiles or collect extra data. If the message contains an individual invite or personal link, verify that each recipient receives their own. Avoid attaching the complete guest list to point out who hasn't replied yet. Private communication usually solves the issue without broadcasting names, contact info, or attendance statuses to the whole group.

Read more: How to ask for RSVPs without feeling awkward.

Send RSVP reminders with a gracious exit option

An RSVP follow-up should specify the event, the deadline, and the expected action. For example: Hi, we're finalizing numbers for dinner on November 18. Could you let us know by Monday if you'll be able to make it? If you can't join this time, no worries at all; it helps us to know either way. The message makes it easy to say yes or no without justifying the answer. If the invitation extends to multiple people, mention that you need the final headcount for the invited party.

There is no universal frequency. A small gathering with close friends might only take a single conversation; an event with vendor commitments might require an earlier check-in. Decide based on your actual planning deadline, not a marketing template. Avoid sending back-to-back messages whenever you spot someone online or see a read receipt. Being available to open an app doesn't mean someone is ready to finalize their calendar.

Draft an easy-to-reference arrival reminder

The pre-event message should work like a quick fact sheet. Include the event name, full date, arrival time, location, and a helpful tip about entering. If there's a gap between arrival and the start of an activity, state both times clearly. Add a point of contact for day-of issues and, when applicable, remind guests to have their invitations ready. A note about parking is only helpful if the details have been confirmed and don't promise spots outside your control.

Picture someone opening the message while traveling. Can they find the address and entry details without downloading a heavy file? Is it clear if the entrance is on a side street? You can link to secondary details, but the essential information should be right there in the message text. Double-check the location link before sending, and avoid posting private addresses or access details publicly when hosting a private event.

Arrival reminder template

This text is a sample template. Replace the bracketed placeholders and keep only what the guest needs to get there.

“Hi, [name]. A quick reminder about [event name] on [full date]. We look forward to seeing you at [arrival time] at [location]; the program begins at [start time]. Please enter through [entrance details]. If you need anything on the day of the event, text [contact name/number]. See you soon!”

The essentials appear right away: event name, date, arrival time, and location. If the message takes up more than one mobile screen, move secondary details to a link. If entry requires a code, review how to manage event check-in with QR codes.

Treat changes as priority alerts

If the venue, date, or a key detail changes, use a dedicated update. State what changed first, followed by the new information, and finally what response you need. For example: The gathering has moved to Sunday the 22nd; the location and time remain the same. Could you let us know if this new date works for you? Silently editing an image that was already shared isn't enough, because some people will keep the old version or rely on a screenshot.

Identify guests who might miss the update in time, especially if they are traveling or organizing a group. Follow up via a channel they already use, without sharing phone numbers or requesting unnecessary public confirmations. If one person is coordinating for an entire family, confirm they agreed to take on that role. Don't assume an update is communicated just because the message was sent: for high-impact changes, verify that it reached the designated point people.

Read more: How to reschedule an event without causing confusion.

Does the update replace an instruction or merely add another?

When a door changes, the reminder should identify the instruction it replaces. A second address without explanation can look like a complete venue change. Name the event and date, say the time and building remain unchanged when confirmed, and describe the current entrance. Date the notice to distinguish it from an old screenshot. Sending it does not prove every guest received or read it.

Review channels you control: the current invitation, pinned message, and welcome-team wording. Ask cohosts to relay the correction wherever they shared the old version without promising to erase every copy. Request any specific reply separately. Revised wording does not replace checking that the door will be available and someone will welcome guests there.

Review tone, timing, and length

Read your message out loud before hitting send. If it sounds demanding, trim explanations and return to the specific action. Phrases like “you haven't responded yet” can be reworded to “we're finalizing the guest count.” Avoid guessing the reasons behind someone's silence or implying that an absence will ruin the event. Warmth doesn't require a string of emojis or a lengthy greeting; addressing someone by name and explaining what you need with natural phrasing is usually enough.

Pick a considerate time of day for the recipient and keep time zones in mind when relevant. In a true emergency, the priority is alerting people right away; for a routine RSVP, there's no need to wake someone in the middle of the night. Also check how it looks on a phone screen. The first section should state the purpose and the action. If it looks like a solid wall of text, add line breaks and remove details that are already resolved.

When you shouldn't send a reminder

Before scheduling a message, verify that it provides fresh value. In these cases, it's better to hold off:

• The person has already answered and their response still stands.
• The detail you plan to remind them about was already shared via the same channel and hasn't changed.
• There is no pending action for that person—for example, if they've already declined.
• The timing is unreasonable for their time zone or typical schedule.

When in doubt, ask before broadcasting. An unnecessary message dilutes attention away from the reminder that truly matters.

Close the loop after sending

The work doesn't stop once you hit send. Log responses, update headcounts, and pass along only the relevant updates to your team. If someone asks for clarification, check if the wording was confusing for others before answering individually twenty times. A repeated question usually means the message is missing the exact door, the full date, or the allowed plus-one count. Update your reference details and send the clarification only to those who genuinely need it.

Convite can be part of your QR invitation workflow, but don't present this editorial guide as an automated reminder feature within the app. Check the features you are using and keep a human touch on all communications. After the event, retire your temporary logistics lists. A late reminder, an outdated date, or a message sent to someone who already cancelled can all be prevented with one final check of everyone's status.