For hosts who need a number, not a guess
The page invites, the RSVP decides. Guests confirm, name plus-ones inside your limits, add meal notes, and you watch the real headcount form instead of estimating from read receipts.
A read receipt is not a headcount. You can see that people opened the invitation and still have no idea whether they intend to come, whether they are bringing someone, or whether one of them needs the fish. The number you can actually plan around only appears when guests give a structured answer, and that is what an RSVP attached to the invitation does.
An invitation website with RSVP turns the polite gesture of confirming into real planning information. The page does the inviting; the reply does the deciding, and it decides in a form you can act on.
Confirming should take seconds, not a composed message. A guest taps yes and the answer is on your list against their name before they think about writing a note.
Where a guest may bring someone, they name that person in the reply, and only up to the number you allowed. The companions land on your count instead of appearing at the door.
Alongside the yes, a guest records a preference or an allergy. That single field is the difference between a rough headcount and a number the kitchen can cook against.
The point of an accurate count is not the count itself; it is the decisions it lets you make early.
The live list is the quiet reward. As replies come in over the days after you send, the total forms in front of you, so by the time a vendor asks you for final numbers you are reading them off a screen instead of tallying messages at midnight. The headcount stops being an estimate carried forward from a read-receipt count and becomes something you watched take shape.
How it works
Create the page through the app or Jitabi and switch the RSVP on from the start, so the yes button is part of the invitation rather than a separate task.
Set how many companions a guest may name, and ask for a meal note, so every reply carries the specifics you will act on.
Send the invitation and track the live total as confirmations attach to names, day by day.
Give the caterer a real headcount and per-dish breakdown, and set your tables against actual attendance instead of a guess.
Questions
A text tells you someone intends to come; it does not tell you reliably how many, or with which meal needs. An RSVP collects the confirmation, the plus-ones within your limit and the meal note as one record against their name, which is what a caterer or seating plan actually needs. A yes in a message you have to tally by hand.
You set the limit when you build the invitation, and the reply honours it. A guest names a companion only up to the number you allowed, and that person is added to your count. This applies the same rule to everyone and keeps extra heads known in advance rather than discovered at the door.
Yes. Alongside confirming, a guest can record a meal preference or an allergy in their reply. That turns a single headcount into a per-dish one, so weeks before the day you can give the kitchen an exact number for each option, including the guest who cannot eat most of them.
The list builds live as replies arrive, so you are never waiting on one final tally at the last minute. The guests who have not answered are simply the names still unchecked, and a reminder goes to exactly those people, so the count firms up while there is still time to plan against it.
Get Started
Let guests confirm in two taps, name plus-ones within your limits and leave a meal note, so the caterer and the tables are settled on facts. Start free.
