Resources

7 Dunning Email Mistakes That Kill Recovery

Most failed payments are recoverable. Most dunning emails are not built to recover them. The gap is rarely effort — operators send the email, on time, from the billing system. The gap is in the details: a subject line that says nothing, a body that hides the amount, a link that lands on a login wall, and then silence. Subscribers do not ignore dunning because they want to churn. According to Recurly research, 20–40% of subscriber churn is involuntary, which means a large share of the people you lose to a failed card never made a decision to leave. They just never fixed the problem your email described badly. This piece walks through seven dunning email mistakes that kill recovery, what each one costs you, and the fix you can ship without rebuilding your whole sequence. If you want the positive model first, start with dunning emails that work and then audit your own sequence against the mistakes below.

Mistake 1: A vague subject line

The mistake. Subjects like "Important information about your account," "Billing update," or "Action required" tell the subscriber nothing. They read like every other system notice in an inbox full of system notices, and they get triaged the same way: later, which usually means never. A vague subject also hurts you with spam filters and inbox tabs, because it gives neither the subscriber nor the filter a clear signal that this message is personal and time-sensitive.

The fix. Name the product, the problem, and the action in the subject. "Your [Product] payment failed — update your card to keep access" is longer and far more effective, because the subscriber can decide in two seconds that it matters. Keep the subject honest: do not fake urgency you do not have, do not use a fake reply prefix, and do not promise the account is already cancelled when it is not. Specificity is the urgency.

Mistake 2: No amount, no date, no card detail

The mistake. The email says a payment failed but never says how much, for what, or on which card. The subscriber cannot verify the charge is theirs, cannot check whether the card in question is the one they replaced last month, and cannot tell whether this is a duplicate notice for a problem they already fixed. So they do nothing, or worse, they mark it as suspicious.

The fix. Put four facts in the first three lines: the amount, the plan or product name, the date the charge was attempted, and the card brand and last four digits. That combination lets the subscriber match the failure to their own records in seconds. It also separates your notice from phishing: a dunning email asking for card details without identifying the charge looks exactly like the scams subscribers are trained to delete.

Mistake 3: One email and done

The mistake. A single failure notice, sent once, and then the subscription quietly lapses when the retries run out. One email assumes the subscriber saw it, understood it, and had their new card in hand at that exact moment. In practice the first notice lands during work, gets buried by the evening, or arrives before payday for an insufficient-funds failure — the largest single decline category at 40.6% across 5.4M failed payments, according to Churnkey's published analysis of Stripe data. Timing, not intent, is what kills that recovery.

The fix. Run a short sequence, not a single shout. A practical pattern is an immediate notice when the failure happens, a reminder a few days later paired with your retry schedule, and a final notice before access changes. The touches should not be identical copies — vary the angle: first the facts, then the simple update path, then the deadline and what happens next. This is not nagging for its own sake. According to Churnkey's published analysis of Stripe data, each additional dunning email touch adds roughly 1–2 points of recovery. Each touch earns its place, provided the sequence stops the moment the payment succeeds or the card is updated. Use the dunning email deliverability checklist to make sure those extra touches actually reach the inbox instead of the spam folder.

Mistake 4: A dead-end card update link

The mistake. The email asks the subscriber to update their card, and the link goes to a general login page, a homepage, or an account dashboard where the billing form is three clicks deep. Every extra step loses people. Worse variants exist: the link expires before the subscriber opens the email, the update page is not usable on a phone, or the page demands a password reset before it will show the card form to someone who has not logged in for months.

The fix. Link to a dedicated, secure card update page that opens with the task already in front of the subscriber — no hunting, no unrelated navigation, no upsell in the way. The page should work well on mobile, confirm success clearly when the new details are saved, and ideally trigger a re-attempt so the subscriber sees the resolution, not just a form submission. Test the full path yourself from a phone, logged out. If inbox to updated card takes over a minute, your recovery rate is paying for the friction.

Mistake 5: The wrong sender

The mistake. Dunning arrives from a billing platform domain, a no-reply address, or a name the subscriber has never seen. The subscriber signed up for your product, not your processor. An unrecognized sender gets the phishing treatment — deleted, ignored, or reported — and a no-reply address tells the subscriber that the one channel they might use to explain a problem is closed.

