For the page guests actually fill
A guest RSVP page fails when it asks for too much and succeeds when it asks for exactly enough. The fields you choose and the words beside them decide whether people answer honestly, quickly, or not at all.
Think about the last form you abandoned. It probably asked something you did not know, or something you saw no reason to give. A reply page is no different. Every field you add is a small chance the guest pauses, gets busy, and never comes back. A guest RSVP page should read like a kind question, not a registration.
The design goal is honesty at low effort. You want guests to tell you the truth about whether they are coming, who is with them, and what they can eat, in a way that takes seconds and never makes declining feel rude. The fields and the wording are how you get there.
Keep the essentials, make the rest optional, and tie everything back to a name.
Small wording choices do most of the work. Borrow and adapt these.
Will you be joining us? I'll be there, Sadly I can't make it, Let me reply closer to the day.
You may bring one guest. Add their name below so we can set the table right.
No need to apologise. We'll miss you, and we've saved a photo from the day for you to see after.
Anything the kitchen should know? Fill this in only if it applies, otherwise skip it and you're done.
A reply page should look and sound like the invitation it belongs to. If the card is warm, the form should not be clinical. If the invitation used the family name, the reply should recognise it. Guests answer more readily when the whole thing feels like one continuous note rather than a detour into software.
The other half of good design is where the answers go. Every reply on the page should land as a tick against the guest's name on your list, companions attached to them, meal counts adding themselves up. A field that collects nothing useful is a field you should remove, and a field that feeds the list cleanly earns its place.
How it works
Build or draft the page so the reply sits under the same heading, tone, and details guests just read. Continuity is what gets answers.
Keep attendance, companions inside your limit, meal, and an optional note. Anything you would not act on is friction that costs replies.
Phrase the no so it is easy and kind to give. Honest declines early are worth more than hopeful yeses that never show up.
Before you send, confirm each answer lands against a name and totals correctly. The reply page and the list are one system.
Questions
Attendance, the number of companions within your limit, a meal choice if you serve one, and an allergy note where relevant. Add an optional free-text line for anything a tap cannot capture. Resist fields you would never act on.
Make no a clear, one-tap option and phrase it kindly so declining is not awkward. A guest who feels welcome to say no early gives you a truer count than one who dodges the question until the deadline.
Usually not. Guests reply against their name on the list you built, so they need not re-enter an address or phone number. Fewer fields means more replies, and the important answers still attach to the right person.
It should, because that is what gets it filled. The page uses the same design and tone as the invitation, so guests read the details and answer on the same screen without noticing a handoff.
Get Started
A short, kindly worded reply page earns faster and more honest answers than a long form ever will. Design the guest's question and the count takes care of itself.
