RSVP etiquette in the group-chat era: how to reply well (and by when)

The invite used to come on stiff card stock with a little envelope. Now it comes as "anyone free saturday??" in a chat with fourteen people, and somehow that has made us all worse at answering. The etiquette didn't disappear when the paper did. It just got easier to ignore. This is the guest's guide to not being that person.

What "RSVP" actually means

It's French: répondez s'il vous plaît, or "please respond." Not "please respond if you feel like it," and definitely not "respond only if you're coming." The whole point of those four letters is that the host is asking you, directly, to close the loop. A yes closes it. A no closes it. Silence leaves it hanging, and the host is the one left holding it.

Why your reply actually matters

Behind every invite is someone doing math. How much food. How many chairs. Whether to book the big table or the small one. Whether the whole thing is even worth doing. When you don't answer, you don't stay neutral. You become a variable. The host either over-caters for a ghost or under-caters and stresses. Your five-second reply is the difference between a host who can plan and a host who's guessing.

How to reply well, and by when

Good replies are fast, clear, and specific. You don't owe an essay. You owe a decision.

1. Answer within a day. You knew your Saturday within about ten seconds of reading the message. The other 23 hours are just you avoiding it.
2. Give a real yes or a real no. "I'm in" or "can't make this one" both help. Mush doesn't.
3. Tap the button if there is one. A structured RSVP counts you in one tap; a message buried in 90 others does not.
4. Flag the plus-one and the diet up front. Not at the door. "Yes, plus my partner, and I'm veggie" saves a whole back-and-forth.
5. If your yes has a condition, say the condition. "Yes if my shift gets covered, I'll know Thursday" is honest. Just don't forget Thursday.

The "maybe" problem

Here's the hard truth: most "maybes" are a no wearing a nicer coat. Maybe feels kind because it doesn't reject anyone, but it quietly dumps the decision back on the host and keeps your options open in case something better lands. If you genuinely don't know, that's fine. Put a deadline on it: give a date you'll turn the maybe into a yes or a no, and then do it.

How to bow out gracefully

Declining is not rude. Ghosting is. You can miss the thing and still be a great guest.

And if you said yes and then can't come, tell the host the moment you know. A same-day drop-out with notice is forgivable. A no-show that they only understand when you never walk in is the thing people quietly remember.

Nobody's ever been mad at a fast, friendly no. They get mad at the silence that made them cook for a person who was never coming.

Withly

For hosts: how to get people to actually reply

Some of the silence is on you. If replying is a chore, people won't. Make the yes cheap and the deadline clear, and most of the flaking sorts itself out.

• Ask once, with a real date and time, not "sometime this month."
• Give one link that opens straight to the details and takes a one-tap RSVP, so nobody has to make an account to say yes.
• Put a reply-by date in the invite. "Let me know by Thursday" gets answers; open-ended asks get ignored.
• Send exactly one reminder the day before. One. More than that trains people to tune you out.

That's most of the fix: one clear ask, one link, one nudge. If you want the link that opens to the details and counts people in with just a name, that's what a Withly event is built to do.

Be the guest you'd want at your own thing. Answer fast, mean your yes, give a clean no when it's a no, and never let a plan die in silence. The etiquette survived the envelope. It just needs you to hit reply.