One flow: invite, then reply
The invitation and the reply should not be two separate errands. An event invitation with RSVP lets guests answer on the page they opened, printed cards carry the live link, and a password gate can sit before the reply.
You print the cards, hand them out, and then what? The reply comes back by text, by a mutual friend, by a knock on the door three days before. The invitation did its job beautifully and then abandoned you at the hardest part, which is knowing who is actually coming.
An event invitation with RSVP attached closes that loop. Saying yes happens on the same page as reading the details, so the moment a guest decides is the moment their answer reaches your list. The invitation is not finished when it is sent; it is finished when the last reply arrives.
The same live page reaches guests through more than one door.
Small prompts that connect the invitation to the answer on the same page.
Scan to see the details and let us know if you can make it, by the 20th.
You've been invited to something we're keeping under wraps for now. Open the link for the day, and tell us only us whether you're coming.
We're keeping this one between us. Enter the code we shared, and you'll find the details and a button to reply.
Because the reply rides on the invitation, your rules travel with it too. Plus-one limits are honoured when guests answer on the page, meal choices and allergy notes are gathered in the same motion, and every confirmation is tracked to a name on your list rather than a loose message you have to interpret.
For guests it reads as one thing: an invitation you respond to. For you it is one flow from the card in someone's hand to the count on your screen, with nothing lost between the two. That is the quiet argument for keeping the invite and the reply in the same place.
How it works
Create the page in the web app or with Jitabi, then turn the yes button on so the reply is part of the invitation rather than an afterthought.
Choose the plus-one rules and meal fields, and set a password if the event is a surprise or should stay private to invited guests.
Turn the live page into a QR or short link you can print on paper cards, so the physical invite opens the same reply system.
Confirmations arrive against names, companions and meals included, so the invitation and the count finish together at your deadline.
Questions
Yes. Every event gets a live link you can print as a QR or a short web address on the card. A guest who prefers paper scans it and replies on the same invitation page everyone else uses.
Hold the invitation until you are ready to send it, and add a password so only guests you give the code to can open the page and reply. Unpublished drafts stay hidden from guests until you publish them.
On the invitation itself. They read the details and tap yes on the same page, which is why so many answers arrive straight away. There is no separate form to find, and each reply lands against their name on your list.
You set the limit and the reply honours it, even on the invitation. Guests add the companions you allow, named against their reply, so the extra seats are accounted for without a follow-up question.
No. A password is a gate you set for the page; guests who have the code reach the details and reply without signing up or creating anything. There are no individual guest logins to manage.
Get Started
One flow that carries the details and the answer, on paper or on a screen. Send the invitation and gather the replies in the same motion, tracked to your list.
