AddThisFeature

Cancellation Waitlist

Offer a freed-up slot to the people waiting for it, in order.

moderate Engagement

What it adds

A per-slot queue that automatically offers a released booking to waiting people one at a time.

What your agent is told to do

5
  1. 1

    Let someone join the queue from the same screen where they found the slot full, capturing only what a booking needs, and confirm their position back to them.

  2. 2

    When a booking is cancelled or released, offer the slot to the first person in the queue with a stated claim deadline, and move to the next person only when that deadline passes or the offer is declined.

  3. 3

    Hold the slot for the person holding the live offer. If the slot stays openly bookable during the offer window, the queue means nothing and whoever refreshes fastest wins.

  4. 4

    If the app already has a Waitlist feature for signup or capacity, extend it with slot-level queues and offer expiry rather than building a second waiting-list concept with its own table and its own notification path.

  5. 5

    Do not notify everyone in the queue at once and let them race. It generates a burst of disappointment for everyone but one person and trains people to ignore the notification.

Edge cases it handles

8
  • Every offer carries a claim deadline, and the slot moves to the next person automatically when it lapses. Without a deadline one unresponsive person blocks the queue until the appointment has passed.
  • Two people must never claim the same released slot. Claim under a lock or a conditional update so the second claim loses cleanly and returns the person to their place in the queue.
  • Entries whose slot has already started must be dropped rather than offered, and the person told the queue has closed for that time.
  • Cap how many offers one person receives in a period. Someone waiting on a busy calendar can otherwise be notified repeatedly through the night.
  • Every notification must carry a one-tap way to leave the queue that works without signing in, and leaving must take effect before the next offer is generated.
  • A person holding a live offer who cancels their own place must release the slot immediately rather than letting the deadline run down.
  • Respect the app's Quiet Hours if it has them, and decide explicitly whether a short claim deadline overrides them or the offer skips to the next person.
  • Someone who books the slot through the normal flow while an offer is outstanding must be blocked, not silently allowed to jump the queue.

Definition of done

9
  • People can join a waitlist for a full slot and see their position.
  • A cancellation offers the slot to the first waiting person with a visible claim deadline.
  • The slot is held for the duration of an offer and cannot be booked around it.
  • Concurrent claims on one released slot resolve to a single booking.
  • Entries for slots that have started are dropped rather than offered.
  • Offer notifications are rate limited per person and each carries a working leave-the-queue action.
  • The feature extends the app's existing waitlist rather than duplicating it.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.