At 8:47 on a Monday morning, Maya, who leads operations for a subscription reporting tool with about 4,000 paying accounts, opened the overnight billing run and found 31 failed renewals. Most were familiar: a card that had expired over the weekend, a bank that wanted authentication, a corporate card replaced after an employee left. A support colleague, trying to be fast, sorted the list by amount, pasted the company's strongest unpaid-invoice template into an email, and sent it to all 31. By lunch, three customers had replied in alarm. One asked whether their account was being referred for collection. Another, a customer for four years, cancelled on the spot — not because the charge had failed, but because the message told them the company saw them as a debtor, not a subscriber whose bank had simply said no.
The payment problem took ten minutes to fix for most of those accounts. The trust problem took much longer. That gap is the subject of this essay: an invoice for a subscription that has not yet renewed is not a collections letter, and treating it like one changes what customers hear, what your team does next, and what obligations you may be creating for yourself.
Two different jobs
Dunning is the communication and retry process that begins when a legitimate, expected subscription charge fails and the customer is not yet in default in any meaningful sense. The card may be expired, the bank may have soft-declined the attempt, or the customer may need to complete a verification step. The goal is restoration: update the payment method, agree a sensible retry, and keep a willing customer subscribed.
Collections is different. It starts later, after a debt is genuinely due, attempts to resolve it have failed, and the business is now seeking payment for value already delivered, often with formal notices, deadlines, and consequences. Understanding where dunning ends and collections begins helps operators place each failed payment on the right side of that line before they choose language, timing, or escalation.
Tone is a diagnostic, not a decoration
In dunning, tone should assume good faith and a solvable problem: “We could not process your usual card — you can update it here, and your workspace stays available until Friday.” That is specific, calm, and actionable. Collections language assumes non-payment: “final notice,” “failure to remit,” “further action.” Use the second vocabulary for the first situation and you manufacture conflict. Use the first vocabulary for a genuinely defaulted account and you manufacture delay, because nothing signals that the position has changed. Read your current templates aloud and mark every word that implies intent. A failed authorization, on its own, proves nothing about intent.
Timing separates help from pressure
Dunning lives in hours and days: a prompt notice while the customer still remembers the renewal, a small number of well-spaced retries, and clear information about what happens at the end of the grace period. Collections lives on a formal timetable, after that grace period and after fair notice. Problems arise when teams compress the two — five urgent messages in 48 hours, access cut off before the stated date — or stretch dunning indefinitely, retrying a dead card for months while revenue and the customer's own records drift. Write the timeline down, with dates the customer can verify, and then honour it.
Legal posture is part of the design
This is not legal advice, and rules vary by place and by whether you sell to consumers or businesses. But the posture differs. Dunning is ordinary communication about a contract the customer still wants performed. Collections can trigger specific consumer-protection, credit, privacy, and communications rules, and it creates records that may be relied on later. That is why improvised threats are so costly: a message that casually mentions referral, reporting, or legal steps may commit you to a process you have not checked and do not intend to run. Keep dunning factual, keep evidence of notices, and involve qualified counsel before a real collections track begins.
Who owns each process?
In a healthy subscription business, dunning is owned jointly by billing operations and customer success, with support able to see the same status the customer sees. Collections, if it exists at all, is owned by finance, with a defined handover, a different template set, and a clear point at which subscription access and debt recovery are treated as separate questions. When one inbox owns both with one set of macros, the strongest macro wins — and it is usually the wrong one.
A practical checklist before you send anything
- Classify the failure first: expired card, soft decline, authentication needed, or genuine non-payment after grace?
- Check how many days have passed and what the customer was last told.
- Remove any word — “final,” “delinquent,” “enforcement” — that the facts do not yet support.
- Give one clear action, one secure place to do it, and one date that matters.
- State what stays available during the grace period, and do not cut access earlier.
- Log the notice, the retry schedule, and any customer reply in the billing record, not only in a support thread.
- Define, in writing, the exact condition that moves an account out of dunning — and who must approve that move.
Maya's team kept the helpful parts of that Monday: the quick sorting, the same-day follow-up. They replaced the template, separated the queues, and made the handover explicit. The renewals did not all recover — they never do — but the replies changed from defensive to practical, which is what dunning is for.
If you are reviewing your own sequence, start with the language your newest customer would receive on their worst morning, and compare it with what Swipe Again's failed payment recovery service is designed to do: recover a willing subscriber first, and escalate only when the facts have actually changed.
Top comments (0)