A client's payment fails on the 3rd. You see it on the 11th. By the time you sit down to write the message you have drafted it four times in your head, and the awkwardness of having waited eight days is now a bigger problem than the $280.
That delay is the thing to fix. Not the money, and in most cases not the client.
Most late payments are not a client avoiding you
There are two completely different situations that show up in your dashboard as the same red "past due" row, and coaches routinely respond to the first one as if it were the second.
A failed payment is a technical event. The card expired, the client got a new one after a fraud alert, the account was short on the day, or the bank declined an unfamiliar recurring charge. The client almost always does not know it happened. Their card is on file, they have not thought about your invoice since they signed up, and nothing has notified them.
A client avoiding payment is a relationship event. They know. They have gone quiet, they are not logging, and the payment is a symptom of a decision they have already half made.
The tell is not the payment. It is everything around it. A client who trained on Tuesday, logged their food on Wednesday and sent you a form check on Thursday has an expired Visa, not a grievance. A client whose last workout was three weeks ago and whose last message was a thumbs-up has something else going on.
| Failed payment | Avoiding payment | |
|---|---|---|
| Client engagement | Normal — still training, still logging | Dropped off weeks ago |
| Response to a message | Replies quickly, often embarrassed | No reply, or "will sort it out" |
| Cause | Expired card, new card, insufficient funds, bank decline | Money trouble, or they have mentally left |
| What it needs | A card update and 30 seconds of your time | A real conversation |
| Risk of getting it wrong | You damage a good relationship over admin | You spend two months hoping |
Treat every failed payment as the first case until the evidence says otherwise. The cost of being wrong in that direction is one wasted message. The cost of being wrong in the other direction is a client who paid you for fourteen months and got chased like a debtor.
Handle the technical ones automatically, and early
Before you write anything, check whether the payment has already been retried. Card processors attempt a failed charge again on their own schedule, and a decent number of failures clear on the second or third attempt with no involvement from anyone.
So the sequence is: let the retry run, then act. Acting on day zero means messaging clients about payments that were going to succeed on day two anyway.
What you need from your billing system is narrow. You need to be able to see which subscriptions are past due without going looking for them, retry a charge manually once the client says they have fixed the card, and know that the client can update their own card without emailing you a photograph of it. In Fitsly that is the subscriptions list filtered to past due, a Retry payment action on the subscription and on each failed invoice, and a payment methods screen in the client app where they set a new primary card themselves — payments and packages covers the rest of the billing side.
One thing worth checking in your own setup: whether a failed payment notifies you at all. On several platforms it does not — the subscription just shows as past due in a list while the processor retries, and nothing lands in your inbox. That is workable, but only if you actually look. Put a weekly five-minute check on your calendar and the eight-day delay stops happening.
The escalation ladder
Most coaches wait far too long to say anything, and the waiting is what makes it hard. On day two a failed payment is a card problem and the message takes ten seconds to write. On day twenty it is a confrontation, because now you also have to explain your own silence.
Escalate on a schedule you decided in advance, so that none of it is a judgement call made while you feel awkward.
| Day | What you do | What you say | If there is no reply |
|---|---|---|---|
| 0–2 | Nothing. Let the automatic retry run. | — | — |
| 2 | One short message, in the app. No apology, no accusation. | "Hi Sam — heads up, this month's payment didn't go through. Usually it's just an expired card. You can update it under Payment methods in the app. Nothing's changed on your end in the meantime." | Assume they did not see it. |
| 5 | Same message, different channel — email or SMS if you normally use them. | "Sam, the payment's still showing as failed. Can you update the card when you get a chance? Happy to send you a payment link instead if that's easier." | Stop assuming it is technical. |
| 10 | Ask about them, not about the money. | "Sam, I haven't heard back and I'd rather check in properly. Is everything alright? If you need to pause or stop, that's completely fine — I just need to know either way." | Move to a stated consequence. |
| 14 | State what happens and when, with a date. | "If I don't hear from you by Friday I'll pause your program from Monday. It's not the end of anything — message me and I'll switch it straight back on." | Do exactly what you said. |
| 21 | Pause access. Confirm it in writing. | "I've paused your program as of today. All your history is still there. Message me any time and we'll pick it up." | Prepare to close it out. |
| 30+ | Cancel the subscription and stop chasing. | "I'm closing off your account so it's not sitting there unresolved. No hard feelings at all — if you want to come back, message me." | Write it off. |
Two rules make this work. First, every message is short. Long messages read as anxious and invite long replies you then have to manage. Second, you never say the same thing twice — day 5 is not day 2 sent again, day 10 changes the subject, day 14 introduces a date.
Whether you can add a late fee, and whether your terms are enforceable, depends entirely on where you and the client are. Consumer credit and debt collection rules vary by country and by state, and some of what a US coaching contract does is not lawful in Australia or the UK. If you want to charge interest or send anything to collections, get advice from someone qualified in your jurisdiction before you do it, not after.
Pausing access without humiliating anyone
Pausing is not a punishment, and it should not be delivered as one. It is what happens when an unpaid service stops being provided, which is ordinary and which the client already expects.
Three things make it land well.
Say it before you do it. A pause the client was warned about is administration. A pause they discover by opening the app is an ambush, and it is the version that turns a lapsed client into someone who talks about you.
Do it quietly. No announcement, no removal from a group chat in front of forty other clients, no message that ends with "as per my terms". One direct message, from you.
Say what stays. Their logged history, their photos, their program record — none of it is being deleted, and telling them so removes the panic that makes people go further into hiding. Check what your platform's pause actually does before you use it here: on many, pausing a subscription only skips the billing and the client keeps full access, which makes it the tool for a client you are keeping rather than the way to stop delivering.
When the client genuinely cannot pay
Sometimes the reply, when it finally comes, is that they have lost their job or something has gone badly wrong. This is the moment most coaches handle worst, in both directions — either an uncomfortable silence, or an instant free ride that neither of you agreed to and that quietly turns into resentment.
Offer two specific things instead.
A pause with an end date. Not "let me know when you're back on your feet", which never resolves. Three months, resuming on a named date, billing skipped in between, program and history intact. The end date is what makes it a pause rather than an abandonment, and it means the conversation gets picked up by a calendar instead of by whoever feels worst about it.
A smaller tier. If you have a lower-priced package built out of things that scale — group programming, a template block, monthly rather than weekly contact — moving them down is better for both of you than losing them entirely. This is one of the more practical arguments for structuring your packages in tiers in the first place: it gives you somewhere to move people other than out.
And if the honest answer is that they need to stop, let them stop cleanly. Cancel the subscription, tell them the door is open, and mean it. A client who left with dignity refers people. A client who left owing you money they could not pay does not come back and does not recommend you — the wider version of that conversation is in how to end a coaching relationship.
When to write it off
At some point the correct decision is to stop. The test is simple: how much is owed against how much of your attention it is consuming.
One month of a mid-tier package is a few hundred dollars. If recovering it takes six messages, a week of low-grade dread and a difficult conversation, you have spent more than it is worth — and the time went into the one part of your business that produces nothing. Cancel the subscription so it stops accruing, mark it as bad debt for your accountant, and move on.
Two things make writing off cheap. One is that you stopped delivering at day 21, so the loss is one month rather than four. The other is that you priced with enough margin that a single unpaid month is a bad week, not a crisis — which is a question of what your business actually costs to run and whether your prices clear it. The cost breakdown is here.
Formal debt recovery for a few hundred dollars is almost never worth it for an independent coach, and the rules for it differ by jurisdiction. If the amount is genuinely large, take advice before you spend anything on it.
The prevention that matters most
Nearly all of this is avoidable, and the prevention is boring.
Bill automatically, on a card on file. Manual invoices depend on a client remembering, deciding and acting every single month, and each of those steps loses people. Recurring card billing removes all three. If you are still invoicing by hand, moving to automated recurring payments is the single change that removes the most late payments.
Let the retries do their job. Automatic retry on a failed charge recovers a meaningful share of failures with no human involvement. Do not disable it, and do not act ahead of it.
Make card updates self-serve. If fixing a card requires the client to message you and you to do something, half of them will not bother today and will forget by Thursday.
State the payment term at onboarding, in writing. One or two plain sentences: when you charge, what happens if a payment fails, and how much notice you need to cancel. Put it in the welcome document and in your agreement — the contract template covers the wording. Saying it once, at the start, when nobody is stressed, is what lets you send the day 14 message without it feeling like a threat.
Watch the disengagement, not the invoice. Clients almost always stop logging before they stop paying. If you notice the three quiet weeks, you have a coaching conversation. If you only notice the failed charge, you have a money conversation, and that one is much harder to win.
