How to Run a Waitlist for a Sold-Out Event

The short version of how to run a waitlist for a sold-out event: let people join without paying, keep the line in the order they joined, and give a freed seat to the first person who still fits it. On a free event that can run on its own. On a paid event, don’t admit anyone until they’ve paid, which means a human makes the call.

Most help articles on this topic are a vendor explaining where their own button lives. That’s the easy part. The part organizers actually lose sleep over is the judgement: how long to keep the list open, who goes first, what to say to someone who’s number nine, and what to do when a seat frees up the night before.

This post is about those calls. The button-clicking side is covered in the RSVP feature page and the paid-event waitlist docs.

What a waitlist is actually for

A waitlist does two jobs. It stops you turning people away at the exact moment they were ready to say yes, and it gives you a measure of real demand you can use next time.

That second one is underrated. If forty people queue for a twenty-seat workshop, you’ve learned that you should have booked a bigger room or run it twice. A “Sorry, this event is full” message teaches you nothing, because the people who hit it just leave.

It’s also a safety net for the dull reason that people cancel. A sold-out event is rarely a full one on the day. Someone gets ill, a train is cancelled, a plan changes. Without a list those seats go empty while a person who wanted one sits at home.

Free events: let the line run itself

For a free event the best waitlist is one you never touch. When a registered guest cancels, the next person in line moves up and gets told, and you hear about it only if you check.

Two details matter more than they look. First, seats should be freed by the size of the party, not the head count of one. If someone who was bringing two guests cancels, three seats open up, and the line should move by three. Second, the order should be strict. If the next person in line is a party of four and only three seats are free, skipping them to seat a smaller group further back feels unfair, and people notice.

Eventonomy does both of these on RSVP events: it walks the waitlist in order, sized to each party, and stops at the first party that no longer fits. Seat claims are atomic too, so two people grabbing the last seat in the same instant can’t both get it. One gets in, the other joins the list, and nobody sees an error.

Paid events: nobody gets in without paying

Paid events are different, and this is where a lot of organizers (and plenty of plugins) get it wrong. If a waitlist promotes someone straight to “going” on a ticketed event, you’ve just admitted a person who hasn’t paid. Somebody then has to chase them for the money, or you quietly give away a seat.

So in Eventonomy the waitlist on a paid event never promotes anyone automatically. People can still join, with just a name and an email, and nothing is charged. When a seat opens up, you choose who gets it and how they pay. That’s a manual step, and it’s deliberate. There’s no automatic claim-to-purchase link for a freed paid seat, so you’ll message the person yourself and point them to the event page once tickets are available again.

If that sounds like more work, it is, but only slightly. Paid events are usually smaller, and the people on the list are warm. A short personal message converts better than an automated one anyway.

Deciding who gets a freed seat

First come, first served is the right default, and you should say so up front. It’s easy to explain, hard to argue with, and it needs no judgement from you at 11pm.

There are a few reasonable exceptions, and they work when you tell people about them in advance:

• A speaker’s guest, a sponsor, or a volunteer who needs a place. Treat those as separate allocations, not as queue-jumping.
• A member-only event where members go first. State it on the event page.
• A group that must stay together. Admit the whole party or none of it.

What you shouldn’t do is play favourites silently. People talk, and a waitlist that looks rigged does more damage than a “sorry, full” message ever did.

What to tell the people on the list

Be honest about the odds. “You’re number nine, and we usually see two or three cancellations” sets a better expectation than “we’ll let you know!” Don’t promise a seat. Do promise to email when you know.

Say what happens next, in plain words: you’ll be told if a seat opens, how long they’ll have to confirm, and that they should make other plans in the meantime. For a paid event, say that they’ll pay when a seat is offered, not now.

Tell them when you’ll stop. Decide on a cut-off, say a day before the event, and after it, release the list with a note saying thanks and when the next date is. Nobody wants to be left wondering whether they’re in on the morning of the event.

Cutting no-shows so you need the list less

The cheapest way to get more out of a waitlist is to have fewer empty seats in the first place. A few habits help.

Set an RSVP deadline, so people have to decide while there’s still time for someone else to take their place. Send reminders before the event, because a reminder gets you either a “yes, I’m coming” or a cancellation, and both are useful. A cancellation a day early is a seat you can fill. A no-show is a seat you can’t.

Make cancelling easy. If a guest has to email you to cancel, many won’t bother. A magic link in the confirmation email that lets them change their answer in one click means more early cancellations and fewer ghosts.

Turning on a waitlist in Eventonomy

In the free plugin it’s one setting: Waitlist when full, under Eventonomy → Settings → Registration. Switch it on and the RSVP block’s button reads Join waitlist once an event is at capacity. On free RSVP events, promotion is automatic. On a ticketed event the person joins the same way, and you admit them by hand from the attendee roster.

A word on what needs Pro. The waitlist itself is free. Selling the tickets that make an event “paid” in the first place needs Pro, which adds Stripe, PayPal and WooCommerce checkout. The free vs Pro page has the full split, and the event tickets page covers the paid side. If you only run free events, you won’t need to think about any of it.

The roster is where you do the work: you can see the queue in order, message waitlisted people, and move someone to going when you’ve decided to admit them. Take care with that last one on a paid event. It records the person as going without a ticket or a payment, so it’s for people you’re admitting free of charge. For everyone else, send them to the event page to buy a ticket. See event registration for how the rest of the flow fits together.

One last rule

Whatever you decide, write it down in one short paragraph and put it on the event page. A waitlist works when people know the rules before they join. It falls apart when the rules are invented the night a seat opens up.