A patient cancels a 2 PM crown prep at 9:40 in the morning. Your front desk is on the phone with someone else, then lunch happens, then the afternoon runs long. By the time anyone looks at the gap, it's 1:50 and nobody's filling it. That chair sits empty. At a dental group doing maybe $400 to $600 of production per operatory-hour, a dead afternoon slot is real money gone, and it happens three or four times a week at most practices I've talked to.
The fix isn't a better front desk. It's a flow that texts the next person on your waitlist within minutes of the cancel, lets them claim the slot by replying, and books the first one who says yes. No phone tag. The hard part isn't the automation, it's keeping that text on the right side of the line between an appointment message and marketing. I'll walk through both.
Full disclosure: I work for Ready, an SMS platform. I'll show how we handle the two-way reply parsing, but the flow logic matters whether you use us or not.
Why the first 10 minutes decide whether the slot fills
Opted-in patients tend to read a text within a few minutes, industry chatter puts SMS open times in the 3-minute range versus days for a portal message or email. That speed is the entire advantage. A canceled slot has a short shelf life: offer it fast and people can rearrange their day; offer it at 4 PM for a slot that was at 2 PM and you've missed the window.
So the design goal is: cancel detected → waitlist contacted → slot claimed, all inside roughly 10 minutes, with zero staff action required. The only way that works is if replies get parsed automatically and the booking locks to the first valid "yes."
The flow, step by step
Here's the backfill logic. I'll describe it as a GHL workflow because that's what most clinics I see run, but the shape is the same anywhere.
- Trigger. An appointment status flips to Canceled or Cancelled for a slot inside, say, the next 72 hours. (Cancels further out, you don't need to rush.)
- Pull the waitlist. Query contacts tagged
waitlistwho match the slot, same provider, same visit type, within quiet hours for their timezone. Order them however you prioritize: longest-waiting first, or by urgency flag. - Offer in small batches, not all at once. Text the top 3 to 5, not the whole list. If you blast 40 people and 12 reply yes, 11 of them get a "sorry, taken" and a bad taste. Batch of 3, wait 7 to 8 minutes, then the next 3 if nobody claimed.
- Reply-to-claim. The patient texts back
YES(orY, or "yes please", more on parsing below). First valid claim wins. - Lock and confirm. Book the slot, send a confirmation, and send the other batch members a "that one's filled, you're still on the list" note so they're not left hanging.
- No claim? After the batch exhausts, fall back to the front desk with a task, now it's a known gap, not a surprise at 1:50.
The offer message
Keep it short, specific, and claimable:
Hi Dana, a 2:00 PM slot opened today with Dr. Lee. Reply YES to take it and we'll lock it in. First reply gets it. Reply STOP to opt out.
One segment if you keep it tight (160 GSM-7 characters). No emoji, an emoji drops you to 70 characters per segment and you'll spill into a second segment for nothing. On Standard that's $0.02 plus a $0.0045 carrier fee per segment, so a batch of 5 is about a dime. Even filling one extra crown prep a month pays for the texting line for a decade.
The consent line that keeps this a reminder, not marketing
This is where clinics quietly cross a line. A text about an appointment the patient asked to be waitlisted for is a treatment/transactional message. A text that says "we had a cancellation, also, ask us about Invisalign this spring!" is marketing, and marketing requires a separate, explicit opt-in. Staple an offer onto a reminder and you've changed its consent category without changing the patient's permission.
The safe version of the waitlist text does exactly one thing: offers the slot the patient already requested. No promos, no upsell, no "while you're in, consider…". The moment you add an offer the patient didn't ask for, you need marketing consent. We dug into this exact boundary in the one sentence that flips your consent requirement and the broader recall-vs-marketing consent line, both worth reading before you write any template.
Two practical guardrails:
- Capture waitlist consent at sign-up. When a patient asks to be on the waitlist, record it: "Text me if an earlier slot opens." That attestation is your audit trail. Ready logs opt-in attestation on bulk and API sends for this reason.
- Keep the message body clean of PHI. "A 2:00 slot opened with Dr. Lee" is fine. Naming the procedure, diagnosis, or anything clinical in the body is a separate problem, see the 4 fields to never include.
Reply parsing: why "yeah" shouldn't lose the slot
The flow lives or dies on reading replies correctly. If your automation only books on an exact YES, then "yeah," "yes pls," "I'll take it," and "👍" all fall through as no-response, and the slot stays empty while the patient thinks they claimed it.
Build the match to accept the obvious variants:
| Patient types | Should the flow book it? |
|---|---|
| YES / Y / yes | Yes |
| yeah / yep / sure / ok | Yes, accept natural affirmatives |
| "I'll take it" | Yes |
| 👍 | Yes (with a confirm-back) |
| MAYBE / "what time?" | No, route to staff, it's a question |
| STOP | No, opt out, honor immediately |
Ready's two-way inbox lands every reply in-app (and in GHL for connected accounts), and you can pair that with keyword routing so affirmatives book, questions escalate to a human, and STOP opts out, all without someone watching the screen. We covered the affirmative-parsing problem in depth in why 'yeah' instead of 'C' books as a no-response, and the routing structure in building a keyword routing tree.
STOP is non-negotiable and automatic, inbound STOP is honored and propagates across campaigns so an opted-out patient can't be contacted again. Quiet-hours enforcement also matters here: if your cancel fires at 8:10 PM, a patient in an earlier timezone shouldn't get pinged. Ready holds those sends based on the recipient's local hours. The multi-timezone quiet-hours trap post explains why batch sends go wrong across zones.
The race condition nobody tests for
Here's the bug that bites every DIY version: two patients reply YES within the same 30 seconds, and both get booked, and now you've double-booked a single slot and have to call one back to un-invite them. Worse than an empty chair.
Guard against it:
- Set a claimed flag the instant the first valid YES lands, before you send the confirmation. Subsequent YES replies hit the flag and get the "sorry, just filled" message instead.
- Keep batches small (3 to 5) so the window for a collision is tiny.
- Confirm back every time. The first-replier gets "You're booked for 2:00 with Dr. Lee", never leave a YES unacknowledged.
And while you're auditing: double-texting is the other common failure, where a contact gets the offer twice because two workflows fire. If you run GHL, the 4 workflow mistakes that double-text your contacts is a 20-minute audit worth doing before you turn this live.
What it actually costs to run
Say you fill one otherwise-dead slot a week. The texting cost: a batch of 5 offers plus a couple of confirmations is roughly 7 segments, about $0.17 all-in on Standard. Over a month that's under a dollar in SMS to recover four slots. If each recovered slot is worth even $200 in production, the flow pays for itself hundreds of times over. The real investment is the hour it takes to build the workflow and write the templates correctly, not the per-message cost. You can sanity-check your own numbers on the cost calculator.
The practical takeaway
A canceled slot is a 10-minute problem, not a 3-day one, but only if the offer goes out automatically, reads the reply loosely enough to catch "yeah," and locks to the first claim without double-booking. The compliance piece is simpler than it sounds: offer the slot the patient already asked for, keep marketing out of the body, log the waitlist opt-in, and let STOP and quiet-hours run on autopilot.
If you want to see how the two-way inbox and reply routing handle the claim logic, the features page walks through it, and self-serve 10DLC registration gets you approved in most cases within 1 to 3 days so you're not waiting weeks to flip this on. Start with one visit type and one provider's waitlist, prove it fills a slot, then expand.