Skip to content

The subscription emails nobody ever builds (and that quietly lose you customers)

Payment recovery and expiring card flows almost never get built because they're tedious and live between two tools that talk poorly to each other. Yet that's where you lose subscribers you already paid to acquire. AI agents cut down the painful part so it finally ships.

Author
Axel Corton
Subject
CRM
Date
Read time
5 min
The subscription emails nobody ever builds (and that quietly lose you customers)

Key takeaways

  • You lose subscribers not because they want to leave, but because their card expired and nobody warned them.
  • Building these flows eats a full week of wiring triggers, testing and writing copy, so it stays stuck in the to-do list.
  • You already paid the CAC for this subscriber, then lose them over a single form field.
  • Priority order: expiring card (preventive), then dunning, then subscription states, then cancellation win-back.
  • With Claude and Codex plugged into Omnisend's MCP, 14 such flows are live on one subscription project.

There's one thing I see in pretty much every subscription brand we take over. The welcome series is there, polished, with the right design and the right tone. Makes sense, it's the part you can show off in a meeting.

And then there's everything else. Card expiring, payment failing, product out of stock, subscription paused, skip, cancellation. All of that is almost never done. It's on a list somewhere, down at the bottom, underneath the more interesting thing this quarter. And it stays there.

The worst part is that you're not losing those subscribers because they stopped wanting your product. You're losing them because their card expired and nobody told them.

Everyone knows these emails need to exist

Everyone knows these emails need to exist. That's not the problem. Ask any CRM lead whether payment recovery flows matter and they'll say yes without blinking.

So why does it never get done? Because it's a pain to build, and because it lives across two systems that talk to each other badly. You've got your email tool on one side (Klaviyo, Omnisend, whatever) and your subscription management tool on the other. And in the middle, the data has to flow correctly. The subscriber's real status, the card expiration date, the payment status.

It eats up a week of someone's life. A real week, digging for the right triggers, testing that the flow fires at the right moment, writing the copy. And because it's the thankless work, it always comes after the collection launch or the new paid campaign. So it stays on the to-do list. For months.

I've seen it everywhere. And honestly, I get it. Between rebuilding a nice newsletter that'll make the client happy on a call, and building a payment recovery flow nobody will ever see except the people whose card expired, the choice is made pretty fast in everyone's head.

And those are exactly the subscribers where you're bleeding money.

You already paid for this subscriber

This is the thing that drives me a little crazy about this topic. You already paid for this subscriber, the CAC came out of your pocket at acquisition. You spent money on acquisition to bring them in, they converted, they placed an order, they subscribed.

And you lose them over a form field. A card that expires after three years, and that's it. Nobody warned them. They disappear from your active subscriber base and in your reporting it looks like normal churn. When really it's just a payment that slipped through the cracks.

I often compare it to retail. A subscriber whose card expires is like a loyal customer who comes into the store every week and one day forgets their wallet at the register. You're not going to say "oh well, bye." You set their items aside, you call them, you tell them to come back. In eCommerce, payment recovery is exactly that. Except most brands let the customer walk out without a word.

And if you want to see where these leaks actually cost you, start with your P&L before your campaigns. Badly managed subscriber retention often weighs more than the ROAS drop everyone's panicking about. an eCommerce audit that starts with your P&L

The flows that deserve to exist

When I talk about this part of subscription emails, here's what I mean concretely.

Payment recovery (dunning) is the first one. A payment fails, Stripe or your PSP automatically retries several times, and meanwhile you send a sequence to warn the subscriber and push them to update their card. This is where the biggest volume of recoverable subscribers plays out.

The card about to expire is the other big one, and this one's preventive. You detect that the card expires within the month, you send an email before the payment fails. It's the most profitable because you act before the damage is done.

Then you've got the whole series around subscription states. Product out of stock on their next delivery, subscription paused, delivery skipped, cancellation. On cancellation by the way, a well-thought-out win-back flow that goes out a few weeks later can bring some of them back.

Taken one by one, none of these flows will change your life. But all together, they genuinely bring churn down across your base.

Why I finally got around to it recently

I'll be honest, I put this part off for a long time myself on our own projects. Because it's exactly what I described above. A week of unfun work to fit in somewhere.

What changed the game recently is agents. Claude and Codex plugged into Omnisend's MCP. The agent reads the subscription's real status directly in the tool and builds the flow. So instead of blocking off a week, I described what I wanted, I reviewed the drafts, and I turned it on.

We've got 14 flows like this live on one of our subscription projects today. Built that way. And I'm honest enough to admit that without that tooling, I probably wouldn't have gotten there this early. Not at this stage anyway. It would've stayed on the list, like always.

I'm not saying the agent does everything on its own and it's magic. You have to review, fix the copy, check the triggers. But the most painful part, the one that made it take a week and therefore never get done, is massively reduced. And that's enough for the thing to finally come off the to-do list.

Go look at your flows today

If you run subscriptions, go open your email tool and look at your payment recovery flows. I'll bet you one thing. Either they're flat-out disabled, or it's still the default copy from three years ago that nobody ever touched.

If I were starting from scratch, here's the order. I'd start with the expiring card, because it's preventive and the most profitable. Then dunning on failed payments, which handles the bulk of the volume. The subscription states (pause, skip, out of stock) can come next. And win-back on cancellation last.

Once that foundation is solid, you can tackle the rest of your retention. And that's where other topics take over, like abandoned cart emails that actually work or your email subject lines nobody opens. It's also the kind of project we take on when we handle the email and SMS side for fashion brands.

But start with the least sexy one. The subscribers you let slip away over an expired card, that's money you already spent for nothing.

Sources

  1. Omnisend API docs — Omnisend MCP Server

Frequently asked questions

What is a dunning flow in eCommerce?

It's the email sequence that fires when a subscription payment fails. While your PSP retries the charge, you warn the subscriber and push them to update their card. It's what lets you recover subscribers lost purely because of a failed payment, not because they lost interest in the product.

Why are these emails so often missing when everyone knows they're needed?

Because they're a pain to build and they live between two systems that talk to each other badly, your email tool and your subscription tool. It takes about a week of unglamorous work, so it always comes after the more exciting topic of the quarter and it stays on the list.

Which subscription email do I start with if I'm starting from scratch?

With the expiring card flow. It's preventive, you act before the payment fails, it's the most profitable. Then dunning on failed payments for volume, then the subscription states (pause, skip, out of stock), and win-back on cancellation last.

Can AI really build these flows for me?

It does most of the painful work. With an agent plugged into the tool via MCP, it reads the subscription's real status and builds the flow. You describe what you want, you review, you activate. You still need to fix the copy and check the triggers, but the week of grind that blocked everything largely disappears.

How much can putting these emails in place actually bring in?

Hard to give you a magic number without seeing your account, and I'm wary of cookie-cutter promises. But every subscriber recovered from an expired card is CAC you already paid and that you're saving. On a running subscription base, it's often one of the cheapest recoveries to go after.

Keep reading

Subscribe to our newsletter

Our methods on paid media, eCommerce and CRM, in your inbox.

Opening soon