The fix. Send from your own brand, on your own domain, with proper authentication in place, and use a reply-to that a human or at least a monitored inbox actually reads. Some of the most valuable dunning replies are not card updates at all: they are "I am in hospital, please pause me," "our company card changed, send this to finance," or "I thought I cancelled." Each of those is a save waiting to happen, and every one of them bounces off a no-reply address.

Mistake 6: A threatening tone

The mistake. First-notice language that sounds like collections: account suspended, immediate action required, failure to comply. The experience behind most failures is mundane — an expired card, an empty account two days before payday, a bank that flagged a legitimate charge. Leading with punishment for an accident makes people defensive, and defensive people cancel to end the interaction rather than fixing the card.

The fix. Assume good faith in the early touches and save firmness for the final notice, where a clear deadline is honest rather than hostile. "Your card did not go through — here is the quick fix" outperforms "Your account is past due" for the same failure. Name the consequence plainly when it is real: access pauses on a stated date if the payment is not resolved. Tone is not softness — it is sequencing. Help first, warn clearly once, then follow through on exactly what you said.

Mistake 7: No final notice

The mistake. The sequence just stops. The subscription cancels or the account closes without a last, unmistakable message saying this is the final chance, what will happen, and when. Subscribers who meant to fix the problem get no trigger to act, and subscribers who later complain are right about one thing: nobody told them it was ending.

The fix. End every sequence with a true final notice, sent while there is still time to act. It should state the exact date access ends or the subscription cancels, repeat the amount and the one-step update path, and offer the alternatives that fit: update the card, pause instead, or talk to support. After that date, do what the notice said. A final notice that cries wolf trains subscribers to ignore the next one. Ready-made structures for every stage, including the final notice, are in the dunning email templates — adapt the copy to your brand rather than sending the defaults your billing platform shipped with.

A quick audit you can run today

1. Read your live sequence as a subscriber. Trigger a test failure and read every email cold. Would you know the amount, the card, and the deadline?
2. Click every link on a phone, logged out. Time the path from email to a saved card update. Anything over a minute is a defect, not a preference.
3. Count the touches and the gaps. One email is a mistake. A sequence with no final notice is unfinished. Check that touches stop immediately on success.
4. Check the sender. Your brand, your domain, a monitored reply path. If the From line names your processor, fix that before you write another word of copy.
5. Check the last email against reality. The date it promises must be the date your system acts. Mismatches destroy trust in every future notice.

The bottom line

None of these seven mistakes require new software. They require reading your own dunning the way a busy subscriber reads it: quickly, on a phone, with no patience for vagueness. Say what failed, for how much, on which card. Send more than once, from your own name, in a tone that assumes an accident. Link to a page that does one job. And finish with a final notice that means what it says. Recovery is mostly the removal of reasons to do nothing.

Frequently asked questions

How many dunning emails should I send?

Enough to cover the retry window with distinct touches rather than one notice. A common practical pattern is an immediate failure notice, one or two reminders spaced with your retries, and a final notice before access changes. The exact count matters less than stopping immediately when the payment succeeds and making each touch add information instead of repeating the first email.

What should a dunning email subject line say?

It should name your product, state that a payment failed, and point to the action, such as updating a card to keep access. Avoid generic subjects like billing update or important account information, which subscribers triage as low priority and which give spam filters nothing useful to work with.

Should dunning emails include the amount and card details?

Yes. Include the amount, the plan or product name, the date of the failed attempt, and the card brand and last four digits. Those details let the subscriber verify the charge is theirs, identify which card needs replacing, and trust that the message is legitimate rather than a phishing attempt.

Why does the card update link matter so much?

Because friction at that step decides whether intent becomes recovery. A subscriber who clicks through to a login wall or a general dashboard often abandons the task, while a direct link to a secure update page that works on mobile can be completed in under a minute. Test the path yourself, logged out, on a phone.

Is a firm tone ever appropriate in dunning?

Yes, in the final notice, where a real deadline exists. State plainly what will happen and on what date, and then follow through. Firmness works when it is specific and true. Threatening language in the first notice, before the subscriber has had a fair chance to fix an ordinary accident, tends to push people toward cancelling instead.

Related reading: Dunning copy personalization