Make capacity, status and next steps visible
RSVPs, capacity, waitlists, guest lists, manual attendance and attendee CSV export are included in Free. A signed-in visitor can join a published event; once the confirmed capacity is reached, the next response receives Waitlist status. A blank or zero capacity means unlimited. Pro adds paid checkout, verified guest checkout, promo codes, transaction records and browser QR or manual check-in.
Use one primary attendance action
Use Free RSVP for a simple “I’m attending” journey or an external booking link when registration happens elsewhere. Use Pro ticketing when NexDirectory must take payment, verify guest buyers or manage QR entry.
The RSVP button is a safe toggle for one user
The RSVP action is available on a visible event to a signed-in member. Joining adds the attendee; cancelling removes them and refreshes the confirmed and waitlist counts shown to the member and organiser.
For non-event profiles, the same member page presents saved listings without capacity. Labels adapt to Save Listing, Save Job or the chosen profile’s saved-item language, while the canonical page remains [nexdirectory_saved_listings].
Capacity decides who is confirmed and who waits
Set capacity to the number of places you can genuinely confirm, not the room’s theoretical maximum. NexDirectory checks the confirmed count as people join and places later responses on the waitlist once the limit is reached.
A cancellation creates a possible opening, but your team still needs a clear promotion and communication process. Decide who reviews the waitlist, how they contact the next person and how long an offered place is held.
Connect personal and organiser views
The canonical personal page uses [nexdirectory_saved_listings] and shows confirmed or waitlist status with cancellation controls. The attendee page uses [nexdirectory_whos_attending] for people allowed to view the event’s attendance information.
Single event pages can show RSVP and waitlist counts. Test privacy and role behaviour before publishing attendee identities. Counts, organiser access and public visibility are separate decisions; expose only what the event genuinely needs.
Launch and test a capacity-controlled RSVP
Choose the real confirmed limit
Allow for staff, accessibility space and safety requirements, then enter the maximum number of attendee places. Use zero only for a genuinely unlimited event.
Connect the attendee pages
Publish the personal saved/attendance page and, when organisers need it, the Who’s Attending page. Check that their routes work on a phone.
Test joining and cancelling
Sign in as a member, RSVP, confirm the status and essential email, open the personal page, then cancel and verify the count changes.
Test the final place
Use test accounts to reach capacity, then join once more. Confirm that the extra response is clearly labelled Waitlist in both the attendee and organiser views.
Write the waitlist procedure
Name the person responsible, the contact method, the response deadline and how manual attendance updates will be recorded.
RSVP checklist
- Event is published and visible
- Capacity matches the real confirmed limit
- Login / Sign Up route works
- First RSVP receives Yes status
- Post-capacity RSVP receives Waitlist status
- Cancel removes the user’s row
- Personal attendee page shows current status
- Organiser has a documented waitlist process
Questions you may have
Can a logged-out visitor use the standard RSVP button?
Standard RSVP requires a member account. If registration happens elsewhere, use a Free external booking link. Use Pro ticketing when you need an on-site paid or ticketed journey.
What does capacity 0 mean?
The RSVP logic treats a non-positive capacity as unlimited, so new RSVP rows receive confirmed status rather than waitlist status.
Does cancelling automatically contact the first waitlisted person?
Do not assume it does. Use the organiser view and your documented waitlist process to offer the place and record the outcome.
Why does Directory profile say Save Listing instead of RSVP?
The interaction adapts to the chosen profile. Capacity and attendance apply to Events; other profiles present the action as saving a listing, job or marketplace item.