DEV Community

Swipe Again
Swipe Again

Posted on

Subject Lines Do the Heavy Lifting: A Template Teardown

Open a folder of dunning templates from almost any subscription business and read only the subject lines, in sequence, as the customer receives them. Something like: "Your payment failed." "Action required: payment failed." "URGENT: your account will be cancelled." "FINAL NOTICE: payment still outstanding." Read cold, it sounds like a relationship deteriorating in fast-forward — from a billing hiccup to a final notice in four emails, about a charge the customer may not even know missed. The sequence escalates because templates are usually written one at a time, each author imagining theirs is the only message. Together, they tell a story nobody intended.

The fix starts with treating the sequence as one document with five movements. The first email's job is pure information, delivered without heat: a payment did not go through, here is the amount, here is the one link that fixes it. Its subject line should read like a receipt, not a warning — the subscriber is far more likely to be embarrassed than defiant, and a calm subject protects the open. The second email adds the one genuinely useful new fact: when the next attempt will happen, so the customer can align a payday or move money. New information is the only legitimate reason a second email exists; a louder restatement of the first is just volume.

The middle of the sequence is where the template libraries usually fail hardest, because it is where a different reader arrives. Early emails are read by subscribers who simply need a link. Later emails are read by subscribers whose situation is harder — a replaced card, a closed account, a subscription they are quietly reconsidering. The copy has to change register: less about the payment, more about the choice, with the options laid out plainly — update the card, pause instead of cancelling, or end it cleanly with access through the paid period. A sequence that offers no dignified exit converts waverers into chargebacks and disputes, which cost more than the renewal was worth.

Working through dunning email templates that sound like the business itself is a useful exercise in voice: the templates that perform read like the company's own support team on a good day — specific amounts, specific dates, one action per message, a signature from a recognizably human sender. The ones that fail read like they were written by the billing system, which, in a sense, they were. Subscribers decide in about two seconds whether a payment email is a person solving a problem with them or a machine processing them, and the subject line is where that decision starts.

Two disciplines hold the whole sequence together. First, every claim in every email must be operationally true: if the copy says an attempt happens Friday, the retry must happen Friday, because a customer who acts on the message and finds it false will not act on the next one. Second, the sequence must be wired to stop — on payment, on cancellation, on a dispute — the moment the situation changes. An email that arrives after the customer has already fixed the card is not a rounding error; it is the business announcing it does not know what it is doing, in writing, to the person it just rescued.

Rewrite the subject lines first, as a set, on one page. If they read like one calm person following up about one problem, the bodies will follow. If they read like an escalation ladder, no amount of body copy will undo what the inbox already said.


Published by Swipe Again — failed payment recovery at a flat $179/mo.

Top comments (0)