RSVP Tickets
Eventixa includes RSVP registration for events where attendees need to respond with Going or Not Going instead of purchasing a standard ticket.
RSVP registration is useful for free events, community gatherings, internal events, meetups, and other situations where you want attendance responses without a payment workflow.
Available in: Eventixa Core
Location: Eventixa → Events → Edit Event → Tickets & RSVP
Related features: Attendees, Capacity, Check-In, Waitlist
What Is an RSVP Ticket?
An RSVP ticket is a free registration type designed around attendance intent.
Depending on the RSVP configuration, attendees can respond with:
- Going
- Not Going
RSVP does not use the normal paid-ticket checkout workflow.
Open RSVP Settings
Go to:
Eventixa → Events
Open the event you want to configure.
Then select: Event Settings → Tickets & RSVP
Click: Add New RSVP
Eventixa opens the RSVP editor.
Standard Tickets vs RSVP
These are different registration types.
| Feature | Standard Ticket | RSVP |
|---|---|---|
| Free registration | Yes | Yes |
| Paid registration | Yes | No |
| Going response | No | Yes |
| Not Going response | No | Optional |
| Payment required | For paid tickets | No |
| Attendee records | Yes | Yes |
Choose RSVP when the event needs attendance responses rather than ticket purchasing.
Create an RSVP
Click: Add New RSVP
Enter a visitor-facing name.
Examples:
- Event RSVP
- General RSVP
- Workshop Attendance
- Community Meeting RSVP
- Guest Attendance
Use a name that clearly explains what the attendee is responding to.
RSVP Description
Add a short description if attendees need more context.
For example:
Let us know whether you plan to attend the community meetup.
Keep the description concise.
Going
Going represents attendees who confirm that they plan to attend the event.
A Going RSVP can:
- Reserve capacity
- Create attendee records
- Collect attendee information
- Participate in attendee counts
- Be eligible for check-in where applicable
Not Going
Eventixa can also allow a Not Going response when enabled for the RSVP ticket.
This is useful when you want invited users to explicitly tell you they will not attend.
Not Going attendees are tracked separately from Going attendees.
Enable Not Going
Where available, enable the Not Going option in the RSVP configuration.
Use it when explicit declines are useful for planning.
For example:
- Invite-only events
- Community meetings
- Internal events
- Member gatherings
If you only care about positive registrations, you can leave Not Going disabled.
RSVP Quantity
Eventixa RSVP registration can support quantity selection.
This means one purchaser can respond for more than one attendee where allowed.
For example:
Quantity: 3
Eventixa can then collect information for three individual attendees.
Minimum Quantity
Set the minimum allowed RSVP quantity.
For example:
Minimum: 1
This is the normal setting for most RSVP registrations.
Maximum Quantity
Set the maximum number of attendees allowed in one RSVP submission.
For example:
Maximum: 4
This prevents one registration from reserving an excessive number of places.
Individual Attendee Information
Eventixa can collect attendee information for each RSVP participant.
At minimum, the individual attendee workflow can require:
- Name
This is useful when one person registers multiple attendees.
Why Individual Attendee Information Matters
Suppose a user selects:
Going Ă— 3
Instead of storing only the purchaser, Eventixa can collect information for all three attendees.
This improves:
- Attendee lists
- Check-in
- Communication
- Reporting
- Capacity accuracy
RSVP Capacity
An RSVP ticket can have its own capacity.
For example:
Capacity: 250
Going registrations consume the available capacity according to the Eventixa RSVP workflow.
Not Going responses do not represent occupied attendee places.
RSVP Summary
The event editor can provide an RSVP Summary showing information such as:
- Capacity
- Remaining
- Going attendees
- Not Going attendees
- Checked In
- Waitlist
This gives you a quick view of RSVP activity without leaving the event editor.
Going Counts by Attendee
RSVP counts are attendee-based.
For example, if one booking contains: Going Ă— 4
the Going count reflects four attendees rather than just one booking.
This makes event capacity and RSVP summaries more accurate.
Not Going Counts by Attendee
The same attendee-based counting applies to Not Going responses.
For example:
One RSVP booking with two Not Going attendees contributes:
Not Going attendees: 2
rather than one response.
RSVP and Payments
RSVP registration does not require payment.
There is no paid invoice requirement for an RSVP response.
If you need attendees to pay, use a standard paid ticket instead.
RSVP and Ticket PDF
Not Going attendees should not receive normal attendee ticket access intended for actual participants.
Going attendees can use the supported Eventixa attendee workflow.
RSVP and Check-In
Going attendees can participate in check-in where supported.
Not Going attendees should not be treated as check-in candidates.
This keeps attendee operations aligned with the actual RSVP response.
RSVP and Waitlist
Where Waitlist is enabled, a full RSVP capacity can participate in the Eventixa waitlist workflow.
This is useful when the event has limited free attendance.
If capacity later becomes available, the normal Eventixa reservation workflow can be used according to the waitlist configuration.
RSVP on the Frontend
The RSVP interface appears in the main event content area.
Visitors can select the applicable RSVP option and quantity.
Depending on configuration, the frontend can show:
- Going
- Not Going
- Quantity selector
- Availability
- Attendee fields
RSVP Quantity Example
Suppose the RSVP configuration is:
| Setting | Value |
|---|---|
| Capacity | 100 |
| Minimum | 1 |
| Maximum | 4 |
| Not Going | Enabled |
A visitor could submit:
Going Ă— 3
and provide attendee information for all three participants.
Multiple RSVP Tickets
Eventixa can support more than one RSVP ticket for an event where appropriate.
For example:
Morning Session RSVP
Capacity: 50
Evening Session RSVP
Capacity: 75
Each can maintain its own registration configuration.
RSVP and Recurring Events
RSVP can also be used with recurring events.
For recurring events, make sure the RSVP registration remains associated with the correct occurrence.
Test more than one occurrence before opening registration.
RSVP Attendees in Administration
RSVP attendees appear in Eventixa attendee management.
You can review information such as:
- Name
- RSVP status
- Event
- Check-in state
This makes RSVP attendees manageable alongside standard-ticket attendees.
Editing RSVP Configuration
You can reopen an RSVP ticket and change supported settings such as:
- Name
- Description
- Capacity
- Quantity limits
- Not Going behavior
- Attendee information settings
Be careful when changing an RSVP configuration that already has registrations.
Deleting an RSVP Ticket
Before deleting an RSVP ticket, check whether it already has attendees.
If registrations exist, review those records before removing the ticket.
If you only need to stop new registrations, closing availability may be safer than deleting active registration data.
Example: Community Meetup
Configuration:
| Setting | Value |
|---|---|
| RSVP | Community Meetup RSVP |
| Capacity | 100 |
| Going | Enabled |
| Not Going | Enabled |
| Min Quantity | 1 |
| Max Quantity | 4 |
Visitors can confirm attendance without payment.
Example: Invitation Event
For an invitation-only event, you may want:
- Going
- Not Going
This gives organizers a clearer headcount than only collecting positive registrations.
Example: Free Workshop
A free workshop can use RSVP rather than a free standard ticket if attendance intent is more important than a normal ticket-style workflow.
Choose the registration type that best fits the event experience.
Free Standard Ticket vs RSVP
Use a free standard ticket when you want the normal ticket-and-checkout style registration.
Use RSVP when you want an attendance-response workflow.
Free Ticket
Best for:
- Ticket-style registration
- Standard booking flow
- Ticket delivery
RSVP
Best for:
- Going / Not Going
- Invitations
- Attendance confirmations
- Simple free registration
Common Problems
Add New RSVP Does Not Appear
Make sure you are editing an Eventixa event and viewing:
Tickets & RSVP
Not Going Is Missing
Check whether the RSVP ticket has the Not Going option enabled.
RSVP Quantity Is Limited
Review:
- Maximum quantity
- Remaining capacity
Going Count Looks Higher Than Booking Count
This can be correct.
RSVP counts are based on attendees, so one booking can represent multiple Going attendees.
Not Going Attendee Received the Wrong Workflow
Review the RSVP status and attendee handling.
Not Going records should not be treated as normal attending ticket holders.
RSVP Is Asking for Payment
Verify that you created an RSVP registration rather than a paid standard ticket.
Recommended Workflow
- Create or edit the event.
- Open Tickets & RSVP.
- Click Add New RSVP.
- Enter the RSVP name.
- Add a description if needed.
- Configure capacity.
- Enable Not Going if required.
- Set minimum and maximum quantity.
- Configure attendee information.
- Save the RSVP.
- Preview the frontend form.
- Test a Going response.
- Test a multi-attendee Going response.
- Test Not Going if enabled.
- Review the RSVP Summary and attendee records.
Important Notes
- RSVP is free and does not use the paid-ticket payment workflow.
- Going and Not Going are tracked separately.
- RSVP counts are attendee-based.
- Quantity can represent multiple individual attendees.
- Collect attendee information when individual records are important.
- Not Going attendees should not receive attendee ticket/check-in treatment intended for Going attendees.
- Test RSVP on recurring occurrences separately when recurrence is enabled.
