For the date behind the date
Guests see the reply date on the invitation page itself. As it nears, anyone who has not answered gets one polite nudge before you finalise the numbers, so the deadline does the chasing for you.
Almost every invitation carries the date of the party and no date at all for the answer. That omission is the reason I will let you know survives for five weeks, and the reason the host ends up assembling a headcount by archaeology the night before it is due.
A reply deadline is a promise about when silence stops being neutral. It gives the guest a second, smaller occasion to prepare for, and it gives the host a moment the numbers can legitimately close. Both effects only work if the date is visible where the question is asked, which is on the invitation page itself, beside the button.
The sentence that carries the date does most of the work, and a reason makes it stick:
Please reply by the twenty-first of March. It is the date we hand the restaurant their final numbers.
We have held a table until the first of June. After that we have to release the extra seats, so tap your answer before then and keep your place at it.
The reply date is Friday and the cake is confirmed Saturday, so if you have not tapped yet, the page is right here. Marta is saving Tom a seat and hopes you can take it.
Set the reply date when you build the invitation and it lives in the guest's view, part of the same screen as the question, so nobody can honestly say they did not know. There is no separate terms email and no fine print; the deadline is written into the event the way the venue is.
As the date approaches, the guest list shows its blanks with precision, and one action sends a reminder to exactly those names on WhatsApp or email. Nothing fires on a schedule by itself: you choose the moment, the list chooses the recipients, and the message carries the page link so the reply can be finished on the spot. When the date passes, you finalise from the list you have, which is the version with no ghosts in it.
How it works
Build the page, place the reply deadline beside the button with its reason in the wording, and publish the invitation into the chats.
Answers land on the guest list as rows. The deadline does most of the pulling at this stage simply by being visible.
A few days out, send one reminder to the names still missing, on WhatsApp or email, from the list rather than from memory.
The count closes when you said it would, the restaurant gets a real number, and the evening stays yours instead of a running negotiation.
Questions
A tap still reaches the list whenever it happens, because replies land when guests act. The deadline is the date you said you needed answers; after it, a late yes is a spare-seat conversation held on the record, and the host decides.
A reason does the softening. Saying we must confirm the restaurant by Friday is not bureaucracy, it is the cake and the table booking, and guests answer dates that carry consequences far more reliably than dates that carry only eagerness.
No, and you are better for it. You send reminders from the non-responder list yourself, choosing the moment, so the nudge arrives as your timing rather than a machine's, and nobody already answered gets pinged.
The blanks are already gathered for you, so a final reminder or one phone call covers a named group rather than a mood. The number you hand over is built from confirmed answers, which is the entire point of setting the date.
The page carries one date, so the honest way to do it is a separate personal note to the few travellers asking for their answer sooner. Better still, set the single deadline early enough that distance is comfortably covered.
Get Started
Start free, put the reply deadline on the invitation page, and one warm reminder before it is all the chasing the evening needs.
