For the host staring at an unread thread
Why Guests Don't Reply to Invitations, and How to Fix It
Silence is rarely rudeness. It is a reply that felt like effort, no visible deadline, and an invitation that arrived in the wrong place.
For the host staring at an unread thread
Silence is rarely rudeness. It is a reply that felt like effort, no visible deadline, and an invitation that arrived in the wrong place.
Hosts imagine a guest reading an invitation, feeling something, and choosing to ignore it. That almost never happens. What happens instead is that the guest reads it while standing in a queue, thinks they should answer properly later, and the moment passes. Three days on, replying feels awkward because it is late, so it drifts again, and by the time you need the number they have talked themselves into believing you assumed they were not coming.
The useful reframe is that non-reply is a design problem rather than a manners problem. Each of the four blockers below has a boring fix, and the fixes work whether or not the guest in question is being thoughtful.
Most missing replies trace back to one of these.
If a reply means writing a paragraph, choosing between dinner options and remembering a partner's full name, the guest defers it. The fix is a form with one question at a time: are you coming, how many seats, anything about food. Thirty seconds, then they go back to their day.
An invitation without an answer-by date is permanently not urgent, so it sits in the unread pile forever. Print the date on the page and repeat it in the message, worded the same way in both places. A concrete date creates a decision the guest can postpone only briefly.
Asking for a text response means the guest has to compose, and asking for a phone call means they have to be brave. A button on the page they already opened removes both. Whatever channel you choose, it should cost less effort than ignoring it.
A message buried in a busy group chat is genuinely hard to find again, and replying there means writing in front of forty people. Private threads get faster answers. If you use a group, follow it with the link sent individually to anyone whose answer you actually need.
Written to the person who has not replied, without guilt in the wording.
Hello Lena, quick one on Saturday. I'm confirming numbers with the caterer on Friday and I still need yours. Two minutes here if your plans are settled, and if they are not, tell me and I'll hold a seat until Thursday.
Marta, no pressure from me, but I'd hate to lose you both over a busy inbox. The reply page is open until Sunday evening. If you can't make it this time, say so and I'll put you first on the next one.
Even with all four blockers fixed, some proportion of a guest list will not answer. People travel, people have a difficult month, some find it genuinely hard to say no to an invitation. A host who chases those names to the last hour spends the day before the event badly and still ends up guessing.
The practical move is to decide a cut-off, treat silence as a likely no for catering purposes while keeping an open seat or two, and send one honest line to the remaining names the day before. That protects your headcount, your evening, and the relationship. A page with a deadline and a reminder makes the cut-off easy, because the unanswered list is short enough to handle one message at a time.
How it works
Build the invitation in the web app or through Jitabi, then set the answer-by date so it appears next to the reply button rather than only in your message.
Name, attendance, headcount, plus meal notes only if the menu needs them. Every question you delete is an answer you get back.
Private threads for the people whose answers matter, a group post for the celebration. One link, one line of your own words above it.
At your chosen point, send a reminder to the non-responders from the guest list. Keep one or two spare seats for the tail nobody reaches, and get on with the party.
Questions
Because replying in a group is public and the message is easy to lose. Guests read it, intend to answer, and the thread scrolls on. Sending the same link privately to the people you need counts on usually turns that silence into answers within a day or two.
Two is a normal number for a wedding, one is plenty for a dinner. Send them only to people who have not answered, keep the wording warm, and never send a third. Persistent chasing turns a guest who was busy into a guest who is annoyed.
It works on the ones who meant to reply and forgot, which is most of them. It does not convert a person who has decided to say nothing, so the deadline is about giving you time to plan around the few who stay silent.
Yes, if the answer is obvious. Telling a guest that their partner is welcome removes a question that otherwise arrives as a private message and delays the count. Where a plus-one is not possible, say so on the page and set the limit in the form.
Count them as a no for planning and tell them so kindly. A single line, I've had to finalise numbers and I've kept you in mind for the next one, is better than carrying an uncertainty into your own event.
Get Started
Short form, visible deadline, one reminder to the right names. Answers arrive without you having to ask twice.