DEV Community

Swipe Again for Swipe Again

Posted on

The Second Send Is Where Templates Earn Their Keep

The first dunning email is easy to write because the situation is simple: a payment failed, here is a secure link, please update your card. Almost any polite template handles it adequately. The templates that matter are the later ones — the second send to a customer who opened the first and did nothing, and the final send to a customer who has now ignored two. Those are the moments where tone, information, and judgement separate a working sequence from a stack of reusable text.

The second send needs to add information, not volume. Repeating the first email louder teaches the customer that the sender has nothing new to say. A useful second message answers the questions that stopped the first one from working. Is this charge the subscription they think it is, named the way they would name it? What exactly happens if they do nothing, and by when — a real date, not a vague warning? Is there a human route if the card is fine and something else is wrong? A template that carries those answers respects the most common reason for inaction, which is not defiance. It is uncertainty.

There is also a mechanical point templates often miss: the link is the product. The update page the email sends people to decides more outcomes than the copy does. It should open fast, work on a phone held in one hand, ask for nothing beyond the card, and confirm clearly when the update succeeds. Any template review that stops at the inbox is reviewing the envelope and ignoring the letter. Send every template to yourself, follow it as a customer would, on the phone you actually carry, before arguing about a single sentence.

That standard sits behind failed payment email templates written for the second send, not the first: a sequence is judged at its hardest step, where the easy recoveries are gone and the remaining customers need a reason, a reassurance, or a graceful exit. The final send especially needs that grace. A customer who is leaving anyway should leave with the account closed cleanly and the door open, not with a threat that guarantees they describe the business unkindly to the next person who asks.

Personalisation, in this context, is mostly accuracy. The customer's name matters less than the correct amount, the correct plan, and the correct date their access changes. Getting those three right signals a system that knows the account. Getting one wrong signals a bulk mailer, and bulk mailers get ignored with a clean conscience. Templates should therefore be tested against real account data — including the awkward cases, the annual plan, the paused subscription, the customer mid-trial — because those are exactly the records where a merge field quietly produces nonsense.

One more discipline separates working sequences from template libraries: every send should have a job that can be stated in one line, and sends without a job should be deleted. The first send informs. The second send removes uncertainty. The final send closes honestly, with the consequence and the deadline stated once, plainly. A fourth send usually exists because nobody decided where the sequence ends, and indecision reads to the customer as pressure. Pressure recovers a few payments and costs more goodwill than the ledger ever shows.

Write the templates on a calm day, approve them as a set, and then let them run without weekly tinkering. The sequence that works is the one whose words were chosen before anyone was staring at a churn number — a point Swipe Again returns to often, because billing emails written in a panic sound like it, and customers can always tell.

Top comments (0)