bookings
A Cancellation Policy That Holds Up
Most cancellation policies fail at the moment they matter, because the customer never saw them at a point where seeing them meant anything.
A cancellation policy is not a paragraph. It is a sequence of moments where a customer either did or did not understand what they were agreeing to, and the paragraph is only the last of them.
Policies fail for one reason above all others: the customer genuinely did not know. Not as an excuse. As a fact, because the policy lived in a terms page nobody opened, and the first time they encountered it was when they were being charged under it.
Where the policy has to appear
Three places, and the first two matter more than the third.
At the point of booking, in the flow, as a sentence. Not a link. Not a checkbox next to "I agree to the terms". One line, above the button, in the words a person uses: free to move or cancel up to 24 hours before, after that the deposit is kept.
In the confirmation. The same sentence, in the email or message that lands immediately. This is the version the customer can find later, and a policy that cannot be found later is not enforceable in any practical sense regardless of its legal status.
In the terms. Where the full version lives. This is for completeness, not for communication, and treating it as the primary location is the mistake.
A policy that appears in all three, in the same words, is one you can enforce without an argument. A policy that appears only in the third is one you will choose not to enforce, repeatedly, because enforcing it feels unfair, which means you do not have a policy at all.
Make the cut-off a time, not a feeling
"Reasonable notice" and "sufficient notice" are not policies. They are invitations to negotiate at the worst possible moment.
A cut-off needs a number and a unit: 24 hours, 48 hours, noon the day before. The customer should be able to compute whether they are inside it without asking you.
Attaching it to the appointment time rather than to a calendar day avoids the second argument. "The day before" is ambiguous for an 8am slot. "24 hours before the appointment" is not.
And it needs exactly one tier, or at most two. Policies with four bands of escalating charges are not read, not remembered, and not applied consistently.
Say what happens, in money
The useful policy states an outcome, not a principle.
"Cancellations within 24 hours may incur a fee" tells the customer nothing they can act on. Does it? How much? Who decides?
"Cancel or move up to 24 hours before at no charge. Inside 24 hours the $75 deposit is kept." is a sentence the customer can make a decision against, which is the entire function of a policy.
The rule that overrides your policy
For sales made at the customer's home, your cancellation terms are not the whole story.
The FTC's cooling-off rule at 16 CFR 429.1 generally gives a buyer three business days to cancel a qualifying sale made at their residence, and obliges the seller to provide a dated copy of the contract and a cancellation form stating that right. The rule has thresholds and exemptions, and many states layer their own requirements on top, frequently longer periods for particular trades. The FTC publishes the rule and a plain-language summary.
What that means operationally is simple: a contract term cannot sign away a statutory cancellation right, and a policy written as though it can is a policy that will fail the one time it is tested. The booking flow and the in-home sale are different moments with different rules, and software that treats them identically will get one of them wrong.
Enforce it in the customer's favour at the margin
The last part is a judgment rather than a rule, and it is the one that separates a policy that works from one that generates complaints.
Enforce the policy. Having one you waive on request trains everybody to request.
But when the call is close, decide for the customer. Twenty-five hours and ten minutes is outside the cut-off. The person who cancels at twenty-three hours fifty because their child is ill is inside it, and charging them is correct, legal, and costs more in the long run than the deposit is worth.
The way to make that sustainable rather than arbitrary is to write down what you did and why, on the record, every time. Discretion that is recorded is consistent over a year. Discretion that is remembered is whatever mood the office was in.
What the system has to do
Four things, and a booking tool that does not do them is making a policy you cannot run.
Show the policy in the flow, from a single source, so changing it changes everywhere it appears.
Timestamp the agreement: what the customer saw, when, and that they proceeded.
Compute the cut-off per booking, in the customer's local time, and show them whether they are inside it when they open the cancellation link.
Record every cancellation with who initiated it, when, and what was charged. That record is the entire defence against a chargeback, and it is three fields.