Policy and response
Salon no-show policy: what to say and do
A policy is useful only when your team can apply it calmly in the moment. The goal is consistency—not a longer paragraph on the booking page.
GET THE RECOVER SYSTEM — $19Start here
Make the policy clear, then separate enforcement from recovery
State the cancellation window, what happens after a missed appointment, and how a client can reschedule. Keep the language factual and make sure staff know where the policy applies before a booking is at risk.
When a no-show happens, first classify the situation. A genuine emergency, a first missed appointment, and a repeated pattern may need different treatment. After that decision, run the recovery workflow for the lost capacity and follow-up.
Immediate workflow
What to do next
- 01
Write the minimum clear policy
Define your notice window, the action for a missed appointment, and any deposit or rebooking requirement. Avoid vague language staff cannot apply consistently.
- 02
Classify the situation before responding
Check client history, appointment value, timing, and the stated reason. This keeps a first exception from being treated like a chronic pattern—or vice versa.
- 03
Send the policy-aligned response
Acknowledge the missed appointment, state the next available action, and only mention the relevant policy step. Keep the recovery offer and enforcement decision distinct.
- 04
Log the event and review repeat behavior
Record the reason, action taken, and rebooking result. Weekly review reveals whether your policy is working or where staff need a clearer route.
The operational gap
A written policy does not handle exceptions or empty chairs
The policy tells a client what you generally expect. It does not decide how to respond to an emergency, a high-value regular, silence after a no-show, or an open slot that needs filling now. Those moments need operating rules and follow-up paths.
BOOKED RECOVER is a ready-to-run appointment recovery operating system: choose the route, send the appropriate message, follow the response branch, log the event, and review the pattern weekly.
What RECOVER handles
More than a script for one awkward moment
Decision routes for value, timing, and repeat behavior
Message workflows with follow-up and response branches
Empty-slot and waitlist actions when capacity is already lost
Tracker, calculator, and weekly review for the next decision
Related guides