One reply flow. Fewer loose ends.
Guests reply from their invitation, confirm who is attending and choose only the menu options relevant to them.
The couple approves the invitation groups, menu labels and deadline before release. Private access links are never included in public analytics.
Ask only what the guest needs to answer.
Attendance, names, menu selections and dietary information are collected in a short ordered journey.
- Private invitation access
- Guest-limit checks
- Menu availability checks
- Confirmation and organiser notification
The quality of the data begins before the form opens.
Lewis imports and checks the approved invitation structure with you. The couple remains responsible for final names, meal options and dietary follow-up.
Practical questions.
Can a guest change their reply?
The agreed wedding process determines how changes are handled. Guests can contact the organiser when a correction is needed.
Are dietary notes public?
No. They belong to the private wedding workflow and are not part of public analytics.
Does the Irish pilot translate private guest pages?
Not yet. Private-wedding multilingual support is a separate future product phase.
Talk through the reply structure before building it.
Share the date, approximate guest count and menu shape. Lewis will explain the practical fit.
Check your date