The RSVP page

The RSVP page is the form that contacts use to respond to your event, choose tickets, and (for ticketed events) pay. It is built in the same Forms canvas used elsewhere in SwiftFox, with extra blocks that are specific to events. You create it from the event's RSVP section — on a narrower window it may sit under the Setup menu (see Events — Overview).

Creating the RSVP page

1. Click Create RSVP Page.
2. In the Create RSVP page dialog, enter a Form name.
3. Optionally open Start from a template (optional) and choose a saved RSVP template to base the page on. Only Event RSVP Template forms appear here — see Form templates.
4. Click Create RSVP page.
5. Drag blocks onto the form and configure each one.

Event-specific blocks

These blocks are unique to RSVP forms:

• Calendar — lets the contact download an .ics calendar file for the event.
• Event Location — displays the location visually.
• RSVP — sets the contact's RSVP value when submitted. This must be the last button on the form because it acts as the submit button. (This block appears in the canvas with the button label you give it, e.g. "Accept".)
• Tickets — lets contacts choose from the available tickets; you can allow a quantity and make the block required.
• Payment Method — required for ticketed events (see below).
• Rich Text — a formatted text block that supports event merge fields (see below).

Tickets block

Select the Tickets block on the canvas to open its settings panel:

• Set available tickets — choose which of the event's tickets appear. Only tickets with Show ticket turned on (see Event tickets) are available in the form.
• Allow user to choose ticket quantity — let contacts choose how many of each ticket they want.
• Required — make choosing a ticket compulsory.
• Collect attendee details for each ticket — add one attendee space per seat bought (see below).
• Contacts that need tickets — how the block counts the people who need a ticket, with Choose which contacts need tickets, Minimum quantity and Maximum quantity.
• Conditional settings — show or hide the block based on earlier answers.

Collecting a name for every seat

By default, someone buying several tickets or a table has to add each guest themselves with Add New Contact. Turning on Collect attendee details for each ticket builds those spaces for them.

1. Select the Tickets block and tick Collect attendee details for each ticket.
2. SwiftFox adds an Add/Update Contacts block straight after the Tickets block, linked to it. You can move it like any other block, and set up its fields as usual. Its settings panel also has a Questions tab, where you switch on any event registration questions you want every attendee to answer (see Event registration questions).
3. Optionally tick Require all attendee details. It is off by default, so a buyer can submit with some seats still unnamed; those seats can be named later from the event's Bookings section (see Audience & bookings).

What the person filling in the form sees:

• Once they choose tickets, the linked block shows the person making the booking first, under an on-screen heading that reads Purchaser, then one numbered space per seat bought — Attendee 1, Attendee 2 and so on. Group tickets count every seat, so two tables of ten give twenty spaces.
• An Attending the event switch, on by default, decides whether the person booking takes one of the seats. Switch it off when someone is buying for others and not coming themselves: they still own the booking, and every seat stays free for guests.
• Each space has a clear (×) button to empty it without giving up the seat. To reduce the number of seats, clear an attendee first.
• The linked block shows and hides with the Tickets block, so it cannot be bypassed.

Things to know:

• Use only the linked contact block for the people booking tickets. If the form has other contact blocks, the Tickets panel warns you about it.
• If you delete the linked block, the Tickets panel shows an error with a Restore block button.
• Unticking Collect attendee details for each ticket asks you to confirm, because it removes the linked contact block and its field settings.
• Forms where this setting is left off work exactly as before.

Payment Method block

For ticketed events, the Payment Method block is required:

• Configure a payment provider, or enable Invoicing.
• If you are using Xero (via the Xero Integration), select Xero in the invoicing Select so invoices generate in Xero.

Merge fields (personalising with event details)

Rich text blocks in an event RSVP form can pull in the event's own details, so you don't have to retype them. This keeps the form specific to the event and updates automatically if the event details change.

To insert a merge field:

1. Drag a Rich Text block onto the form and click into it.
2. Either type the @ symbol, or click the @ Merge fields button on the block's toolbar (top right).
3. Choose a field from the list (you can search).

The available event merge fields are:

• Event Name
• Event Description
• Start Date
• End Date
• Event Timezone
• Event Location Address
• Event Location Type
• Any event custom fields configured on the event.

Merge fields are only available in event RSVP forms, inside rich text blocks.

RSVP block and session RSVP

The RSVP block sets the RSVP reply and submits the form. In its right-hand settings panel:

• Please select RSVP action — the RSVP value applied when the contact clicks the button (e.g. Attending).
• Button label — the text on the button (e.g. Accept).

If the event has Sessions enabled (see Event sessions), the RSVP block also shows a Sessions section:

• Turn on Allow users to select sessions to RSVP to.
• Session label — the label shown above the session Select on the form (defaults to "Sessions"; rename it to anything you like).
• Session selection is required — force the contact to pick at least one session.
• Show session date/time — display each session's date and time in the Select.
• Session question description — helper text shown with the session Select.

Once enabled, a session Select appears on the form and contacts choose which sessions they want to attend when they RSVP. Their per-session choices then show against them in the event's Audience table.

Single vs multiple contacts

Choose the contact block that matches how people register:

• Add/Update Contact — for a single registrant.
• Add/Update Contacts — for group bookings, allowing multiple contacts to be added. This block duplicates the basic fields and uses first name / last name / email matching. If you turn quantity off, the purchased quantity defaults to the number of contacts added.

For ticketed events where people often book several seats, Collect attendee details for each ticket on the Tickets block is usually the better choice — it creates one attendee space per seat bought (see Collecting a name for every seat above).

Preview, publish and finish

• Preview the form, then Publish or Share it as normal.
• Use Save and close to return to the event.

Building the RSVP page — step by step

1. In the event's RSVP section, click Create RSVP Page, enter a Form name, optionally choose a saved RSVP template under Start from a template (optional), then click Create RSVP page.
2. Drag the Calendar and Event Location blocks.
3. To personalise the form, drag a Rich Text block and insert event merge fields via the @ symbol or the @ Merge fields toolbar button.
4. Drag the Tickets block and select the available tickets (allow quantity if needed). To collect a name for every seat bought, tick Collect attendee details for each ticket.
5. For ticketed events, drag the Payment Method block and configure a provider or enable Invoicing (select Xero if using the Xero Integration).
6. For group bookings, either tick Collect attendee details for each ticket on the Tickets block (and use only the contact block it adds), or, with that setting off, use the Add/Update Contacts (multiple) block.
7. Drag the RSVP block last, and set its target RSVP value and button label. If the event uses sessions, turn on Allow users to select sessions to RSVP to in the same settings panel, then set the label, required, date/time and description options.
8. Preview and Publish, or use Save and close to return to the event.