A waitlist sounds like a simple feature until you actually need it to do two things at once: stop people from registering past capacity, and automatically re-fill a spot the moment someone cancels. Get the setup wrong and you end up with one of two problems — an event that’s technically “full” but still lets people in, or a waitlist that just sits there collecting names nobody ever gets invited from.
This guide covers how to set capacity correctly at every level it applies to, how to choose between automatic and manual waitlist processing, and what to check when a waitlist isn’t converting the way it should.
Decide where capacity actually needs to be capped
Before touching any settings, be clear on what is capped — this is the step people skip, and it’s the reason a waitlist can “work” at the event level while a specific session or attendee category still oversells.
- Event-level capacity — a hard cap on total registrations for the whole event.
- Category-level capacity — a cap on one specific registration type (e.g., only 6 exhibitor booths, even though the overall event has no cap).
- Session-level capacity — a cap on an individual breakout or workshop, independent of the overall event cap.
If you only set a cap at the event level, a single popular session or category can fill up while the event overall still shows availability — and attendees will be confused when they’re told a session is full but the event isn’t.
Step 1: Set the capacity limit(s)
- Go to your event’s Registration Settings (or Event Info, depending on your Cvent platform version) and find the Capacity or Registrant Rules section.
- Enter the maximum number of registrants for the level you’re capping — event, category, and/or session.
- Leave capacity fields blank for any level that shouldn’t be limited. A blank field is treated as unlimited, not zero — an easy mistake if you’re used to other platforms where blank means “closed.”
Step 2: Turn on waitlisting and write the messaging attendees will see
- Enable the Waitlist toggle for the event (and separately for any session or category that needs its own waitlist).
- Set the sold-out message — the text shown when someone hits a full event, category, or session. Be specific here; a generic “this event is full” message doesn’t tell people a waitlist option exists.
- Set the waitlist link/button text — what registrants click to join. “Join the Waitlist” performs better than vague phrasing like “Learn More,” since it sets a clear expectation.
Step 3: Choose automatic or manual waitlist processing
This is the setting that determines whether your waitlist actually does the work for you.
- Automatic processing — the moment a spot opens (someone cancels or is removed), the system automatically registers the next person on the waitlist, in the order they joined, and sends them a confirmation. Best for high-volume events where you don’t have time to manage this manually.
- Manual processing — an admin has to review the waitlist and invite the next person, who then has to confirm before the spot is locked in. Best when you need to control exactly who fills a spot (e.g., prioritizing by attendee category, sponsor tier, or approval status) rather than strictly by wait time.
If you choose manual, make sure someone on your team actually owns checking the waitlist regularly — a manual waitlist with no one monitoring it is functionally the same as having no waitlist at all.
Step 4: Set up the emails that go with it
A waitlist is only as good as the communication around it. At minimum, confirm these are turned on and correctly worded:
- Waitlist confirmation email — sent when someone joins the waitlist, so they know they’re on it (not registered).
- Spot-available / invitation email — sent when a spot opens, whether that’s an automatic confirmation or a manual “you’re invited to register” prompt.
- Cancellation confirmation email — sent to the person who cancels, which is what triggers the waitlist to check for the next name.
If you’re using manual processing, the invitation email should include a clear deadline to respond, and your process should define what happens if that deadline passes (move to the next person automatically, or hold the spot open).
Step 5: Test the full cycle before you rely on its that go with it
Don’t just test that the waitlist accepts someone — test that it actually fills a spot.
- Set a temporary low capacity (e.g., 2) on a test category or session.
- Register two test accounts to fill it, then register a third — confirm they’re offered the waitlist, not blocked outright.
- Cancel one of the first two registrations.
- Confirm the third account is automatically registered (if automatic) or receives an invitation (if manual), and that the correct emails fire at each step.
- Reset the capacity back to its real number once testing is confirmed working.
Common issues and how to fix them
People are still registering after the event shows “full.” Check whether capacity is set at the level you think it is. A cap on the event overall won’t stop registrations to an uncapped category or session within it.
The waitlist isn’t moving anyone up after a cancellation. Confirm the cancellation is going through the system’s cancel workflow, not just a manual deletion of the record — a deleted registration doesn’t always trigger the same waitlist check that a proper cancellation does.
Waitlisted people never hear anything. Check that the waitlist-related email triggers are actually turned on — they’re separate from your standard registration confirmation emails and are easy to leave off during initial setup.
A category or session is oversold despite a waitlist being “on.” Waitlisting has to be enabled at the same level as the capacity that’s being hit — enabling it only at the event level won’t protect a specific session or category.
The takeaway
A working Cvent waitlist comes down to matching three things at the same level — capacity, waitlist enablement, and the emails that drive it — rather than assuming an event-level setting covers everything underneath it. Set the cap where the real constraint is (event, category, or session), pick automatic or manual based on how much control you need over who fills a spot, and run a full cancel-to-refill test before you trust it on a live event.