A clear yes or no
Guests confirm whether their invitation group can attend. A decline can notify the organiser without asking the guest to complete irrelevant menu fields.
Attendance, names, food choices and dietary notes can arrive as one useful guest record.
Guests open a private link in their usual browser, without creating an account or downloading an app. Each invitation can cover the people replying together, including the adult or child menu intended for each person.
The reply flow is working with fictional details in the public demo. Its full live-service rehearsal still has to be completed.
A couple should not have to work out which meal belongs to which name after the reply arrives. The form asks for the detail at the point when the guest already has it in front of them.
Guests confirm whether their invitation group can attend. A decline can notify the organiser without asking the guest to complete irrelevant menu fields.
The reply records each person in the group, rather than leaving a single contact name to stand in for everyone attending.
Adult and child choices can be kept separate. Each required course is selected against the guest who will receive it.
Allergies, intolerances and other requirements share one note beside the relevant guest. The couple reviews that wording before the agreed venue handover rather than treating the form as medical screening.
The service is managed around the working product. Lewis prepares the journey with the approved wording and menus, then rehearses it before any live invitation is shared.
Invitation groups, guest wording, courses and available dishes are checked before the reply links are sent.
They answer for the people on their invitation, then review the names, meals and dietary notes before submitting.
The product saves the reply with its confirmation record so an email issue does not require the guest to enter everything again.
Attendance, table assignment, course choices and dietary notes can be combined in the agreed CSV export when the plan is ready.
Wedding replies can include information that needs care. The public marketing pages cannot access wedding records, and the guest route only opens with its private invitation code.
Guest information is used to provide the booked wedding service. It is not sold or used to market Yours, Dearest to the guest.
Read the working privacy noticeThe wedding receives a deletion schedule. The current working default is 90 days after the event, with an agreed export first where that is part of the scope.
Share the date, venue and the parts of the guest journey that are becoming awkward. Lewis will reply personally and confirm whether a founding setup is a sensible fit.