An RSVP form collects free responses to your event instead of selling tickets. You add it to the public event page, and each accepted response creates check-in tickets automatically. RSVP forms are intentionally basic; to collect per-guest data or restrict responses to a known list, use Invites or a CSV import instead (see below).
Requirements: An event. Each collected RSVP draws one credit from your balance.
Add the RSVP form to your event page
-
Open your event and go to Event Page.
-
Add an RSVP Form section. Select an existing form, or type a name and click Add to create one. For the full event-page builder, see Event page and settings.
- Open the RSVP form to set its options:
- Allow decline — lets guests respond no. When off, every response is treated as an acceptance.
- Include email — collects the guest’s email and makes it required.
- Include quantity — shows a guest-count field so one person can RSVP for several. When off, each response counts as one guest.
- Include list — shows a list selector so guests can pick a sub-list.
- Save the event page.
The RSVP form is now live on the public event page. Open the page from your event to view it, then share the link with your guests.
How RSVPs work
When a guest accepts, a check-in ticket is created for each guest in the response — an RSVP for 3 people creates 3 tickets. Those tickets are what you scan at the door. A declined response creates no tickets. If the form collects email, the guest is sent a confirmation.
Responses appear in the RSVPs section of the event, and the tickets they create appear alongside your other attendees.
What RSVP forms can’t do
RSVP forms are deliberately minimal:
- No custom questions — you can’t collect t-shirt sizes, dietary needs, or other per-guest fields on the form itself.
- No per-guest detail on group RSVPs — one person can RSVP for several guests when the quantity field is on, but each extra guest becomes a bare ticket with no separate details.
- No response cap — you can’t limit the form to a fixed number of RSVPs.
- One shared link — every guest uses the same public form URL; there are no per-guest unique links.
- One event per form — an RSVP form collects for a single event; multi-session or multi-location RSVPs aren’t supported.
RSVP form vs. Invites
If you need per-guest data or a controlled guest list, use Invites instead of an RSVP form:
| RSVP form | Invites | |
|---|---|---|
| Custom fields | No | Yes |
| Response limits | No | Yes |
| Per-guest unique links | No | Yes |
| Pre-loaded guest list required | No | Yes |
Related articles
- Event page and settings — add and arrange sections, including the RSVP form.
- Emailing attendees: resends, campaigns, and delivery issues — send accept/decline invitation emails to a guest list.
- Import spreadsheets — bring an existing guest list in for check-in.
FAQ
Should I use an RSVP form or a free $0 ticket?
Use an RSVP form for simple open responses where you only need names and a guest count. Sell a registration type priced at $0 instead when you need the full checkout flow — for example to collect more attendee data or hand out tickets that look like a paid order.
My guests can’t see the RSVP page — why?
The event page only loads when the event is published. An unpublished event returns a 404. Publish the event, then reshare the link.
Can I collect t-shirt sizes or other details on the RSVP form?
No. RSVP forms don’t support custom questions. Use Invites, or an outside tool whose final list you then import for check-in.
