How to Handle a Waitlist When Your Padel Courts Are Fully Booked

The moment a slot fills up, demand doesn't disappear

It just becomes invisible.

A member checks the schedule, sees the 7pm slot on Court 2 is taken, and either messages you on WhatsApp asking to be told if it opens, or quietly gives up. The first outcome creates admin work. The second loses you a booking you could have filled.

At most private padel clubs, this is managed informally — a mental note, a sticky note, a screenshot of a WhatsApp message that says "let me know if anything comes up." It sort of works when you have a handful of regulars. It breaks down completely when your courts are popular.

What clubs are actually doing today

When we talk to club admins, the waitlist situation usually looks something like this:

• A member messages asking about a specific slot — the admin mentally notes it.
• If that booking cancels, the admin tries to remember who asked, finds the message buried in WhatsApp, and reaches out manually.
• The member may or may not respond. If they don't, the admin either leaves the slot empty or scrambles to find another person.
• No record is kept. No one else in line is notified. The slot may go unfilled despite real demand.

This is a lot of work for an outcome that should be automatic. And when there are multiple people interested in the same slot, there's no fair ordering — whoever happens to message at the right time gets priority, not whoever asked first.

What a proper waitlist actually needs to do

A waitlist is only useful if it handles the entire chain — not just capturing names, but notifying people and managing confirmations. Here is what that looks like in practice:

1. Members join the queue from the schedule

When a slot is fully booked, members should be able to join a waitlist directly from the booking schedule — not by sending a WhatsApp message, not by calling the club. The same interface they use to browse availability should let them register interest in a taken slot. No login required, no back-and-forth.

2. The queue is ordered and transparent

First in, first served. The order is set at the moment each person joins, and it doesn't change. No one gets bumped because they messaged the admin separately. The system keeps the queue, not the admin's memory.

3. When a booking cancels, the next person is notified automatically

The moment a cancellation happens, the system should immediately contact the first person in the queue — by WhatsApp and email — with a link to confirm the slot. No admin involvement required. The slot is held for a fixed window (30 minutes is a reasonable default) to give them time to respond.

4. If they don't confirm, the notification passes to the next person

If the first person doesn't confirm in time, the slot moves to the next person in the queue, and so on down the line. Each person gets a fair window. If the entire queue passes, the slot opens back up on the general schedule.

5. Confirmation is one tap

The friction between "notified" and "confirmed" should be as close to zero as possible. A one-tap magic link — no login, no form to fill out — is the right model. The moment they click it, the booking is created and they receive a full confirmation over WhatsApp and email.

What this looks like from the admin's side

Ideally, managing a waitlist takes zero active time from your admin team. Here is what happens when a booking is cancelled in Cadences:

1. The admin deletes the booking. The slot is immediately marked as "Blocked for waitlist" on the calendar — it doesn't open up for general booking while there are people in the queue.
2. The first person in the waitlist receives a WhatsApp and email notification with a one-tap confirmation link.
3. If they confirm, their booking appears on the calendar automatically. The block is removed. Admins get a notification that the slot has been filled.
4. If they don't confirm within 30 minutes, the next person in line is notified. This continues until someone confirms or the queue is exhausted.
5. If no one confirms, the block is removed and the slot reopens for general booking.

The admin's only action in this entire process is step one — deleting the original booking. Everything else is handled automatically.

Admins can also view and manage the waitlist manually at any point — seeing who is in the queue, removing someone if needed, or adding a member directly. But in most cases, there is nothing to do.

Why this matters beyond convenience

A well-run waitlist does more than save admin time. It changes how full courts feel at your club.

When members know that joining a waitlist actually works — that they'll hear from you automatically if a slot opens, and that the process is fair — they stop sending speculative WhatsApp messages. They trust the system. The admin stops being the bottleneck between supply and demand.

For the club, this means fewer cancelled slots going empty. When a booking drops, there is a structured queue already in place. The slot has a real chance of being refilled before the window closes.

For members, it's a better experience than a system where the outcome depends on whether the admin happened to remember their message.

How Cadences handles this

Cadences includes a built-in slot waitlist as part of the Starter plan. Members join directly from the guest schedule, the queue is maintained automatically, and notifications go out over WhatsApp and email the moment a cancellation comes in.

When you look at a "Blocked for waitlist" slot on the admin calendar, you can see who's in the queue, their position, and their status — and take any manual action if needed. It's designed to require as little admin involvement as possible while keeping full visibility when you want it.

If you're running a club where popular slots fill up quickly, it's worth seeing how this works in practice.