Refunding a coaching call: the slot, the calendar and the money

Sunday evening, and someone who has paid for Tuesday's ninety-minute session writes to say their week has fallen apart and they cannot make it. You want to be decent about it. But three separate things are now attached to that Tuesday: a payment, a calendar entry with a Meet link on it, and a slot that other people cannot book while it sits there. Refund the money and forget the other two, and you will spend Tuesday morning staring at a call nobody is coming to, on a day you could have sold twice.

Why a call refund is harder than a product refund

When you refund a digital file you lose the money. When you refund a call you lose the money and the hour, and the hour is the part that does not come back. You held Tuesday at two o'clock for a fortnight. You turned down other work around it, or at least did not go looking for any. The refund request arrives at the point where that hour has already cost you something, and no policy makes that feeling entirely go away.

The genuinely awkward cases are the near-misses. Twelve hours' notice from someone whose child is ill is not the same as twelve hours' notice from someone who forgot, but they arrive in the same inbox, look identical from the outside, and you have to decide with incomplete information while you are doing something else.

The mechanical part, at least, can be made reliable. Bookings on store.fan sync with Google Calendar on paid plans and carry a Google Meet link, so the call exists in the same place as the rest of your week rather than in a scheduling tool you check once a day. That is what makes the sequence below possible: everything you need to change is somewhere you already look.

Calls held together by DMs, and calls held by a system

Most coaches start by arranging calls in messages and taking payment separately. It works until the volume rises, and then it fails in a specific way: the money and the time drift apart. Somebody has paid and is not in the calendar, or somebody is in the calendar and has not paid.

The order of operations

The rule underneath all of this is simple. Deal with the calendar before you deal with the card, because a slot you have freed can always be re-held, and money you have already sent back cannot be un-sent.

1. 1Reply within a few hours, even if the reply is only that you have seen it and will sort it out today. Silence is what turns a cancellation into a dispute.
2. 2Offer a reschedule first, with two specific times. Most people asking for a refund on a call actually want a different day, and a named alternative gets accepted far more often than an open invitation to pick something.
3. 3If it really is a cancellation, open the booking order in your store.fan dashboard and check what you are looking at: which product, which price, which date and time.
4. 4Cancel the booking so the slot stops being held. This is the step that clears the Tuesday and lets someone else take it.
5. 5Confirm the calendar entry and its Meet link have gone from your Google Calendar, so no reminder fires at ten to two.
6. 6Now issue the refund in your own Stripe dashboard, full or partial according to the policy you published.
7. 7Send one closing message: cancelled, refunded, the amount, and a line inviting them to book again when things settle.
8. 8Add a note to their customer record. Someone who has cancelled twice is not a villain, but they are information for the next time you are deciding whether to hold a slot for them.

The reschedule-first habit

If you do only one thing from this article, make it this. A reschedule keeps the money, keeps the relationship, and costs you a few minutes of diary shuffling. A refund costs the whole booking. Putting "one free reschedule with at least 24 hours' notice" into your booking description is not stinginess, it is a way of telling people what to ask for. Most of them will ask for it.

A fortnight of Tuesdays

Suppose you sell a ninety-minute strategy call at $180 and you open six slots a fortnight. Over three months, that is thirty-six slots. Say two people cancel outright and four ask to move. Handled with a reschedule-first policy, you keep the four, refund the two, and end up having sold thirty-four of thirty-six hours. Handled by refunding everyone who asks, you keep thirty and have six empty hours you were not paid for and could not resell because you found out too late.

The difference is not toughness. It is timing. A slot freed on Sunday night can be booked by someone else on Monday, especially if that person has already been on your customer list waiting for an opening. A slot freed on Tuesday at half past one cannot be booked by anyone.

The mistake most people make

The usual mistake is doing it in the wrong order: refunding immediately because that is the part that feels urgent, then getting distracted before the calendar is touched. The money is gone, the slot is still held, and nobody can book it. A week later you notice a ghost entry on a Tuesday and cannot remember whether that person was refunded or not. Money first is the natural instinct and the wrong one. Calendar, then card, then message.

Nobody enjoys cancelling a call they were looking forward to. But an hour returned to your diary on Sunday night is worth considerably more than an hour discovered empty on Tuesday afternoon, and the only thing standing between those two outcomes is the order you do things in. If you want to see how bookings, order forms and calendar sync fit together before committing to anything, the features overview and the FAQ cover it plainly.