Failed Membership Payments: The Dunning Sequence That Saves Plans

Maintenance plans die by expired credit card more than by unhappy customers. Here is the 3-touch recovery text sequence, the update-link friction fix, and the save math that protects your recurring revenue.

System 7 from the Leveraged Owner Starter Pack

It is the first Monday of the month and your office manager is reconciling plan billings. Fourteen maintenance agreements show a declined charge — expired cards, a lost card reissued after fraud, one account with insufficient funds. Nobody called those customers. By the third declined attempt your billing software gives up, the agreement lapses, and those customers quietly disappear from the schedule. You did not lose them to a competitor. You lost them to the calendar date on a piece of plastic.

That is involuntary churn: customers you lose without either party making a decision. The fix is a dunning sequence — an automated series of payment-recovery touches that fire whenever a card declines. If you have maintenance plans, this post is part of the Pillar D playbook for keeping your calendar full and calm; pair it with maintenance plan upsells to past customers to grow the plan book you are about to protect.

Why expired cards kill maintenance plans quietly

Credit cards expire on a fixed schedule. Roughly a third of the cards on file at any shop are within a year of expiring, and customers almost never remember to tell you when a new card arrives in the mail. Every month, a small slice of your plan book fails its charge.

The damage compounds. A lapsed plan is not just one month of lost dues — it is the spring tune-up that never gets scheduled, the priority service slot that customer stops using, and the future equipment replacement you lose to whoever shows up at their door next. The customer is not angry. They just drifted away because nobody noticed the decline and nobody asked for the new card.

Most shops handle this by accident. The office notices the decline during billing, maybe calls once, and the customer says "oh yeah, I'll call you back with the new number" — and never does. A dunning sequence replaces the accident with a system: a short, firm, automated set of touches that recovers the payment with minimum staff effort and maximum dignity for the customer.

Touch 1: the day-of-failure update-link text

The first touch fires automatically the day the charge fails. Speed matters — the customer may not know their card was declined, and a same-day heads-up reads as service, not collection.

The text does three things: names the failed charge plainly, gives a one-tap update link, and keeps the tone warm. Payment-update links come from your payment processor or your billing software — the customer taps, enters the new card on a secure page, and the charge retries automatically. No login, no password, no "let me read you the numbers over the phone."

Touch 1 — Failed charge, day 0:

Hi [First Name], this is [Business Name]. The charge for your [Plan Name] plan ([Amount]/month) didn't go through today — this is usually just an expired or replaced card. Tap here to update your payment info in under a minute: [Secure Update Link]. Once it's updated, you're all set — no interruption to your plan. — [Your Name]. Reply STOP to opt out.

Concrete takeaway: touch 1 goes out the same day, gives a secure one-tap update link, and includes opt-out language in the first automated text. No scolding, no "past due" language — failed charges are almost always administrative, and the copy should treat them that way.

Touch 2: the day-4 personal call plus text backup

If the update link sits untouched for four days, the second touch is human. A real call from the office — not a bill collector's call, a customer-service call. The script is thirty seconds long: their card failed, there's a secure link on the way, we just want to keep their tune-ups on schedule.

The call is immediately backed by a second text, because voicemail piles up and texts get read. Send the text whether or not the call connects.

Touch 2 — Phone call script, day 4:

Hi [First Name], it's [Your Name] from [Business Name]. I'm calling because the card on your [Plan Name] plan didn't go through this month — probably an expired or reissued card. No worries at all. I'm sending you a secure link right now so you can update it in about a minute, and your plan stays active with no interruption. Would you like me to send that to this number?

Touch 2 — Backup text, sent right after the call:

Hi [First Name], [Your Name] from [Business Name] — just called about your [Plan Name] plan payment. Here's the secure link to update your card: [Secure Update Link]. Takes about a minute, and your spring/fall tune-ups stay on schedule. Questions? Just reply here. Reply STOP to opt out.

Concrete takeaway: day 4 gets a human call because this customer is four days from silently lapsing. The framing is always "keep your tune-ups on schedule," never "your account is past due." You are protecting their benefit, not collecting their debt.

Touch 3: the day-10 "pause, not cancel" final text

