Put an RSVP button on the event page, choose guest or signed-in registration on the event type, and review confirmation email and analytics for RSVP-only events.
The RSVP flow is the registration experience on RSVP-only events. Attendees register from a multi-state RSVP button on the event page — as a signed-in member or, when you allow it, as a guest with name and email only. This article is for HQ admins who set the event type, default event page, and confirmation email. Attendees follow Register or RSVP for an event.
- RSVP flow — rewritten registration path for event types that accept RSVP (not paid tickets or external ticketing).
- Guest registration — optional event-type setting so visitors can RSVP without signing in.
- RSVP button — Page Builder button with Action set to RSVP, or the RSVP and Join buttons layout.
Note: The RSVP flow applies when the event type uses Bevy Ticketing → RSVP. It does not replace paid checkout. Use Allow registration as a guest on the event type only if you want visitors to RSVP without signing in.
Prerequisites
- Confirm the event uses an event type with Bevy Ticketing → RSVP. See Configure event ticketing.
- On that event type, decide whether to enable Allow registration as a guest (label may mention in-person events on older setups).
- Add RSVP types on the event Details tab (title, quantity, availability, waitlist as needed).
- Use the event page builder — not the legacy ticket widget alone — so visitors get the multi-state RSVP button.
Important: Changing guest registration or moving an event type between paid tickets and RSVP affects live events that use that type. Coordinate with your Customer Success Manager before changing production event types. Full event-type steps: Configure event types.
Guest vs signed-in registration
Signed-in visitors can always complete the RSVP flow on RSVP-only events. Guest registration only unlocks the anonymous name-and-email path. It does not turn off login, and it does not make paid ticket purchase work without an account.
| Visitor | What they do | What Bevy creates |
|---|---|---|
| Signed in | Select RSVP (or one-click RSVP when available) and complete the flow | Registration on their existing account |
| Guest (not signed in) | Enter name and email in the RSVP form — only when the event type allows guest registration | A Prospective User for a new email, or links an existing user for that email. They use the confirmation email to return to the event. |
| Guest registration off | See Log in to RSVP and must sign in or create an account | Registration on the signed-in account after login |
Guest RSVPs do not join the chapter. Optional newsletter opt-in during registration still follows your community’s usual rules — see the attendee article for what registrants see.
Add the RSVP button on the event page
Default event banners often already include registration buttons. Add or fix the button when a page still uses a legacy tickets block, or when you want RSVP controls in another place on the page.
- In the Admin Dashboard, open the default event page template in Page Builder so new events inherit the RSVP button. To fix one event only, open that event’s Page Builder. See About the event page builder.
- If a legacy tickets widget is still on the canvas, select it and delete it.
- Add registration controls in one of these ways:
- Add the RSVP and Join buttons layout from the layout list (event pages only).
- Or drag a Button onto the canvas, select it, open Action, and choose RSVP.
- With the button selected, open each RSVP state (sometimes labeled under a group such as Handle all possible ticketing states). Check copy and styling for every state you care about.
- Select Save.
Tip: Place the RSVP control where visitors expect to register — usually near the event title or after a short description. Event banners already include these buttons; use the standalone layout when you need a second RSVP row lower on the page. Layout details: About event page layouts.
RSVP button states
One button changes label and behavior based on the visitor and the event. Edit each state in Page Builder; communities can also override some strings in Style settings.
| Editor state | Default public label | When visitors see it |
|---|---|---|
| View RSVP options | RSVP | Registration is open; opens the RSVP options. |
| One click to RSVP | RSVP | Signed-in visitor can complete a one-click RSVP (single ticket, no survey). |
| One click to RSVP and join | RSVP and join | Same as one-click RSVP, and the visitor can join a live virtual event. |
| Your RSVP | Your RSVP | Already registered. |
| Log in to RSVP | Log in to RSVP | Guest registration is off and the visitor is not signed in. |
| Join waitlist | Join waitlist | Sold out with waitlist enabled. |
| You are on the waitlist | On waitlist | Visitor is already on the waitlist. |
| Sold out | Sold out | No spots left and no waitlist. |
| Join virtual event | Join | Already registered and the virtual event is joinable. |
Paid or external ticketing events use different button actions (for example Get tickets). This article covers the RSVP action only. Set the ticketing mode on the event type in Configure event ticketing; for other Page Builder button actions and layouts, see About the event page builder and About event page layouts.
Ticket confirmation email
When the RSVP flow is active for an order, Ticket Confirmation can include an Un-RSVP line (default English: No longer attending? Please un-rsvp.) that links to cancel that registration. HQ can edit system email templates, so live copy may differ.
Attendees cancel free RSVPs from that link, from the event page, or from My tickets when Un-RSVP is available — see Manage tickets and Un-RSVP. Organizers remove people from the event on the Registrations tab — see Manage event registrations.
Track RSVPs in Google Analytics 4
If your community has a GA4 measurement ID configured, completed RSVPs can appear in GA4 as purchase-style events with an RSVP item variant and a value of zero (not a paid transaction). In GA4:
- Open Google Analytics for your property.
- Go to Reports → Monetization overview (or a custom exploration that includes purchase events).
- Use the purchase journey (or equivalent) to see discovery → interest (RSVP click) → form progress → completed registration.
If there is no completed purchase event, the visitor did not finish RSVP. UTM parameters on the event page URL help attribute the full journey in your own reports..