Keep these constraints and recommendations in mind when planning and running events. They explain edge cases that can otherwise cause confusion.
RSVP text message reply window
- Replies are counted only within 24 hours of the scheduled send.
- Valid replies must be Yes/Y or No/N.
- Replies to a custom sender name are not supported — send from a text message number so replies can be received and processed.
RSVP form submission
- The RSVP Button must be the last button on the form, because it replaces the standard submit button. If it is not last, the form will not submit as expected.
Paid events
- The Payment Method block is required on the RSVP form for paid events.
- Select Xero in the invoicing dropdown if you want invoices to generate in Xero (via the Xero Integration).
Location rules
- Venue events require an address lookup.
- Online and Hybrid events must include an online meeting link.
AutoMail vs Send Rules
- AutoMail does not interact with Send Rules.
- Use AutoMail for an Initial Invite that should reach anyone added to the event later.
- Use Send Rules for targeted, scheduled segments based on RSVP status.
Bookings export
- The Bookings export is delivered by notification, not downloaded straight away. Open the notification that says the export has completed and select Click here to download. The link expires after 24 hours.
- The Bookings export has one row per booking, matching the Bookings table. Use its Tickets Purchased and Tickets Allocated columns for each booking's ticket counts.
- The Bookings table has no search, filter or sort. For a large event, export the bookings and work in a spreadsheet.
Sessions visibility
- The session assignment view (the eye icon) only appears for certain accounts.