Most failed-payment email sequences fail as literature before they fail as billing. Four messages go out, and all four say the same thing at slightly rising volume: your payment failed, update your card, we mean it this time. A sequence is not one message repeated with escalating punctuation. It is four different jobs, done in an order that matches how a person actually fixes a card problem — which is rarely in the first hour, and almost never because the subject line got louder.
Email one has the easiest job and the most commonly botched one: deliver the news while it is still news. It should arrive close to the failure, name the problem in plain words, and carry exactly one action — a link that lands on a card form, not a login wall. Its tone is clerical, not alarmed. At this point most customers have no idea anything happened; a message written as a final warning teaches them the sender panics early, and they price every later message accordingly.
Email two belongs to the calendar, not the inbox. Its job is to arrive after the plausible fixes have had time to happen — a payday has passed, a replacement card has had days to arrive and be activated. Sending it on day two because the template says day two wastes the best-timed message in the sequence on a moment when nothing could have changed yet. Timing is the copy here; the words barely matter if the day is wrong.
Email three is the honest one. Its job is to explain consequences without theatre: access pauses on a named date, the plan and its history are held until then, and the door stays open after. People respond to a real deadline stated once, calmly, far more reliably than to urgency sprayed across every touch. This is also the message that should sound most like the brand the customer actually bought from — same voice as the welcome email, not a collections department that materialised overnight.
Email four closes the loop and, done well, earns a surprising share of the recoveries. It accepts the cancellation, keeps the update link alive, and leaves a specific, easy way back. A meaningful slice of lapsed subscribers return weeks later when the card problem resolves itself; a sequence that ends in silence or resentment forfeits them to a competitor's signup page instead.
Two failure modes haunt sequences that get the four jobs right. The first is the login wall: the email's single action leads to a sign-in page, the customer does not have the password in reach, and the moment passes — a remarkable share of otherwise good sequences die at exactly that door, which is why the update link should land on the card form itself, token and all. The second is the silent retry storm behind the emails: five automated attempts firing between messages, so the customer who updates a card on day three discovers three more attempts already failed against the old one. The emails and the retries are one system. Reading them side by side, on one timeline, is the review most sequences have never had.
For the full pacing — which day each job belongs on, what each message should and should not contain, and how the sequence flexes by decline type — a teardown of dunning email frameworks by the job each one performs lays out the timing and the copy together, because in this corner of billing the two are the same decision.
Count the sequence by replies and updates per message, not opens. The email that looks quiet in a dashboard is often the one that arrived on the right morning.
That discipline — every touch with a job, a day, and a reason — is how Swipe Again builds its outreach: fewer messages than the templates suggest, each one sent because something about the customer's situation could actually have changed.
Top comments (0)