For hosts who live in the inbox
An email that asks people to write back starts a chain you have to read through. Send it as a link instead: guests open the invitation, confirm from their phone, and the list fills itself while you leave it alone.
The friendly email becomes a thread. Someone replies, their partner is a question mark, a cousin forwards it and adds a friend, a colleague answers from an old address, and a week later you are scrolling a chain to work out a headcount. The invitation was easy; managing the answers is the part nobody plans for.
A party invitation email that leads to a page avoids the scroll. The email itself stays short, one warm line and a link, because all the detail and the reply now live on the page it opens. A guest reads the plan and taps to confirm, and that confirmation lands against their name on your list instead of replying-all into the thread.
The email invites; the page does the remembering so you do not have to.
Venue, map, timings, and dress note sit on the page. If anything moves, you change it there and the next guest to open the email's link reads the corrected version.
Two taps say yes, name a companion within your limit, and choose a meal. The answer is a line on your list, not a paragraph you have to summarise.
Guests who never opened or answered can be sent a gentle nudge from inside the list, so the deadline is not a final hopeful email to everyone again.
The email has one job now: get the guest to the page. Everything else moves onto the invitation.
You may want to know who opened the email before they answered. This is not that kind of tool, and we will not pretend otherwise: what you get is the reply list, which shows who has confirmed and who has not. That is the number that actually decides the evening, and it updates the second a guest taps, so the chasing has somewhere honest to stop.
How it works
Set the date, the venue, and the plan for the evening, in the web studio or through a line to Jitabi. The page and its reply form are created together.
Enable confirmations with the plus-one limit and any meal options, so a guest's answer is recorded against their name rather than written into the thread.
Write one warm line, point to the page, and let the invitation hold the detail. The link is the same for every guest you send it to.
Replies arrive in real time. From the list, send reminders to those still outstanding and arrive at the deadline with a settled number.
Questions
No. They tap the link, read the page, and reply in a couple of taps on their phone. There is no sign-up, which is why email guests who ignore reply-all still manage to answer.
You can, but the better pattern is to keep the email short and put the detail on the page. That way a change later needs only one edit, and everyone reads the same current version.
Yes. A no is recorded on the list the same way a yes is, so your outstanding count is accurate rather than everyone who has not replied looking like they might still come.
Add their answer to the list yourself. The list is the single record, so a written reply and a tapped reply both end up on the same names.
You can send reminders to guests who have not confirmed from inside the list, through their usual channel. You will not see open counts, but you always know who still owes an answer.
Get Started
Send a short, personal email that opens a page, and let two-tap confirmations build the count while you stay out of the inbox.
