RSVP Follow-Up Messages: 18 Templates That Actually Get Replies

Nineteen households. That's how many hadn't replied when a friend of mine hit her RSVP deadline last spring, out of a list of 91. She'd assumed maybe five stragglers. Nineteen.

She got sixteen of them within four days, and it wasn't because she found a clever phrase. It was because she stopped posting "PLEASE RSVP 🙏" on Instagram stories and sent nineteen separate messages instead.

That's the whole method. Individual, specific, easy to answer. Everything below is just wording for it.

The timing

Five days before the deadline — reminder. Cheap, effective, almost nobody does it. Pulls in a good chunk of people who always intended to reply and hadn't got round to it.

Three to four days after the deadline — first follow-up. Not the day after. The day after reads as anxious and catches people who mailed a card that's still in transit.

Five to seven days after that — final check. Then you're done chasing.

Stop. After two attempts, mark them as not attending and move on. Emily Post is direct that responding is the guest's obligation, not the host's problem to solve forever — at some point you close the list and get on with your life.

Rule one: never send a group message

A group text saying "hey, a few of you haven't RSVP'd!" is read by every recipient as being about someone else. Every single one of them. It's the most reliable way to get zero responses from twelve people simultaneously.

One message. One household. Their name in it. That's it.

Pre-deadline reminders

1. Text

Hi Maya! Quick reminder that RSVPs for the wedding close this Saturday — if you haven't sent yours yet, the link's here: [link]. No stress either way, just want to make sure we don't miss you.

2. Email

Subject: RSVP closes Saturday — Marcus & Elle

Hi everyone,

Replies for October 14 close this Saturday the 11th. If you've already responded, thank you — ignore this entirely.

If not, it takes about thirty seconds: [link]

Marcus & Elle

Number 2 is the one exception to the no-group-messages rule, because it's a reminder rather than a chase and it explicitly excuses the people who've already replied. Once the deadline has passed, go individual.

First follow-up: text and WhatsApp

3. The standard

Hi Dev! Hope you're well. We're finalising numbers for the 14th and I don't think we've got your reply yet — are you and Anjali able to make it? Either answer is completely fine, we just need to let the caterer know by Friday.

4. Shorter

Hey Sam! Just doing the final headcount for the wedding — are you in? Yes or no is perfect, no need for a whole message.

5. Warm version, for people you actually see

Hi Grace! Chasing you for the least fun reason — we need the wedding headcount by Friday and I don't have yours. Can you let me know if you're coming? Would love to see you there.

6. When you suspect they never got it

Hi Tomás! Small chance our invitation got lost — did you receive it? It went out on the 20th to your Elmwood address. Here's the details either way: [link]. Just need to know if you can make the 14th.

Number 6 is worth using more often than you'd think. Post goes missing, emails filter into promotions, and some people are mortified to admit they can't find something you sent. Giving them the out gets you a fast answer.

First follow-up: email

7.

Subject: Are you able to join us on October 14?

Hi Priya and Nate,

We're putting the final numbers together for the wedding and I don't think your reply came through. Are you both able to make it?

You can reply here: [link] — or just answer this email, that's easier.

Thank you! Elle

8. Slightly more formal, for colleagues or older relatives

Subject: Kindly confirm — October 14

Dear Mr. and Mrs. Whitfield,

We hope this finds you well. We're confirming final numbers with our caterer this week and wanted to check whether you'll be able to join us on the 14th.

A short reply either way would be a great help.

With warm wishes, Marcus and Elle

"Or just reply to this email" is the single most useful line in any follow-up. Removing one click removes one reason to postpone. Keep whichever channel they use into the same list as everything else, though — replies scattered across email, text and a form is how a headcount goes wrong at the last minute.

The awkward ones

A close friend who's gone quiet

Usually means something's going on, or they can't afford it and don't want to say.

9.

Hey — no pressure at all on this, but I wanted to check in properly rather than keep sending reminders. Are you good? And are you able to make the 14th? Honestly a no is completely fine, I'd just rather know than wonder.

10.

Hi Ben, I'm going to take the awkwardness out of this — if you can't make it, just say so and it changes nothing between us. I only need to know for the numbers.

Say the no is fine and mean it. Nine times out of ten that's exactly the permission they were waiting for.

"We'll try to make it"

The maybe. Useless for planning, and if you let it sit it becomes a yes by default and then a no by absence.

11.

Totally understand! Unfortunately I have to give the caterer a firm number on Friday — can you let me know by then either way? If it's genuinely uncertain, I'd rather put you down as a no and be delighted when you turn up.

12.

No problem — can I put you down as a yes or a no for now? I can update it up until the 8th if things change.

Number 12 works because it gives them a reversible answer, which is what they wanted in the first place.

The elderly relative who doesn't do links

Just call. Script, roughly:

13.

"Hi Auntie Rose, it's Elle. I'm just ringing round for the wedding numbers — are you able to come on the 14th? ... Wonderful. And will Uncle Ray be with you? ... Perfect, I've got you down for two. Nothing else you need to do, I've written it down at this end."

The last line matters. Tell them the job is finished so they don't worry about the card.

Someone who replied for people who weren't invited

14.

Hi Denise! Thank you so much for replying. Quick note — we've reserved two seats for you and Paul. We had to keep the numbers tight so unfortunately we can't stretch to the kids for the evening, though we'd love them at the ceremony if that works?

15.

Thanks Denise! Just so I've got it right — the invitation is for you and Paul. Is that the two of you attending?

Emily Post has a whole section on handling RSVPs that include uninvited guests, and the consistent advice is to correct it early and directly. It's much worse a month later.

A yes who's gone silent since

16.

Hi Nadia! You're still down as a yes for the 14th — just double-checking that's right before I send final numbers on Friday?

Closing the list

17. Final check

Hi Josh, last one from me on this — I need to send numbers tomorrow. If I don't hear back I'll assume you can't make it, which is absolutely fine. Hope to see you either way.

18. Marking them as a no

Hi Kirsty, no problem at all — I'll take you off the list for the 14th so you're not chasing it. If anything changes before the 8th just let me know, I can usually add someone late.

Number 17 does most of the work in this article. "If I don't hear back, I'll assume no" is a soft deadline with a real consequence, and it converts a surprising number of people who genuinely meant to reply three weeks ago.

How to not need most of these

Half the chasing disappears if the reply is easy in the first place. A single link, a QR code, and no login. Nothing gives guests the ick faster than being asked to create an account to say they'll eat some chicken. If you're sending digitally, the tool can usually show you exactly who hasn't opened or replied, which turns "who do I chase" from a spreadsheet exercise into a two-minute job.

The other half disappears with a deadline that leaves you room — set it two to three weeks before your caterer needs numbers, not on the same day.

Send the nineteen messages in one sitting. It takes about twenty minutes and it will feel worse in your head than it does in practice — nobody has ever been offended by "can you make it on the 14th?"