For the final message, ready to send
The facts decide whether guests can come; the sentence around the link decides whether they bother to reply. Placement rules, sample pairings, and the small rewrites that turn a link into an answer.
Replying is work. Typing a whole sentence into a group chat is real work: it needs the right words, and it puts the answer in public. Tapping a button on a page and picking yes or no is not work. The link is only an upgrade when the message frames it that way, as the easy path, not the official one.
So the sentence before the link matters more than most hosts expect. Compare the two versions below, same event, same facts, wildly different tap rates. The ask should read like the smallest possible favour, because it genuinely is one.
Five rules, and they apply in every chat app.
The line does the leading; the link does the landing.
Sunday lunch, eleven, at our place on Trädgårdsgatan. The whole plan, and one button to say yes or no, live here: [link]. By Friday, so the roast is the right size.
Ines turns thirty on the 13th, from six, doors before half past seven because she is terrible at surprises. Confirm you can keep it here: [link]. The deadline is the 6th.
Marta and Tom, Saturday 3 October, Lindqvist House. The day, the travel, and a reply button on one page: [link]. Answers by 12 August keep the caterer honest.
Tomorrow, seven, pasta and loud music at Henrik's. Ten seconds here tells us whether to cook for you: [link]. By noon, no guilt either way.
Rephrased: tell us by Friday here, either answer is genuinely fine. The first has no deadline and asks for a composed sentence; the second has a date, a button, and permission.
Rephrased: the reply button is on the page, deadline the 25th. RSVP is vocabulary from another decade, and the guest should not have to hunt for the action.
Rephrased: the facts are on the page, the ask is one tap. If the message must be read carefully, the structure is wrong. Put the decision in the chat and the detail on the page.
After the tap, the guest sees the page and answers there: a reply button, plus-ones inside whatever limits you set, meal choices or a note if you asked for them. The answer lands in your guest list the moment it is given, so the list grows while you are pretending not to watch it.
This is also why the same link keeps working after the details change. Edit the page, and the next tap sees the new version. Nothing is re-sent, no one is confused, and the worry list shrinks to exactly the names still quiet when the deadline passes. Those get a reminder, sent from the list, and honestly that is the whole job of the mechanism.
How it works
The reply button, deadline and details must exist before the message can point at them. If you want help phrasing the page itself, the in-app AI drafting handles the sections.
Facts first, then one sentence that names the action. Tap, say if you can come, ten seconds.
Give the link a second to render in the chat before sending, and check it on a phone yourself. One tap test beats a hundred intentions.
Answers arrive as they are given. Past the deadline, the non-responders are visible on the list, and a reminder goes out without you writing the awkward second message.
Questions
They open the link and answer on the page: reply button, plus-one choices if you allowed them, a note field if you asked for one. Nothing needs building, and nobody has to search chat history to find what they promised.
After. The guest needs what, when, where before being asked to act, and the link placed right after the ask reads as the natural next step. A link that arrives before the date is a mystery, not a convenience.
It still taps through, so send it anyway, but check once on your own phone before blasting the list. Sending the link on its own line, with a moment before the rest of the text, gives the preview room to render.
Every event gets a live link on a myjoyfullday subdomain plus a shorter path URL; use either in the message. There are no custom domains, and the honest answer is that guests do not read URLs, they read the sentence before them.
Print the page address or a QR code on a card, and take their reply by phone yourself. The list has room for answers entered without a tap, and the page still does what the phone cannot: count everyone in one place.
The page shows the date beside the reply button, so the deadline always exists somewhere. The message should still carry it; a date in the chat becomes a decision now, while a date on the page waits for a tap.
Get Started
Start free, publish the page, then write the sentence that makes the tap the easiest thing your guest does all day.
