For hosts counting heads by scrolling
Forwarded invites scatter answers across group chats, private messages and voice notes. One list gathers every yes, no and plus-one in a single place, with names attached and a total you can read at a glance.
It always arrives at the same time. The venue wants a number, or the caterer wants meal counts, and you open WhatsApp and begin the scroll. Marta said yes in March. Tom replied with a thumbs-up and never followed it. Someone's cousin forwarded the invitation to a third chat, and his answer landed somewhere you cannot find on a good day.
By the end of the scroll you have a number, but you do not trust it. That is the real problem with scattered replies: not that counting is tedious, but that no total you build from chat history can be verified. The list below is how hosts replace that ritual.
The trick is that replies never pass through a chat. Your invitation goes out on WhatsApp as a single link, and the answer is given on the page that link opens. From there it goes straight onto one guest list, no matter whose group, whose private thread, or whose forwarded copy carried the message.
One link means one list. If Anna forwards the invitation to her partner's family chat, their answers join the same rows rather than starting a parallel headcount you have to reconcile later. Nothing reads your message history and no bot sits in your groups; the chat stays exactly as private and noisy as it was, because the tracking happens on your page instead.
Each reply arrives attached to a guest, with plus-ones counted inside the limit you set, so the total row and the total page agree.
Choices and dietary notes are written into the entry at reply time, which is the only moment anyone reliably remembers them.
On the day, a QR check-in at the door marks arrivals against the same list, so attending is tracked as neatly as replying.
With the list current, the counting moment shrinks to opening one page. The deadline shown on the invitation gives the silent names a shape, and reminders to exactly those guests are one action in the app rather than a campaign of individually typed messages. You still know Marta is coming, of course. The difference is that now you can prove it, in a list, with a number the venue can act on.
How it works
Build the event in the web app and publish it, so every chat you send to shares the same address and the same list behind it.
The family group, the work friends, the quiet private messages. However the invitation travels, replies return to a single guest list.
Each tap adds a name, a party, a meal choice. The list updates as replies land, so it is current whenever you open it.
When the venue asks, you read totals off the live list instead of defending a scroll. Collaborators watching the same event see the same truth.
Questions
No, and it would be an uncomfortable magic if it did. Nothing scans or reads your message history. Scattered chats stay chats; the list fills only from replies guests tap on your invitation page, which is what makes the total trustworthy.
It is not. Send the page link now as the details you never got round to typing, and answers begin landing as rows from that point on. Guests who already answered in chat can simply tap once more on the page to join the count.
No. Every event lives at one shareable address, so every reply, however many chats the link bounced through, arrives on the same list against the same guest.
Yes. You can add collaborators to the event with access levels, so the two of you watch one list rather than comparing notes, and the same applies to a family member helping run the day.
They stay visibly silent, which is the point. The list shows who answered, so the missing names are a group you can act on with a reminder before your deadline, rather than a rumour you worry over.
Get Started
Start free and turn one WhatsApp invitation into one guest list, so the next headcount is read rather than remembered.
