One link, every reply accounted for
Details, directions and the reply button all live behind one address. Paste it anywhere and let it travel the forwards — the guest list keeps its own account of who actually said yes.
A paragraph of text is an invitation until someone asks where to park. A picture of a design is an invitation until the time changes. A link is different: it is the front door to a page that holds every answer, and one copy of it works as well as a thousand.
On My Joyfullday, a published event lives at its own address on a myjoyfullday.site subdomain. That string of text is the whole invitation. It pastes into a group chat, a private message, an email, or a QR on a printed card for the neighbours who do not ask.
Three sends covering the three ways links actually circulate.
Everything about Marta's garden party — timings, where to leave the car, what to bring — is on this page, and the reply button is at the bottom: marta-garden.myjoyfullday.site. Reply there so I can count everyone once.
Of course — send them the same link. They reply on the page and it lands on my list with the plus-one counted.
This one is password-only. The page link and the password are in your message; please don't post either in the wide group.
Say exactly what tracks and what does not, because this is where invitation links are usually over-promised. The guest list records replies: each name that arrives through the reply button, plus-ones within your cap, the meals noted on supported events. It does not record readers, and it does not reconstruct the chain of who forwarded to whom. That is not a gap in the tool so much as a line it respects — the page is for guests, and counting is done by answers rather than surveillance. The practical upside is that forwarded links still work for you: a friend of a friend who replies is a head you can see coming, and the password is there for when you would rather that door stayed shut.
How it works
Message Jitabi, edit by reply, publish. The page comes with one myjoyfullday.site link — that is the entire distribution system.
The group chat, the private thread, an email to the travelling cousin, a QR printed for the paper card. All roads are the same road.
The guest list keeps the count: who said yes, who said no, how many came attached to a name.
When replies slow, reminders go to non-responders from the app, over WhatsApp or email. The link stays fixed; only the chasing moves.
Questions
Anyone holding the link can open the page, so for a closed guest list put a password on it and send that to the invited names. The link alone then gets you to a locked door, not to the reply button.
No. The address is fixed to the event and the content behind it moves. Reply to Jitabi with a change and the same link serves the current version to everyone who opens it next.
Not a chain of readers — the list records replies, not openings. What you can see is every answer that arrived, including guests who found the link through someone else; decide separately whether to let the page be password-only.
Yes. The address carries a QR version for cards and posters, so the neighbour who never asks still comes through the same door as everyone in the group chat.
Each published event has its own address, which is exactly what stops two parties' replies merging into one confused list. Build the next page, take the next link.
Nothing to install and nothing to sign up for mid-scroll: they open the page in the browser their WhatsApp uses and reply there. That low friction is why reply counts beat group-chat tallies.
Get Started
The link carries the details, the directions and the reply button. Send it once or a hundred times — the list keeps its own account of who is coming.
