Why a full sauna waitlist can still leave empty places

A waitlist is a queue of requests, not a queue of people who will turn up. A cancelled place is only refilled if someone on the list gets it early enough to use it. A long list for a Saturday morning session can hide losses at several points along the way.

Start with one released place and follow it to the end. A bigger waitlist will not help if the confirmation reaches someone after they would have had to leave home.

Reconcile the funnel

Imagine ten places opening up across a week of sold-out sessions. This hypothetical ledger records what happened to them:

Five of ten places were refilled with someone who came: an attended refill rate of 50%. Counting the eight promotions instead gives 80%. Both numbers are correct, but only the first tells you how many places were actually used.

This is an example for diagnosis, not a studio's result. A delivered email can go unread, and someone can still come after a failed email because they checked their account. Use the stages to investigate a case, not as a fixed chain of cause and effect.

Separate timing from willingness

For a 6 p.m. session, someone who needs 40 minutes to get there is no longer a realistic replacement at 5:30. They meant it when they joined; the opportunity changed after that.

Record when each place was released, when the booking changed, when the notification went out and whether the person came. Then compare losses by how much notice the place had. Losses bunched in the final hour point to travel and availability. Losses spread across every lead time point more toward misunderstanding or delivery.

Know what your booking system does with a freed place

Waitlists differ on the step that matters most here: whether a freed place is booked straight away or offered and held for a reply. Pvolve's studios, for example, book waitlisted members automatically in the order they joined, for cancellations more than two hours before class, and tell late hopefuls to arrive early for no-show places.¹ An offer that waits for a reply loses time; an automatic booking can land on someone who can no longer come. Know which one your system does before you read its numbers.

In Elara, a freed place goes to the waitlist automatically, first in, first out, and the promoted bather is booked straight away and gets a confirmation email, which is on by default and which you can edit or turn off.² Three details decide whether that place is used:

• The cutoff. Promotion stops once online booking closes: at your booking cutoff, or at the session start if you set none, which is the default. A cutoff also closes ordinary online booking for that session at the same time. A place freed after that stays empty unless staff move someone in by hand. If late promotions keep producing no-shows, a cutoff an hour or so before the start may leave the place to a walk-in instead.
• Group size. A bather on the list with friends is promoted only when the whole group fits. If one place opens and the first entry is a party of three, promotion waits rather than skipping to a single bather further down, and the place can stay empty.
• Funding. A bather whose credits no longer cover the session stays on the list and the next eligible person is booked. If you approve bookings manually, promotion creates a request for you to approve rather than a confirmed place.

Because promotion books the place directly, do not tell bathers they will be asked to confirm first. Tell them what they are committing to when they join, and that they can leave the waitlist from their account at any time until the session starts.

Make money timing explicit

On a paid session, joining Elara's waitlist charges the drop-in price up front, for the whole group if friends are included. If no place opens, the payment is refunded automatically once the session's day is over. On a session paid with credits, nothing is used to join, and the credits are taken only when the bather is promoted. The two feel different to the bather, so explain the one they are in.

For a paid waitlist, something like: "Joining charges you now. If you don't get a place, we refund you after the session." For credits: "No credits are used to join. If a place opens, we book you in and use your credits then." Avoid a blanket promise that nobody pays until a place opens.

It also changes support. "Why was I charged?" and "Why did my credits go down?" need the funding path and booking state, not just "you're on the waitlist".

Count people, not entries, before adding sessions

Suppose twelve waitlist entries belong to five people. Four of them later come to a different session; the fifth never finds a time that works. Twelve entries are not demand for twelve more visits.

For a timetable decision, count the unique bathers looking for another time, which sessions they treat as substitutes and whether they eventually came. Keep that separate from the day-to-day queue, where each session still needs its own list.

A 6 p.m. list that fills week after week may justify trying a session nearby. Overlapping lists from the same few regulars may call for clearer booking rules or earlier release of places people are not going to use instead.

Fix one failure at a time

If places are released too late, review your cancellation window and booking cutoff. If bathers misunderstand the commitment, rewrite the joining copy and the confirmation. If confirmations are not arriving, check the address, the bather's own email settings (they can turn email off entirely, or only waitlist updates) and whether the address is suppressed after a bounce.³ If people are promoted but keep failing to come, look at how much notice they need and who is eligible to join.

After a change, measure attended refills alongside no-shows and complaints. A longer waitlist or more notifications sent is not a success on its own. For booking and attendance states, see Elara's booking page.

Ask for a quote. When you set up, fill a session, join its waitlist as a second bather, cancel the first booking and follow the place to the roster.