People are not ignoring you
It is worth knowing why an invitation goes unanswered, because each reason has a different fix and none of them is “remind them harder”.
- They have to check with someone - a partner, a co-parent, a shift rota. They will reply when they know, and they have not forgotten.
- They are waiting to see who else is going. Common, slightly unflattering and completely normal.
- They want to say no and cannot find a comfortable way to phrase it, so they say nothing and hope it resolves itself.
- They read it while walking to a meeting, meant to reply properly, and the message moved up the screen.
- They think it is obvious they are coming and that saying so would be strange.
Make “no” as easy as “yes”
This is the single highest-return thing a host can do, and almost nobody does it. Give people explicit permission to decline, in the invitation, in one line. It costs you nothing and it converts a large share of the silence into usable answers.
The reason it works: a guest who cannot come is carrying a small social debt every time they see your message. Removing the awkwardness removes the reason to avoid replying. You would far rather have an early no than a maybe that becomes an empty chair at a table you have paid for.
Completely fine either way - I’d just rather know than wonder, so a quick “can’t this time” is genuinely as useful to me as a yes.
Work the deadline backwards
A reply-by date only feels real when it is attached to something. Start from the thing you actually have to commit to, add the time you need and let that produce the date rather than picking a round number.
| What you are committing to | Time you need | So ask by |
|---|---|---|
| Restaurant booking | The venue’s own confirmation deadline, plus two days of slack | Usually 4–7 days before |
| Cooking at home | A shop and a prep day, plus time to adjust for dietary needs | 4–5 days before |
| Caterer or bulk order | Their final-numbers deadline, plus three days | 1–2 weeks before |
| Tickets at a fixed price tier | Before the tier changes or the allocation sells | Whenever the sale opens - say so |
| Anything with travel or accommodation | Long enough for guests to book their own | 4–6 weeks before |
The three-message sequence
- The ask. Full details, a specific reply-by date, one obvious way to answer and the line that makes declining easy.
- One group reminder, two or three days before the deadline. Sent to everyone who has not answered, framed around your logistics rather than their manners.
- Individual nudges, after the deadline, only to the people still outstanding. A direct question to one person is a completely different thing from a fourth broadcast.
Nudge on Saturday - I need to give the restaurant final numbers on Thursday morning, so could you let me know before then? Genuinely fine if it’s a no, I just need the count. Details and RSVP here: [link]
Hello! Just you and one other left for Saturday - can I count you in? Either answer is fine, I’m booking on Thursday.
Booking the table at 9am tomorrow for the eleven people who’ve confirmed. If you’re not on that list and you’d like to be, tell me tonight and I’ll add you.
What to do with “maybe”
Maybe is a legitimate answer when the reason is real and dated - a shift they will know about on Friday, a train they might not catch. It is not an answer when it means “I would rather not commit in case something better comes up”, and the difference is usually visible in whether they told you when they would know.
Ask a maybe for the date they will be able to decide, and if that is after your deadline, tell them what you will assume. Being counted out is not a punishment, and most people would rather be asked than quietly written off.
- For a fixed-cost booking, count only confirmed yeses. Maybes are a bonus, not a headcount.
- For a casual gathering at home, expect roughly one in ten confirmed guests not to arrive, and a higher share in bad weather.
- For anything where guests have paid, expect almost everyone to turn up.
- Tell a maybe what the cut-off is, plainly, and let them choose.
Keeping the answers in one place
Reconstructing a headcount from a chat thread is the part that actually costs the evening - scrolling for a yes from nine days ago, wondering whether a thumbs-up counted, adding it up twice and getting different numbers.
Status Social records the answer against the guest, so the list is the count. Guests can change their mind without you missing it, and you can see who has not replied without scrolling anything.