By NUMUS editorial team
A coaching customer asks to cancel, but the request reaches several people: support reads the message, a program owner reviews the circumstances, someone handles the payment, and a coach still has a session on the calendar. The customer needs one clear answer about what happens next.
A useful coaching cancellation refund process checklist connects those responsibilities. Give each request a case owner who follows it through the decision, payment action, remaining service commitments and customer update. A handoff is complete when the next person accepts a defined task and returns its result.
This workflow helps your team carry out a decision. It does not determine refund entitlements or replace review of applicable terms and requirements. For the broader program and payment description, start with coaching merchant account preparation.
Capture what the customer is asking to change
Record the request time, program, enrollment reference and relevant payment. Preserve the customer's message and identify whether they want to stop future sessions, end renewing access, request money back, or resolve a delivery problem. A request can cover several of these at once.
Ask only for information needed to identify and handle the case. If the message already clearly requests cancellation, recording it should not depend on the customer explaining their personal circumstances. Keep confidential coaching discussions out of the payment handoff.
Send an acknowledgment naming the case owner and the next update your team can meet. Distinguish receipt of the request from a completed cancellation or refund. Give the owner a backup so an absent staff member does not leave the request unattended.
Turn the policy question into a decision someone can make
Attach the enrollment terms and policy version presented at purchase, the relevant offer description, and a short delivery summary. Identify the question that needs an answer: for example, how an already agreed make-up session affects this particular request.
Stripe's website checklist calls for clear customer contact information and refund and cancellation policies. That supports making the process understandable before purchase; it does not decide any individual customer's rights. Stripe website checklist
Assign unresolved contract or entitlement questions to the appropriate authorized reviewer. Record the question, owner and next check. Internal review should not become an extra customer requirement or postpone an action that must already be taken. A policy label alone is not a substitute for resolving an ambiguity or considering applicable requirements.
Write the authorized decision as separate instructions
The reviewer should return enough detail for another person to act without guessing:
- Program change: what is canceled and its effective date.
- Payment action: approved amount, currency and original payment reference, with any unresolved adjustment clearly identified.
- Future payments: what must happen to any scheduled charges, with a named billing owner.
- Service commitments: sessions, materials, access or support that remain, and their end dates.
- Communication: who will explain the outcome and handle questions.
Keep the authorization and its basis with the case. If support can make the decision within an established responsibility, record that instead of adding an unnecessary approval layer. Where the answer remains unresolved, say what is still being checked rather than inventing a final outcome.
Bring this responsibility map to a conversation about coaching payment processing, along with your program outline and the tools your team uses.
Return a payment result to the case owner
The payment operator checks the original transaction and existing refund activity, carries out the authorized action through the appropriate provider, and returns the reference, amount, currency and observed status. An unclear response needs investigation before anyone submits another refund.
Stripe, for example, documents pending and failed refunds as well as refund requests. Its guidance also describes reference numbers that may help trace a card refund. Use your actual provider's status and instructions when explaining progress or following up. Stripe refund documentation
If the request affects recurring billing, assign the detailed checks in subscription cancellation and refund reconciliation to the billing owner. The support case still needs the result, but it need not duplicate that financial worksheet.
Check what the program still owes the customer
Send the service instructions to the coach or program administrator. Confirm which appointments change, whether any make-up session remains, and what happens to course materials and support access. Have that person acknowledge the instructions and report what was actually updated.
For a renewing program, the coaching membership billing and access workflow helps assign the access checks across the tools your members use.
In Thinkific's documented Thinkific Payments workflow, issuing a refund leaves the student with product access; unenrollment is a separate action. That is one product example of why the service decision deserves its own handoff. Stripe and Thinkific documentation here illustrates named products, not an offered NUMUS integration. Confirm how your own tools behave. Thinkific payment and access guidance
Use coaching service-delivery records to connect the case to the relevant attendance, rescheduling and access events. Record enough to explain the remaining commitment without copying private coaching notes into every system.
Fictional worked refund handoff ledger
Harborline Coaching is an invented business. A customer paid $1,200 USD upfront for six sessions. Two happened; session three was moved to September 24. The customer now asks to cancel sessions four through six and receive a partial refund while keeping the make-up session.
Every identifier, date, amount and decision below is fictional. The approved $350 refund illustrates a recorded decision, not a per-session calculation, recommended policy or refund entitlement.
| Handoff | Owner and record | Result passed to the next person |
|---|---|---|
| Request received | Support opens case C-042 on September 19 and links enrollment E-042 and payment P-042 | Customer request acknowledged; support owns the next update on September 21 |
| Policy or contract question | Program owner reviews the enrollment terms and rescheduled session record | Confirms the decision must address the make-up session separately from the canceled sessions |
| Authorized decision | Authorized program owner records decision D-042 | Approves $350 USD refund; cancels sessions four through six; retains September 24 make-up session and workbook access through September 30; confirms no further payments are scheduled |
| Provider action | Payment operator checks P-042 and submits the approved refund | Refund R-042 is recorded as pending; operator owns the next provider check on September 21 |
| Remaining service | Coach and program administrator confirm their updates | Canceled appointments removed; make-up appointment retained; agreed workbook access preserved |
| Customer update | Support sends the confirmed program changes and observed payment status | Customer receives one explanation; pending refund remains assigned instead of disappearing into a closed case |
The example stops with an open payment task. A later result should be added to the same case and communicated as appropriate. None of the example dates promises a provider processing speed.
Give the customer a message that matches the work
For the fictional case, support could say:
We have canceled sessions four through six. Your September 24 make-up session remains booked, and your workbook access continues through September 30. We submitted the approved $350 USD refund; the provider currently shows it as pending. We will update you on September 21. Please reply here with any questions about this request.
Use the provider's current guidance for any refund timing explanation. Do not say money has reached the customer when your evidence shows only submission or a processing status.
Your coaching cancellation refund process checklist
Before closing the support work, confirm:
- The recorded request and decision address the same program and payment.
- Every policy question has a decision or an assigned follow-up.
- Payment and future-charge instructions have an owner and a recorded result.
- Remaining sessions, access and support match the documented decision.
- The customer received an accurate update and a usable reply channel.
- Every pending item has a next check, responsible person and backup.
Bring a completed example of your handoffs to NUMUS when discussing your coaching payment journey. It helps explain how the processing relationship fits your program's support and delivery work.