A cancellation stops costing you money. Describe your services and Taskade Genesis builds a waitlist app that keeps an ordered standby list, and the moment a booking frees up it messages the right person, gives them a short window to accept, and moves down the list if they pass.
The Class Booking Portal is a live Taskade Genesis app on this page. It takes sign-ups against sessions rather than running a standby list, so start there: press "Use this app" to clone it in about ten seconds, then add the waitlist records, the offer step, and the fallthrough described below.
Most waitlists die because they live in someone's head or in a note on the desk. By the time a Tuesday slot opens up, nobody remembers who wanted Tuesdays. An ordered list with the person's constraints attached, sitting in the same app as the bookings, changes that entirely: the freed slot has an obvious next owner and the message writes itself.
What the build gives you: a waitlist record per person with the service they want, the days and times that work for them, how urgently they need it, and how long they have been waiting. Plus an offer step with an accept-by deadline, an automatic move to the next person when an offer lapses, and a conversion count so you can see how much of your lost revenue the waitlist recovers.
The same list renders in the layouts you need:
- List view for the ordered standby queue, oldest waiting at the top
- Table view to filter by service, preferred day, and urgency when a specific slot frees up
- Board view to move people through Waiting, Offered, Accepted, and Lapsed
- Plus Calendar, Mind Map, Gantt, and Org Chart across the rest of the 7 project views
Automations do the offering. A field update trigger fires when a booking becomes Cancelled or Released, a filter finds waitlist entries that match the freed day and service, and the top match receives an offer by email and SMS. A delay action waits your accept window, then a branch either confirms the booking or moves to the next person. Across 100+ bidirectional integrations, forms and Gmail pull requests in while SMS, email, and Slack push offers out. Automations run on paid plans; the Free plan includes 10 flow runs in total.
The AI agents in the app carry 34 built-in tools including persistent memory. The Waitlist agent writes the offer in a way that respects the short notice, remembers who has declined three offers in a row, and suggests when a service is waitlisted often enough to justify adding hours.
A waitlist is also the cheapest demand signal you will ever collect. It records what people wanted at the moment they wanted it, including the times you could not sell them. Read it once a quarter and it will tell you whether to open an extra evening, hire, or raise your price on the sessions that fill first. That is a strategic answer produced as a by-product of not losing bookings.
Clone the app, invite your team, and the list is yours. Nobody rents you access to your own standby customers.
Learn field-change triggers in Learn, branching in Learn, and SMS through the Twilio integration. Browse live builds in the Community Gallery. Pair this with the hold and release flow so an expired hold feeds the waitlist, and the reschedule and cancellation flow so cancellations arrive early enough to be useful.
Frequently Asked Questions
How long should the accept window be?
Short enough to keep the slot fillable and long enough to be fair. Two hours works for a next-day slot, thirty minutes for a same-day one. State the deadline as a clock time rather than a duration so nobody has to do arithmetic.
Does it offer to one person or blast the whole list?
Offering one at a time is the honest version and it is what this build does by default. A blast fills the slot faster but creates a race, and the people who lose it remember. You can switch to offering the top three simultaneously if speed matters more than goodwill.
How does it know who matches a freed slot?
Each waitlist entry stores the service wanted and the days and times that work. A filter matches those constraints against the freed booking, so a Tuesday morning opening is never offered to someone who only does weekends.
What happens when someone declines?
They stay on the list with their position intact and a declined count on the record. Repeated declines are useful information: it usually means their real constraint is narrower than what they told you.
Can people add themselves to the waitlist?
Yes. Point your booking form at the waitlist when nothing suitable is available, and the request becomes a standby entry instead of a dead end. That single change turns a "sorry, we are full" moment into a captured customer.
Does the waitlist take payment?
Not usually, and it should not. Ask for payment when the offer is accepted, using the Stripe Checkout Session action, so nobody is holding money for a slot that may never appear.
How do I know if the waitlist is worth running?
The app counts offers made, offers accepted, and slots recovered. Multiply recovered slots by your average booking value and you have the number. Most operators find the waitlist pays for the whole app inside a month.
Can I run separate waitlists per service or location?
Yes. Store service and location on each entry and filter the views accordingly. A multi-site business usually wants one shared list with a location field rather than several disconnected lists, which is covered in the multi-location booking desk prompt.
