A cancellation and reschedule policy for paid calls you can reuse
Write it once, put it on the product page, and stop making the same decision from scratch at nine o'clock on a Sunday evening.

The message comes in at 21:40 on a Sunday. Something has come up, they are very sorry, can they move tomorrow's call. You have now been asked this eleven times this year and you have answered it eleven slightly different ways, depending on how much you liked the person and how tired you were. That inconsistency is not kindness. It is the reason the same message keeps producing a twenty-minute internal debate.
Why this is harder than it should be
The awkwardness is not really about money. It is about being asked to price a stranger's bad week. If you hold the fee you feel mercenary, and if you refund it you have just worked for free and taught the next person that the window is negotiable. Neither option feels good in the moment, which is exactly why the decision should not be made in the moment.
There is also a fairness problem. If you waive the fee for the person who wrote a warm apology and hold it for the person who wrote two blunt lines, you are charging for tone. Over a year that becomes a genuinely unfair system, and it is invisible to you because you only ever see one case at a time.
The last difficulty is that a policy nobody read is not a policy. Buried in a paragraph halfway down a product page, it will be discovered for the first time in the middle of the argument it was meant to prevent. Placement matters as much as wording.
Case by case, against written down
The same eleven messages, handled two ways.
| Deciding each time | A written policy on the product page |
|---|---|
| Twenty minutes of deliberation per request | A four-line reply you paste and send |
| Different answers for similar situations | The same answer every time, which is easier to defend |
| The buyer finds out the rule during the disagreement | The buyer read it before paying and acknowledged it at checkout |
| You feel like the villain for holding a fee | The policy holds the fee; you are just applying it |
| Requests arrive scattered across email, DMs and comments | Requests arrive in your dashboard messages, next to the booking |
| Generosity looks like inconsistency | Generosity is a deliberate exception to a stated rule |
The policy, in six lines
Short enough that people actually read it. Adjust the numbers to your own practice, keep the plain wording, and resist the temptation to add clauses for every edge case you can imagine. All of it lives in the description and the order form of the call you are selling.
- 1Notice window: "You can reschedule up to 24 hours before the call." Pick a number that gives you a realistic chance of reselling the slot.
- 2How to do it: "Message me through your order page and I will send new times." One route, stated once.
- 3Inside the window: "Cancellations inside 24 hours are non-refundable, but I will always try to move you once." One free move is the clause that prevents almost every argument.
- 4No-shows: "If you do not attend and have not been in touch, the session is treated as delivered." Say it plainly rather than implying it.
- 5If I cancel: "If I have to move a call, you choose a new time or take a full refund." This is the line that makes the rest of it fair.
- 6Serious circumstances: "Illness and emergencies are handled like adults. Tell me and we will sort it." Leave yourself the human exception, in writing.
Where to put it
- In the product description, above the fold, in its own short block rather than inside a paragraph about outcomes.
- As an order-form question at checkout: a multiple choice with a single option, "I have read the reschedule policy". It takes the buyer a second and removes an entire category of dispute.
- In your reply template, so the wording the buyer sees afterwards is word for word the wording they agreed to.
What changes in a normal month
Say you run twenty paid calls a month and three people ask to move. Before the policy, that is three separate deliberations, three differently worded replies and at least one you regret. Perhaps one of the three quietly disappears rather than rebooking, because nobody told them what happens next and silence felt easier than asking.
With the policy in place, the same three requests take about two minutes each. Two of them rebook inside the window without any decision from you at all, and the third arrives at eleven the night before and gets the one free move. You have not made more money in any dramatic way. You have removed a recurring evening argument with yourself, and the person who would have vanished is now on the calendar next Tuesday and stays in your customer list as someone who might buy again.
Write the policy into your product page before you sell the first call rather than after the eleventh message.
Create a bookingThe mistake most people make
They write a strict policy to feel protected and then never enforce it, which is the worst of both worlds: the page reads as cold to every prospective buyer, and the actual behaviour is still whatever you feel like on the night. Write the policy you will genuinely apply, even if it is softer than you think it should be. A generous rule you keep is worth more than a strict one you abandon, because the thing buyers are really judging is whether you are predictable. That is the same reason it belongs on the product page rather than in the FAQ where nobody looks until it is too late.
Long enough to have a realistic chance of reselling the slot, which for most people is 24 or 48 hours. Anything longer starts to feel punitive for a single call.
One, yes. It is the clause that keeps the relationship intact and it costs you almost nothing, because the person still turns up and you still get paid. Two free moves in a row is a different conversation.
In your dashboard messages, alongside the booking, and on the iOS app if you handle things from your phone. Keeping the whole thread in one place is what makes the two-minute reply possible.
The payment is in your Stripe account and disputes are handled there. An acknowledged policy captured at checkout, plus a short factual message thread, is exactly the kind of record that helps.
Write the six lines this afternoon. Put them on the product page, add the one-tick order-form question, and save the reply somewhere you can find it. The next Sunday message will take two minutes and cost you nothing at all, which is the only real point of having a policy in the first place.
Bookings, order-form questions and messages all sit behind one link at store.fan/you.
Set yours upTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



