Skip to content
tinyhubs

Guide

How to get RSVPs from a group that ignores you

The short answer: lower the cost of answering to two taps, deliver the ask where people already are, and chase the named silent few instead of re-broadcasting to the compliant many. Silence is friction, not refusal — treat it that way and most of it disappears.

The organizer’s lament

Every organizer knows the shape: twenty-two people, a Saturday game, and by Thursday you have nine answers. One rec-group organizer put the experience perfectly — ninety-nine percent of members look and vote and never respond, and when the no-shows are asked about it afterward the answer is a shrug. The temptation is to conclude your group doesn’t care. The data says otherwise: they came to the game. They just never told you.

Why they didn’t answer

Three causes cover nearly everyone. They never saw it — the ask scrolled past in the chat (here’s why). Answering cost too much — a new app, an account, a login they forgot. Every step between “saw it” and “answered” sheds a fraction of your group, and the ones it sheds are precisely the least-engaged people whose answers you’re missing. Or they answered in their head — decided they’re coming, felt done, recorded nothing.

The pattern that works

Make the ask an object with a link

The RSVP should live at a stable link that shows the thing and two buttons. Paste that link into the chat your group already uses. No install, no account gate — anyone who can tap a link can answer. (This is exactly how TinyHubs events behave, and why.)

Chase names, not the room

“Reminder: please RSVP everyone!!” is read by the fourteen people who already did and muted by the five who didn’t. The working chase names the five: “Still need Ava, Ben and Priya for Saturday — [link].” It’s shorter, kinder, and it works, because a named ask is a social object in a way a broadcast never is. The prerequisite is a tool that knows who hasn’t answered — keeping that list in your head is the job you’re trying to quit.

Let people answer for their people

In family groups, chasing a nine-year-old is absurd and chasing “the household” chases nobody. The ask should route to whoever answers for the participant — either parent — and record who answered.

Close the loop visibly

“Game on — 16 confirmed” posted back to the chat teaches the group that answering produces outcomes. Groups RSVP better when RSVPs visibly matter.

What to stop doing

Stop adding reminder notifications — each one trains more people to mute you. Stop counting thumbs-up reactions as data — they aren’t commitments and can’t be tallied. And stop apologizing when you chase by name; you’re doing the group’s job with the group’s tools, which is what an organizer is.

The who-hasn’t list with a one-tap chase message is TinyHubs’ favorite feature for a reason. Watch it work in the sample hub →