For the group chat that never sleeps
You post the invitation, ten messages bury it, and three people reply days late. One link keeps the invite above the noise, because the replies happen on the page rather than in the chat.
A group chat is a river. Anything you put into it floats for about four minutes. The birthday invitation goes out at noon, the voice notes start at twelve-oh-two, and by Friday the message with the date, the address and the question is somewhere under four hundred memes and a debate about someone's hedge.
People genuinely meant to reply. That is the part hosts forget: in a loud group, silence is usually scroll depth, not refusal. The guest who meant to answer lost the message, and finding it again is more work than the answer deserved.
A buried message is gone; a link can be asked for again in two seconds, and whoever opens it on Sunday sees the same complete invitation the first reader saw.
Answers are tapped on the page and recorded on the guest list, so the group keeps joking undisturbed and the headcount grows somewhere the noise cannot reach.
A reply deadline shown on the page tells everyone when the headcount locks, and the number you hand the caterer afterwards is read off a list rather than estimated from vibes.
Groups are forwarding machines, and for an invitation that is mostly a feature. Someone sends the link to their partner, who sends it to the cousin who always comes. Because all of it is the same single address, every answer from every branch of the forward tree lands on one list, each plus-one counted inside the limit you set rather than smuggled in on a Tuesday voice note.
If the gathering deserves privacy, the page can carry a password and the group alone gets it. When the deadline passes and blanks remain, the app lets you send a reminder to exactly those names on WhatsApp, which is one polite message rather than a personal campaign across three chats.
How it works
Text Jitabi the plan, a birthday party, Friday the ninth, Tom's place, and let it draft the page; check the schedule and directions sections before you publish.
Paste it as a single message while the chat is quiet, and resist writing the details into the text; that is what the page is for.
React away, joke away. Answers are happening on the page, so the headcount climbs while the conversation does whatever conversations do.
When someone asks what the plan was, reply with the link. Near the deadline, send one WhatsApp reminder to the names still blank on the list.
Questions
Then you have a cheerful group and no list, because the guest list records replies made on the page. That is why hosts in loud chats make the button part of the bit, posting the link and saying the only yes that counts is the tapped one.
A password on the page stops the copy without a copy-paste conversation. Otherwise, plus-one limits cap how far a reply can grow, and the deadline gives you a natural date to stop adding seats.
No. Membership is proximity, not intention, which is why the tracked list is the thing to count from. A group of sixty with a reply page usually produces a party of thirty-two, and the thirty-two is real.
Carefully, yes. Put the details on a password-protected page so the surprise survives the inevitable leak, take replies on the same page, and remind only the blank names so nobody gets chased twice.
Post once properly and re-share on request. A second blast of the same link reads as pressure; a deadline on the page plus a reminder to non-responders reads as organisation, and reaches only the people who need it.
Get Started
Start free, put the invitation on a page the group can always find again, and count from the list the replies build.
