Guest experience
Understand what guests see when they open the public RSVP flow.
Overview
Guests use the public RSVP page from your published wedding site.
Key concepts
With Invitation list, the experience starts with guest search and requires a matching party. Flexible access also starts with search, but a visitor who is not found can register a new party. Open RSVP starts directly with party details and never asks the visitor to find an invitation.
How it works
When lookup is enabled, guests search by name and Cordially builds the RSVP context for the selected party, including invited guests, invited events, prior responses, dietary notes, accessibility notes, and custom answers. Open RSVP uses the same registration and response flow without the lookup step.
After review, guests submit responses. Cordially validates that every response belongs to the resolved published site and invited events. New Open RSVP parties are created only after names, configured contact fields, events, and answers pass the complete server-side review.
Visible host-created named +1s can always find the linked party using their own exact name. They appear as fixed named guests and cannot be renamed or removed from the public form.
Names previously entered for transferable open +1 slots can also find the linked party when Let guests find an RSVP using the name entered for an open +1 is enabled in RSVP settings. This setting is off by default and does not turn that occupant into a fixed invitation.
Notes and limitations
Guests do not sign into Cordially. Treat the public RSVP link as public and share it only with people who should access the form.
Invitation list does not create a new party when search has no match. Flexible access offers registration after an unsuccessful search. Open RSVP begins at registration. Self-registered parties in either mode only receive active events configured for public RSVP.
Invitation email recipients reach the same published site. Sites do not currently issue recipient-specific RSVP access links.