For the polite chase
The guest list already shows who is missing. One action sends a warm reminder back to their WhatsApp well ahead of your deadline, so the chase stops being a personal campaign.
The discomfort of chasing an RSVP is not really about the asking. It comes from doing it one by one, from memory, each message a small personal audition in which you pretend you have not been counting. Every reminder typed out of nowhere feels like pressure even when it is not.
Structure dissolves the awkwardness. The list sorts answered from unanswered, so you never have to remember who is missing. The reminder is one action aimed at exactly those names, sent when you choose. And the guest receives it as a friendly nudge carrying the invitation link, which is a different object entirely from a host asking to be validated.
Same message every time would be cold; these are for different moments of the chase:
Hi Aunt Elena, hope the date is working out for you. Marta and Tom's wedding page is here whenever you have a moment to tap yes or no. It genuinely takes ten seconds.
We are tying up final numbers for the caterer on Friday. If you can reply by then, your seat and your meal are ready; the page remembers the choices with your name.
No answer either way is fine, truly, but I need the headcount on Saturday. The link is here, and a tap is all it takes, and then I will stop hovering.
A reminder is only as good as what happens after it is read, and the answer is a link to the invitation page itself: the deadline visible, the button one tap away, meal choices and plus-ones answered on the spot. The guest who meant to reply last month, and forgot, finishes the job in the queue for the bus.
Reminders leave the app when you send them, to non-responders on WhatsApp or email as you choose. Nothing fires automatically, nothing nags people who already answered, and the count you finalise after the last reminder contains no ghosts.
How it works
Build the page, publish it, share the single link across your chats, and set the reply deadline guests will see on the page.
Replies arrive as rows over the following days. The names without a row are not a mystery; they are a list.
Open the non-responders view and send one warm WhatsApp or email reminder. It reaches exactly the people who are missing, and no one else.
When the deadline passes, the stragglers have been asked once, kindly, with the reason attached. The number you give the venue is the number you have.
Questions
No, and that restraint is the feature. You choose the moment and the group of names; reminders go to non-responders when you send them. A scheduled auto-nag arriving while the guest is typing yes is how reminder systems become spam.
If they never tapped the button, yes, because the list only knows what the list saw. Most hosts laugh about that, tell the guest to tap once for the record, and the name falls off the reminder list the same evening.
Either works. Reminders reach non-responders through WhatsApp or email, so a guest who lives in their inbox gets chased where they actually read.
The reminder action is aimed at the list of names that have not answered, so you are not typing twelve near-identical messages by hand. Each guest receives a single note carrying the invitation link, as if it were written for them, which in structure it was.
Then the reminder is the soft version of the call, with the deadline and the reason attached. For the guests who truly matter, hosts follow the nudge up personally, and the list has at least told you precisely whose name to dial.
Get Started
Start free and let the guest list show who is missing, so your reminders arrive with a reason instead of an apology.