The third touch is the last automatic one. It names a specific consequence — the plan pauses, not cancels — and gives one final one-tap update. "Pause" is deliberate language: canceling feels like a fight and invites the customer to shrug and leave. Pausing feels temporary and invites a tap.

Touch 3 — Final recovery text, day 10:

Hi [First Name], this is [Business Name]. We still haven't been able to update the payment for your [Plan Name] plan, so we've placed your plan on pause starting [Date] — your member pricing and tune-up slots are held, not canceled. Tap to reactivate in one minute: [Secure Update Link]. We'd love to keep you. Reply STOP to opt out.

Concrete takeaway: touch 3 uses a firm, named consequence (plan pauses on a date) while leaving the door wide open (slots held, one tap to reactivate). After this touch, stop texting about the payment — further texts about money start to feel like harassment, and the compliance clock matters (more on that below).

The update-link friction fix

The entire sequence lives or dies on the update link. Every extra step between the text and the updated card costs you recoveries. Walk through your own update flow on your phone before you turn the sequence on:

Also decide what happens to customers who never open the link: after day 10, the agreement sits paused. Schedule one office follow-up call per paused plan per month, and keep it human — "Hey, we miss you on the schedule." Those calls are the long tail of the sequence and they save plans the texts could not.

After day 10: pause, then win back

When the sequence ends without an update, do not keep dunning. Change the customer's status to "paused plan" in your system, stop the money texts, and start the win-back clock instead: thirty days later, a different kind of text — not about the failed charge, about the missed benefit.

Win-back text, day 30 after pause:

Hi [First Name], it's [Your Name] from [Business Name]. Your [Plan Name] tune-up slot for [Season] is coming up and we'd love to have you back on the schedule. If the old card was the problem, here's a fresh link to reactivate your plan: [Secure Update Link]. Either way, happy to book the tune-up as a one-time visit if you'd like. Reply STOP to opt out.

Concrete takeaway: after the 3-touch sequence ends, the payment conversation is over and the relationship conversation begins. The customer who would not update a card may still book a tune-up — and a tuned-up customer is one office call away from rejoining the plan.

Worked example: the save math

Here is a worked example so you can run your own numbers. Example: a shop carries 240 maintenance plans at $29 per month. Each month, 12 charges fail (5% of the book — cards expire in waves). Without a sequence, the office saves about 2 of them with a casual call, so 10 plans lapse every month.

A 3-touch dunning sequence with a clean update link recovers roughly 8 of the 12. That is 6 extra plans saved per month, or 72 plans per year that keep paying $29 monthly dues — before you count a single tune-up, filter, or replacement those members would have bought. The sequence itself costs the shop maybe two hours of setup and one phone call per month for touch 2. That is the entire pitch for building it this week.

The compliance corner

Recovery texts are business texting, so the rules apply in full. Before you send the first automated text: A2P 10DLC registration on your business number (A2P = application-to-person messaging; 10DLC = the carriers' registration system for business texting; 1–7 day approval, ~$15–$20 one-time). Include opt-out language ("Reply STOP to opt out") in the first automated text to each customer. Keep every text inside TCPA (federal telemarketing law) quiet hours — no texts before 8am or after 9pm in the recipient's local time. This is general information, not legal advice; if you are unsure whether your billing texts qualify as transactional or marketing, check with an attorney before you scale them.

Related guides in this series

If you are building recurring revenue, protect it the way you built it: the appointment confirmation texts that keep tune-up slots from going empty, maintenance plan upsells to past customers for growing the plan book, and the filter-change reminder series that keeps members engaged between visits.

Get System 1 free: the complete Missed-Call Safety Net

The full setup SOP, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.

Free. The full 8-system Starter Pack is $27 if you want everything else.

The done-for-you version

This post is System 7 from the Leveraged Owner Starter Pack — the done-for-you version with the full SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems. Build the whole dunning sequence in one afternoon instead of piecing it together from blog posts.

Stats sourced as labeled: examples in this post are illustrative worked examples, not customer results; texting compliance details are general information, not legal advice.

Keep building your systems

Related guides from the Leveraged Owner blog: