A cancellation at nine becomes a filled slot by half past, because the waitlist is already sorted and the offer goes out the moment the gap appears. Instead of scrolling a notebook for someone who might take a Tuesday morning, you get a ranked list of people who said they would, matched to the provider and appointment length that just came free.
Start from the When Free. It is a live Taskade Genesis app for collecting when people are genuinely available, which is the raw material a waitlist runs on rather than a finished waitlist. Work it for a minute, then clone it into your own workspace in about ten seconds and add the offer log, the ranking, and the first-to-accept rule on top of the availability it already captures.
The build includes a waitlist record capturing who wants an earlier appointment, which providers they will see, which days and times actually work for them, and how urgently they want to move. It adds an offer log so you know who was asked and when, a first-to-accept rule so a slot is never promised twice, and an AI agent that ranks candidates against the specific gap rather than by signup order.
The waitlist is readable in the layout that matches the moment:
- Board view with lanes for waiting, offered, accepted, and booked
- Table view for the full list with availability windows and provider preferences
- Calendar view to see open gaps against who could fill them
- Plus the rest of the 7 project views
Automations make the speed possible. On paid plans, Taskade automations detect a cancelled appointment, build the shortlist, send the offer to the top candidates, and close the slot on the first acceptance. Across 100+ bidirectional integrations, your calendar pulls the cancellation in while Gmail and Slack push the offers and the internal update out. The mechanics start with automation triggers.
The AI agents carry 34 built-in tools including persistent memory. The ranking agent remembers who has declined three short-notice offers in a row and stops putting them at the top, which keeps the list useful rather than nominally long.
Workspace DNA is what makes a waitlist worth keeping. Memory holds each person's stated availability, their provider preference, and every offer they have already declined. Intelligence, drawing on 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, matches the specific gap to the people who could realistically take it. Execution sends the offers and closes the slot on the first acceptance, in the minutes that actually matter.
Running it in your practice
- Clone the app and publish the join form. Put the link where people already ask, which is usually the booking confirmation and the phone script.
- Ask only what the matching needs. Provider, acceptable days, acceptable times, and urgency. Every extra question costs you entries on the list.
- Set the offer batch size. Three to five at once with a first-to-accept rule fills slots quickly without promising the same appointment twice.
- Decide the acceptance window. Thirty minutes for a same-day gap, longer for next week. The window is what stops a slot being held open all afternoon.
- Prune quarterly. Ask everyone on the list whether they still want an earlier appointment. A short accurate list beats a long stale one.
The measure that matters is time from cancellation to filled, and most practices can see it drop in the first fortnight.
Clone it, invite the desk team, and the waitlist is yours. The ranking rules, the offer wording, and the acceptance window are all things you set and change.
Where to go next: browse the Community Gallery for scheduling apps other practices publish, read schedule automations for recurring sweeps of the list, or open create to build from your own description. This pairs with no show recovery when the gap was not a cancellation, and with provider schedule coordination when the freed slot needs a room as well as a person.
Frequently Asked Questions
How does the app decide who to offer a slot to first?
By the criteria you describe: how well their stated availability matches the gap, which provider they need, how long they have been waiting, and how urgent they marked the request. The reasoning is visible on the card, so you can override any ranking with one click.
Can we offer to several people at once?
Yes, and most practices do. Set a first-to-accept rule so the slot closes on the first yes and the others receive a short note that it has gone. The offer log keeps the whole thing honest.
What stops a slot from being double booked?
The acceptance writes back to the appointment record and closes the offer immediately. Anyone else who replies afterwards sees a closed state, and the automation sends the polite decline rather than a person having to.
How do people join the waitlist?
Through a short form you can send by link or embed on your site. It asks for the same fields the ranking uses: provider, acceptable days and times, and how soon they want to move. See build a form with logic for the branching version.
Does it work for multiple providers or locations?
Yes. Each waitlist entry records which providers and which locations are acceptable, so a gap in one diary only surfaces the people who could actually take it.
Can we see how well the waitlist performs?
Yes. The table shows offers sent, acceptance rate, and average time from cancellation to filled. That is usually the first number a practice manager wants once the process is running.
Is any of this deciding clinical priority?
No. The ranking is administrative: availability, provider preference, and how long someone has been waiting. Any clinical prioritisation is set by your practice and entered as a field the app simply respects.
