How to get your group to actually RSVP
Nobody is ignoring you. They are reading your question in a chat with 40 unread messages, deferring it, and never returning. Here is how to fix the mechanism.
The Sail Team6 min read
You asked a clear question in the group chat four days ago. Two people replied, one of them with a thumbs up you cannot interpret, and the trip is now blocked on five people who have definitely read it.
This is not a friendship problem. It is a mechanism problem, and mechanisms can be changed.
Why group chats produce silence
Three things are working against you, all at once:
- Diffusion of responsibility. A question addressed to eight people is addressed to nobody. Each person assumes someone else is handling it — a robustly replicated finding, and a perfect description of a group chat.
- Deferral without return. Your message arrives while someone is mid-something. They intend to answer later. Eleven messages arrive on top of it. There is no later.
- No cost to silence. Not answering is free and slightly comfortable, because a non-answer keeps options open. Every hour you leave that true, you are asking people to volunteer for a small loss.
Each tactic below removes one of those three.
1. Ask one person at a time
Individual messages get individual replies. It feels like more work — eight texts instead of one — but you will spend less total time than you would on four rounds of chasing a group thread, and the response rate is not close.
If eight messages sounds like too much, that is precisely the task worth automating. Sail sends the RSVP to each person individually and collects the answers into one list, which is the same tactic without the typing.
2. Make the answer a tap, not a sentence
"What do you think about the dates?" requires composing a reply, which requires attention and a free hand. "Can you do March 14–18? Y/N" requires one character.
Every unit of effort you remove raises the response rate more than you would guess. A yes-or-no question sent by text gets answered while someone is standing in line — an open question waits for a moment of focus that may never arrive.
3. Attach a deadline and a default
A deadline alone still lets people wait. A deadline with a stated default makes silence into a decision:
Booking the house Thursday night. I'll assume you're out if I haven't heard by then — no hard feelings either way, I just need the number.
This is not a threat, and it should not read as one. It is a fair, dated chance to answer, and it inverts the incentive: silence now costs something.
4. Publish the running count
"6 in, 2 to go" does more than any reminder. It supplies social proof, it makes the holdouts visible without naming them, and it signals that the trip is really happening — which is often the actual thing people are waiting to learn.
5. Ask for money, not for words
The single most reliable filter is a deposit. Not because you need the cash on that date, but because paying anything converts an intention into a commitment. A person who has sent $50 is a different person from one who sent an emoji.
Keep the amount small enough that it is not itself a decision. $50 filters nearly as well as $300 and gets you an answer far faster.
6. Send it where they actually are
Every additional step between your question and their answer costs you responses. If answering requires downloading an app, making an account, and finding the right screen, you have lost most of your group before the question is even read.
Text messages get opened. This is the entire reason Sail runs RSVPs and polls over SMS rather than through an app — the people you are inviting do not have to install anything, and the reply is one tap in the messages app they already have open.
7. Follow up once, then stop asking
One reminder, on the deadline day, is effective. The third reminder is not — it teaches the group that your deadlines are soft, which makes every future deadline weaker.
Send the one reminder, apply the default you announced, and move on. Groups adjust quickly to organizers whose deadlines turn out to be real.
A message you can copy
Lisbon, March 14–18. Roughly $850 each, all in. I need a yes or no by Thursday so I can book the place — $50 to hold your spot. 6 in, 2 to go. No worries at all if it's a no, just tell me so I can size it right.
That is short, closed-ended, dated, priced, socially proofed, and gives an honest out. Nearly every non-response to a trip invite is a failure of one of those six.
Once you have your yeses, the next problem is logistics — see how to plan a group trip and the itinerary template.
Frequently asked questions
How many times should you follow up on an RSVP?
Once. Send the reminder on the deadline day, then apply the default you announced. Repeated reminders teach the group that your deadlines are negotiable, which makes every future deadline less effective.
Is it rude to set a deadline for friends to respond?
No — it is the opposite. A deadline with a stated default tells people exactly what is expected and gives them a graceful way out. What actually strains friendships is an organizer chasing the same question for three weeks.
Should I ask for a deposit from friends?
If you are personally fronting a booking, yes. Keep it small — $50 filters almost as well as a larger amount and gets you answers faster. Frame it as holding a spot rather than as paying you, and say up front whether it is refundable.
What is the best way to collect RSVPs for a group trip?
Ask each person individually, make the answer a single tap, and send it somewhere they already are — SMS beats app notifications and group chats by a wide margin. Then track the yeses in one list rather than by scrolling back through a thread.