For hosts chasing answers through chat logs
Scrolled-back chats and half-answers stop here. A workable tracking habit comes down to one list holding every guest, the answer they gave and the plus-one they brought, so missing replies surface by themselves.
There are only ever three groups of guests: people who said yes, people who said no, and people you cannot place. Hosts spend their attention on the first group because those answers feel warm and arrive unprompted, and the evening is ruined by the third, which stays invisible until the numbers are due.
Tracking is not cleverness; it is bookkeeping with a kind face. The practice is to keep one list, give every answer a fixed destination, and compare the two often enough that the gap shows itself while there is still time to close it.
Not per chat, per thread or per memory. A guest exists in one place, so an answer, or the absence of one, attaches to a single entry.
Replies must land somewhere other than the conversation they were invited from. A button on the invitation page turns an answer into a record the moment it is given.
Counting yeses is trivia; listing the names without answers is tracking. The second task is the one that pays for itself.
A reply deadline gives silence a shape and turns endless waiting into a date you can act on.
My Joyfullday is where the practice happens rather than something that happens to you. The Lindqvist family wedding, invited through four different WhatsApp chats, still produced one guest list, because every chat carried the same single link and every reply landed on the same page. Before the day, the list separates the answered from the missing, and reminders go to the missing names. On the day, a QR check-in at the door marks arrivals against the same record, so tracking runs from first invitation to last guest coat.
Be clear about what this does not claim. There is no open or click tracking on the message you sent, and no bot reading group history to mine for maybes. Tracking works because answers arrive in one place by design, not because your chats were surveilled.
How it works
Publish the event page and send its single link to every chat you had planned, so invited and answered live in the same system.
Each tap writes a name, an answer and a party onto the guest list, with meal choices kept alongside.
A week out, the names without answers are what you look for. That list is short, specific and entirely actionable.
QR check-in at the door turns the tracked list into a tracked arrival record, so who-came is as answerable as who-replied.
Questions
No, and no honest tool can. A message in WhatsApp tells the sender only that it was delivered. Tracking that matters starts after the guest taps the link and gives an answer on your page, which is a fact rather than a hint.
Only an answer given through the reply button on the invitation page. A chat message reading probably, if the weather holds is human and lovely, and is not a tracked answer. Hosts simply point those guests back to the link.
The list shows who answered; everyone else is the gap. Reminders inside the app are aimed at exactly those names, which beats mentally cross-checking threads, and it is the reason the deadline on the page earns its place.
It does not, because one event carries one shareable link. Different chats, same page, same list, regardless of where the guest happened to open it.
The deadline gives later a boundary. On the strength of it, decide whether to hold a seat, and record what you chose so the list tells the truth about where everyone stands.
Get Started
Keep one list, give answers one destination, and read the gap early. Start free and set that up as part of the invitation itself.
