Skip to main content

RSVP per Event / Multiple RSVP Forms

RSVP

Create separate RSVP forms for different events (e.g., ceremony and dinner) with individual questions – automatically linked via locations and events

Where do I find this?
Content > Sections + Planning > Events + Guests & RSVP > Questions

Step by Step

  1. 11. Create locations: Under 'Content', create a Locations section and add your locations (e.g., 'Church', 'Restaurant'). Enable 'Show in RSVP' for each relevant location.
  2. 22. Create events: Go to 'Planning' > 'Events' and create events (e.g., 'Ceremony', 'Dinner'). Assign each event to the matching location via the 'Location' dropdown.
  3. 33. Create RSVP sections: Under 'Content', create multiple RSVP sections (e.g., one for the ceremony, one for the dinner). Assign each RSVP section to the matching event.
  4. 44. Assign questions: Go to 'Guests & RSVP' > 'RSVP Overview' > Questions. When creating a question: Under 'Applies to', choose which RSVP form the question should appear in.
  5. 5No selection under 'Applies to' = the question appears in all RSVP forms
  6. 6Guests see only the relevant questions per RSVP section on the public page
  7. 7On the token-based RSVP page, questions are shown dynamically based on the chain: Location β†’ Event β†’ RSVP Section β†’ Questions

Tips

  • Ideal for weddings with multiple parts: civil ceremony, church service, dinner, party
  • Typical use case: Menu choice only for the dinner RSVP, not the ceremony
  • The section assignment ('Applies to') only appears when 2 or more RSVP sections exist
  • Global questions (without assignment) are shown in all RSVP forms – ideal for general questions like allergies
  • In the question overview, badges show which form a question is assigned to
  • The complete mapping chain is: Location (Content) β†’ Event (Planning) β†’ RSVP Section (Content) β†’ Questions (RSVP Overview)
  • For the public page, question assignment to RSVP sections is sufficient. The Locationβ†’Event link is especially important for token-based invitations.