No-show and deposit policy
The client is on the phone. “I had no idea there was a fee.” She did. The policy is on your site, in the confirmation email, and in the terms link. You have proof and you still do not want to have this conversation. You want the machine to have it.
A policy that reads like a legal notice, hides in the confirmation email, or gets enforced by a person who does not want the conflict tends to produce pushback. A policy that is short, obvious, and mechanical is the version worth testing.
By Ray Williams, Founder, RAWTech
Published · Updated
Ray Williams builds booking, payment, reminder, review, and rebooking systems for owner-operated service businesses.
the short answer
A no-show policy holds up when the deposit is small enough to feel fair, the notice window is a round number, the refund and reschedule paths are self-service, and the charge is enforced by the booking tool rather than by you. Write it in five clauses, show it three times before the customer books, and let the software apply it every time.
Operational guidance, not legal advice. Adapt the policy to your jurisdiction, payment processor, booking platform, and business model.
Pick a deposit that is fair, not punitive
A deposit is a commitment device, not a fee. Too small and it does nothing. Too large and you scare off customers who would have shown up and tipped.
As a starting point to test, try 15 to 25 percent of the ticket, or a flat 25 to 75 dollars. For high-prep or high-cost services, some businesses start in the 25 to 50 percent range. Your numbers will differ, so treat these as inputs to adjust rather than rules.
The deposit is credited toward the service. Say that on every screen the customer sees, then count questions, complaints, and abandoned bookings against your recorded baseline.
Deposit or cancellation fee: pick one mechanism
Both mechanisms protect the slot, but they behave differently at checkout, in disputes, and in customer perception. Choose the one your booking tool and processor can actually enforce, then write the policy around it.
| Question | Deposit at booking | Cancellation fee on a stored card |
|---|---|---|
| When money moves | Charged when the appointment is created | Charged only after a late cancel or no-show |
| Customer perception | Reads as part of the price when it is credited to the service | Reads as a penalty, so wording and notice matter more |
| Enforcement | Automatic. The booking cannot be created without it | Depends on the card still being valid and the rule firing on time |
| Best fit | High-demand slots, high-prep services, new customers | Repeat customers and services where an upfront charge kills bookings |
| Main risk | Some price-sensitive customers abandon the booking | Failed cards, disputes, and manual follow-up |
Confirm which mechanism your booking platform and payment processor support before you publish the policy. Capability differs by tool and by plan.
How deposits work inside a booking flowFailed card at booking time
Fill-in policy template
Replace each bracket with your own value and publish the result as-is. Five clauses, plain sentences, no legal voice.
Avoid penalty, forfeit, and non-refundable in customer-facing copy. Keep that wording for the terms link.
- Deposit: “A [amount or percent] deposit holds your appointment and applies to your service.”
- Notice: “Reschedule or cancel up to [24 / 48] hours before your appointment.”
- Refund: “Cancel inside that window and your deposit refunds automatically. Cancel later and the deposit is kept.”
- Late arrival: “Arriving more than [10 / 15] minutes late may shorten the service or require a new appointment.”
- No-show: “If you do not arrive and did not cancel, the deposit is kept and the slot is released.”
- Exceptions: “Emergencies happen. Reply to your confirmation and we will look at it case by case.”
- Enforcement: “These steps run automatically through our booking system.”
Show the policy three times
Once is not enough. A policy that appears only in a terms link is a policy the client will sincerely say she never saw.
Put it on the booking page above the pay button. Put it in the confirmation email in the first three lines. Put it in the reminder text in one short sentence.
Enforce it automatically or do not enforce it
The most common failure is a policy that exists on the site but not in the booking tool. If enforcement depends on you remembering to charge a card at 6pm on a Friday, some of the time you will not, and clients learn the policy is negotiable.
Configure the tool to take the deposit at booking, keep it automatically on a same-day cancel or no-show, and refund automatically inside the window. Pair the deposit with a 24-hour and 2-hour reminder that includes a one-tap reschedule link, so customers move the slot before the window closes. Once the software does it, the policy is real.
Refund windows that hold upHandling deposit disputesInstalled version: automated reminders and deposit policy
Rollout checklist
Work top to bottom. Each line is a thing you can verify in one sitting.
Recovery wording for the customers who still miss lives in the recovery templates guide, not here.
No-show recovery email templates
- Write the five clauses using the template above.
- Confirm your booking tool can take the deposit and apply the rule without manual work.
- Publish the policy above the pay button, in the confirmation, and in the reminder.
- Capture timestamped acceptance at checkout and show the policy on the receipt.
- Record your current no-show and late-cancel counts before launch so you have a baseline.
- Tell existing customers once, in plain language, before the rule starts.
- Review the counts after 30 days and adjust the deposit or the window, not both at once.
Frequently asked questions
start here
Confirm where the policy is actually breaking.
The Loop Audit reviews your records and a test booking, then names the seam and what to change first.