Cancellation and waitlist recovery
A medical spa with two treatment rooms. At 6:48 PM, a client cancels tomorrow morning's 90-minute laser session. The practice is closed, the provider's morning is now empty, and by the time anyone would normally see the message, the best chance to refill the slot has passed. Empty chair time is the most expensive kind of quiet.
What does this demonstration show?
This demonstration shows a late cancellation at a med spa turning back into booked treatment time. Deptly rebooks the cancelling client first, offers the open slot only to waitlisted clients already cleared for that treatment, confirms the first yes, and sends the practice's standard prep instructions. Anything involving fees, exceptions, or clinical judgment goes to a human — and the annotations show exactly where.
The workflow, step by step
Real product behavior with example names and details. The notes beside each step explain what is happening — including where Deptly asks instead of acting.
6:48 PM
Client
So sorry — I have to cancel tomorrow's 10:00 laser session. Something came up at work.
A cancellation inside 24 hours is a trigger. Deptly starts the recovery workflow immediately instead of letting the message sit unread until morning — the hours right after a cancellation are when the slot is easiest to refill.
2 minutes later
Deptly
No problem at all — these things happen. Want me to move you to the same time next week so you keep your spot?
The cancelling client is rebooked first. That protects the relationship and the future schedule — a cancellation handled warmly usually stays a client; one met with silence often doesn't come back. Any question about the practice's late-cancellation fee would be stated from policy but applied or waived only by a human.
10 minutes later
Client
Next week same time would be perfect, thank you!
The client is rebooked into a real opening in the practice's scheduling system. One loop closed; the empty slot is the remaining one.
6:59 PM
Deptly
Hi — a 10:00 AM opening for tomorrow just came up for your laser session. Would you like it? First to confirm gets the spot.
The offer goes only to waitlisted clients the practitioner has already cleared for this specific treatment. Deptly checks eligibility notes before offering — a laser slot can't go to someone still due for a consultation. Who is clinically suitable for what is never Deptly's decision.
7:26 PM
Waitlisted client
Yes! I'll take the 10:00 — been hoping for an earlier spot.
First confirmed reply wins the slot, a rule the owner set. If a second yes had arrived, that client would get a graceful message and first priority on the next opening.
7:28 PM
Deptly
You're confirmed for tomorrow at 10:00 AM. Here are the practice's standard pre-appointment instructions for your session.
The prep instructions are the practice's own existing templates, sent as written. Deptly never composes medical or treatment guidance itself — it delivers what the practitioners have already approved.
7:30 PM
Deptly
Tomorrow's 10:00 cancellation is refilled from the waitlist, and the original client is rebooked for next week. Nothing needs your attention.
The practice manager gets a heads-up, not a task list. Had the cancelling client disputed a fee or asked for an exception, that thread would be waiting here as a question instead.
Friday
DinboxOwner brief
One late cancellation this week: the chair time was refilled from the waitlist the same evening, and the cancelling client kept a booking for next week.
Closure is verified on both sides — the slot has a confirmed, eligible client in it, and the canceller has a future appointment. Both live in the practice's own scheduling system, not in anyone's memory.
What the owner brief says
You don't watch this workflow run. It rolls up into your weekly brief alongside everything else that was handled — what closed on its own, and the few things waiting on you.
A full sample brief lives on the proof and examples page.
Your weekly brief
deptly · weekly summary
- Thursday's 10:00 laser cancellation was refilled from the waitlist within the hour; the cancelling client rebooked for the same time next week.
- The waitlist offer went only to clients cleared for laser treatment — one accepted, and the confirmation and standard prep instructions went out the same evening.
- No fees were applied or waived — the cancellation fell inside your grace window, so there was nothing to escalate.
- The waitlist has grown enough that Tuesday and Thursday mornings now refill reliably; worth discussing whether to open another laser block.
Example — how this workflow appears in your weekly brief
Verified closure
The cancelled slot was refilled the same evening with a confirmed, treatment-cleared client from the waitlist, and the cancelling client left with a rebooked appointment — both closures verified in the practice's own scheduling system.
Closure means the loop is confirmed done — not that a message was merely sent. That standard, and everything behind it, is explained on trust and control.
The boundary this workflow ran inside
The steps above where Deptly asked instead of acting are the point, not a limitation. Every workflow runs within rules you approve — anything outside them waits for you.
Deptly handles
- Routine steps like the ones above — replies, follow-ups, reminders, status updates, scheduling holds
- Logging every action so the weekly brief writes itself
- Chasing the open loop until it verifiably closes
Deptly asks first
- Anything that touches price, scope, or an exception to your rules
- Messages that fall outside the wording you approved
- Situations the rules don't cover — flagged to you, not guessed at
Always human
- Pricing, hiring, and how the work gets done
- Sensitive customer conversations
- Final say on anything Deptly flags
How those rules get set up in your first weeks is on how it works.
See this loop in context
Questions owners ask
If your booking or practice-management software has a waitlist, Deptly works from it. If it doesn't, Deptly maintains a simple approved list of clients who've asked to be contacted about openings. Specific system integrations are examples, not guarantees — what's possible with your exact setup is confirmed during discovery.
It only offers slots to clients your practitioners have already cleared for that specific service, based on the eligibility notes in your system. Whether someone is clinically suitable for a treatment is never Deptly's judgment — if eligibility is unclear, the slot is held and the question goes to your team.
Money decisions always stay human. Deptly can state your written policy when a client asks, but applying a fee, waiving one, or handling a dispute is always escalated to you or your manager with the full conversation attached.
The rule is yours to set. In this demonstration, first confirmed reply wins; the second client receives a gracious message and first priority on the next comparable opening. Deptly tracks that promise so it's actually kept.
It goes straight to your practitioners, and the client is told a qualified person will answer. Deptly recognizes the boundary between scheduling and clinical territory and never answers questions about treatments, suitability, or side effects itself.
Typically pre-approved: rebooking a canceller into open slots and offering openings to the cleared waitlist within your rules. Always escalated: fees, exceptions to policy, anything clinical, and any client conversation that turns into a complaint. You set the boundary and can change it anytime.
Your workflows next
What would this look like in your business?
Answer a few questions about where work waits in your week and get an honest read on which loop Deptly should close first.