Operations

Updated Oct 2026

Waitlists that actually fill cancelled slots

A waitlist is not a list. It is a queue with a deadline, and if the deadline is missing, nothing happens.

Why the usual waitlist fails

The typical version is a notebook, or a "notes" field in the client record, holding names with no preference for day, time or service. When a slot opens, nobody knows who to call, so nobody calls. The list grows, the slots stay empty, and after a few months the staff stop writing names down.

Three things are usually missing. The entry does not say what the client would actually accept. There is no trigger that fires when a slot appears. And there is no rule for who gets it, so the first person to answer wins by luck rather than by fit.

Fix those and a waitlist becomes the cheapest capacity tool you own — it converts demand you already have into slots you already paid for.

The three parts that matter

1. A specific request, not a wish

Capture three fields at minimum: the service, the acceptable window, and how much notice they need. "Any Saturday, mornings, can come in with two hours' notice" is usable. "Whenever you have something" is not — it puts the matching work back on your desk, which is the failure you were trying to avoid.

2. A trigger tied to the slot, not to a person

The message should fire when a slot is released: a cancellation, a moved appointment, an added shift. Not when someone remembers to check the book. If your tool cannot trigger on a cancellation, the manual version is a single daily task at a fixed time — better than nothing, but it will miss same-day gaps, which are the ones worth filling.

3. A rule for who gets it

Broadcast to everyone matching, first reply wins, and say so in the message. Sequential calling — one person at a time, waiting for an answer — is more polite and much slower; it usually loses the slot. Broadcast with an explicit "first reply" line is faster and, provided you close the loop, feels fair.

What the message should say

Short, specific, and time-stamped. The difference between a message that fills a slot and one that gets ignored is usually the amount of thinking it demands:

Send it from a name, not the brand. And do not attach an offer — a discount on top of a freed slot trains clients to wait for cancellations instead of booking.

The automation rules

Booksy, Fresha and Square Appointments each offer some form of waitlist or "notify me" list, with different degrees of automation; check current pricing and whether the notification fires on cancellation or only on request. Whichever you use, these five rules cover most of the edge cases:

1. Match on service and window. Do not message a client who wants Saturdays about a Tuesday morning.
2. Respect the entry's expiry. A request for "this week" should drop out by itself; stale entries are why lists rot.
3. Hold the slot for the first reply for a fixed time — ten or fifteen minutes — then release it to the next in line if the reply does not turn into a booking.
4. Cap messages per client per month. Two or three is enough. More and they mute you, which also kills your reminders.
5. Confirm back immediately. "You're booked for Saturday 10:00" ends the race; silence invites a second client to arrive for the same slot.

The double-booking risk nobody plans for

Broadcast waitlists create a race. If two clients reply within a minute and both get a friendly "great, see you then", you have promised one chair twice. The fix is procedural: only one message may confirm, and it must come from the calendar, not from a person replying in a chat thread. If the desk handles it manually, the rule is that the booking is entered first and the confirmation sent second — never the other way round.

When a waitlist is the wrong tool

If your problem is that Tuesday afternoons are permanently empty, a waitlist will not help; nobody is waiting for Tuesday. That is a pricing or marketing problem. Waitlists fill gaps in demand that already exists. They are also poor for services that need preparation — mixed colour, ordered stock, a guest practitioner — because a two-hour notice is not enough time to be ready.

What to measure

Track fill rate (slots offered versus slots filled), median time to fill, and how many waitlist entries convert within thirty days. If the fill rate is low, your windows are too narrow. If entries never convert, the messages are going out too late or to the wrong people. Both are fixable without changing platforms.