For the invitation you are sending this week
The message opens a page, and the page asks the question. Date, venue, menu and the yes all live in one place, tracked the moment a guest taps, before you have even closed the chat window.
Type the invitation yourself and it does its best: Saturday, seven o'clock, the garden behind the house, wear something light. But a paragraph of text is a full stop as an invitation. It cannot answer the questions that follow it, and it cannot record who is coming. Everything after that paragraph becomes messages you field one at a time, and a headcount you assemble by archaeology.
An invitation with RSVP built in splits the job in two. The message carries a line and a link. Everything else moves onto the page the link opens, including the question that matters: are you coming.
One warm line plus a single shareable address. It fits into a chat the way any other message does, because the weight has moved off it.
Date, venue with directions, schedule, dress code, an FAQ section, even the gallery once there are photos. This is the part a text block can never be: a place guests return to instead of asking you again.
Yes or no, plus-one inside your limit, meal choice with allergies if you offer them. The tap writes a row onto the live guest list, which is the difference between an invitation and an invitation with RSVP.
Take a birthday lunch as it actually goes: Marta is turning forty, and the group chat produces questions within nine minutes of any text invitation:
Answers need a deadline, and the page shows one, in the guests' view rather than in a message that gets quoted and misremembered. Until you publish, the draft is invisible to everyone, so the invitation you perfect on Tuesday does not leak on Monday. If the gathering is private, a password guards the page and you hand it only to invited guests.
Then the message goes out. One line, one link, into the chats you were messaging anyway. The chat keeps being a chat, jokes and all, while date, venue, menu and every yes land quietly on one list that has no sense of humour at all, which is exactly what you want from it.
How it works
Message Jitabi on WhatsApp as if texting a friend: a birthday lunch, Saturday, the garden, around thirty people. It drafts the invitation page for you to shape.
Tune the schedule, directions, dress code and FAQ sections, and set the reply question with your plus-one limit and any meal choices.
Nothing guests can see exists until you publish. Then the single *.myjoyfullday.site address goes into the group chat with whatever opening line you would have typed anyway.
Every tap lands on the live guest list with meals and allergies attached, so the invitation answers itself while you stay in the conversation.
Questions
No, and that is deliberate. An unpublished event is a draft: guests cannot open it even if they somehow get the address. Publish when the invitation is ready, and the link becomes live at that exact moment.
Yes. You set how many companions each reply may carry, and the guest list counts the full party against your limit, so the headcount includes the plus-one before anyone thinks to ask.
Keep the address off the group and put the substance on a password-protected page. Guests who were invited get the password; the chat gets one line, which is all it needs.
Only as complicated as you make them. Offer two or three choices, or none at all, and guests who need to say something can write an allergy note with their reply.
A single yes or no tap is gentler than composing a message in an app they use reluctantly. And if a guest prefers to telephone you with their answer, the list still needs the tap, so you can do that small favour on their behalf later.
Get Started
Start free, build one page that holds the details and the reply, and let the WhatsApp message be the short thing it was always supposed to be.
