Dunning Emails for Failed Subscription Payments, Drafted With AI

Send three emails: a same-day notice that the payment failed, a reminder about four days later, and a final warning one or two days before access ends. Each carries one clear button to update the card. Let your billing tool retry the charge in between, and use AI only to draft the words.

Most failed subscription payments are not customers leaving. They are expired cards, a bank blocking a charge, or an account without enough money that day. The customer usually wants to stay, so the job of the email is to make a fix easy, not to scold. That tone is where AI helps most, and where an unchecked draft does most harm.

Follow me on Instagram@sagnikteaches

Why a failed charge needs three touches, not one

One email gets read by some and buried by others. Two catch most of the rest. A third gives a customer who was away or distracted a fair last chance, with a date that makes the choice real. Past three, each extra email adds more irritation than recovery for a small business whose customers know the owner by name.

Connect on LinkedInSagnik Bhattacharya

Think of the sequence as three different jobs, not three copies of the same email.

Subscribe on YouTube@sagnikteaches

• Email 1, the heads-up. Tell them calmly what happened and give the one-click fix. No deadline yet, because most cards recover or get updated within a day.
• Email 2, the reminder. Say that the payment still has not gone through, repeat the fix, and mention what happens if nothing changes, in a neutral tone.
• Email 3, the last notice. Give the exact date access pauses or the subscription ends, restate the fix, and offer a human reply as a way out for anyone in a difficult spot.

Fit the emails to your retry schedule

Dunning means chasing an overdue payment, and it has two halves: the retries your billing tool makes automatically, and the emails you send. They must agree, or customers get an email saying "we will try again on Friday" and a charge on Wednesday.

If you use Stripe Billing, Smart Retries uses AI to choose when to retry. According to Stripe's documentation, you set a number of retries within a window of 1 week, 2 weeks, 3 weeks, 1 month or 2 months, and new accounts are set up by default for up to 8 retries within 2 weeks. You can instead turn Smart Retries off and write a custom schedule of up to three retries, each a set number of days after the last. When the card issuer returns a hard decline, such as a lost card, a stolen card or an incorrect number, Stripe keeps the retries on the schedule but only runs the payment once the customer provides a new payment method, which is exactly where your emails matter.

Other billing tools (Chargebee, Recurly, Paddle, Shopify Subscriptions and the like) have similar settings under different names. Whatever you use, find three things before you write a word: how many retries it makes, over how many days, and what happens to the subscription at the end. Stripe, for example, offers four end states: cancel the subscription, mark it unpaid, leave it past due, or pause it if the subscription is eligible. Your emails describe those facts, so get them right first.

A workable plan for a $24 monthly subscription on a custom schedule of three retries (illustrative):

The point of the table is the alignment: every email lands after a retry, never before the tool has had a chance, and email 3 is written only once the end date is certain. On Smart Retries you cannot see the retry days in advance, because the tool picks them, so key your emails to days since the failure instead and have each one check the invoice is still unpaid before it sends. Stripe's default of up to 8 retries in 2 weeks also means a later end date than this table, so your pause date has to come from your actual setting.

What to switch on in the billing tool before writing your own

Many providers send their own failed-payment emails. Stripe's documentation lists several you can turn on: failed payment notifications (an email after each failed payment, with a link to update the payment method), expiring card notifications (sent one month before the card on file expires), renewal reminders, and trial-ending reminders. Those links can point to a Stripe-hosted Customer Portal or to your own subscription management page. Stripe notes the hosted link stops working in some situations, for example once the subscription is cancelled or unpaid, so your last email should not rely on it alone.

That gives you a decision. Provider emails are dependable and secure, but they are generic. Your own emails can carry your voice and the right promises. A sensible split for a small business:

• Switch on expiring card notifications. This prevents the failure, which beats recovering it.
• Keep the provider's failed-payment email for email 1 if you like its wording, or turn it off and send your own, but never both on day 0. Note that Stripe's version goes out after each failed payment, retries included, so with Smart Retries running eight attempts, leaving it on alongside your own three can mean far more emails than you planned. If you want exactly three, switch Stripe's off and send yours.
• Write emails 2 and 3 yourself, because they carry your tone, your pause date and your offer to help.

Test everything with a sandbox customer using a test card that declines before you go live. A sequence you have never seen arrive is a sequence you cannot trust.

The card-update link: where recovery is won or lost

The button is the product of the email. A customer who has to log in, hunt for billing and re-enter an address will not. Rules for the link:

1. One link, one action. "Update your card" goes to a page that does only that.
2. No password wall if you can avoid it. A secure hosted page, such as the provider's customer portal link, beats a login screen.
3. Same wording on the button in all three emails. Customers who half-remember the first email will look for the same words.
4. Check the link on a phone. Most of these emails are opened on one, and a page that needs pinching and zooming loses people.
5. Do not paste card details into any message. Say so in the email: "We will never ask you to reply with card details."

Test by clicking the real link in a test email, in a private browser window, as a customer would.

Draft the sequence with AI: a prompt that works

Give the assistant the facts and the tone, and tell it what it must not invent. A Project in ChatGPT or Claude lets you keep the instruction and your brand voice notes in one place, so every email in the sequence sounds alike. Illustrative prompt:

I run a small subscription business selling a $24-a-month coffee box. Write a three-email failed-payment sequence.

Facts you must use exactly:
- The charge failed on day 0. Our billing tool retries automatically over about 10 days.
- Email 1 goes out on day 0, email 2 on day 4 if still unpaid, email 3 on day 8 if still unpaid.
- On day 10, if unpaid, the subscription pauses and the next box is not sent. The customer can restart any time.
- Each email has one button, labelled "Update your card", linking to [UPDATE LINK].
- Replies go to a real person. Sign off as [your name].

Rules:
- Calm, friendly, plain words. No guilt, no capital letters, no exclamation marks.
- Never invent discounts, deadlines or consequences beyond those above.
- Never ask for card details in a reply.
- Each email under 110 words, with a subject line under 45 characters and a preview line under 70.
- Give two subject-line options for each email.

Here is the kind of first draft a good assistant returns for email 1 (illustrative):

Subject: Your coffee box payment didn't go through
Preview: A quick fix keeps your next box on its way.

Hi [first name],

We tried to take $24 for your coffee box today and your bank didn't accept it. That's usually an expired card or a temporary block, and it is quick to sort out.

Update your card here: [UPDATE LINK]

We'll try again over the next few days, so you won't miss a box if it goes through. If anything looks wrong, just reply to this email.

[your name]

What would you change? Check the claims against your facts. "You won't miss a box if it goes through" is true only if your retries and your shipping cut-off agree, so reword it if the box ships on a fixed date. The subject line is fine. The preview line promises a box "on its way", which could be wrong if the retry fails. Edit it to "A quick fix keeps your subscription active."

Email 2 and email 3: what changes

For the second email, the point is not to repeat the first. It tells the customer that the earlier attempts did not work and gives the same button.

Subject: Still can't take your $24 payment
Preview: One update and you're back on track.

Hi [first name],

Your coffee box payment still hasn't gone through. We tried again yesterday, and your bank is still declining it.

Update your card here: [UPDATE LINK]

If your card is fine, your bank may be blocking us. A quick call to them often clears it. And if you want to pause or stop, reply and I'll sort it, no questions.

[your name]

The third email brings the date and the human exit.

Subject: Your subscription pauses on 14 March
Preview: Last reminder before your next box is held.

Hi [first name],

This is our last reminder. If we can't take your payment by 14 March, your subscription will pause and your next box won't be sent. You can restart whenever you like.

Update your card here: [UPDATE LINK]

If money is tight this month, reply and tell me. We can pause it properly instead of letting it lapse.

[your name]

Notice what the third email does that the others do not: it names the exact date, and it opens a door for anyone in difficulty. Replace "14 March" with a placeholder your system fills in, and never let AI choose the date. If you automate the date merge, test it with three sample customers whose retries ended on different days.

Check the tone: before and after

Left to itself an assistant may produce something like this, which reads as a warning from a collections department:

Before: "Failure to update your payment information immediately will result in suspension of your account. Please take urgent action."

After: "Your payment didn't go through. Updating your card takes about a minute, and then everything carries on as before."

The test is simple: would you say it to a regular at your counter? Ask the assistant to rewrite anything that sounds like a legal notice. Anything with "immediately", "failure to" or "you must" deserves a second look, because customers who got caught by an expired card are embarrassed, not careless.

Handling customers who reply

Some recipients answer the email. Prepare short responses for four common replies and let AI draft the variations:

• "I updated my card, why am I still getting emails?" Check whether the retry has run yet; sequences should stop when the payment succeeds. If they did not, fix the trigger.
• "I want to cancel." Do it, confirm it, and send no further dunning emails.
• "I cannot pay this month." Offer a pause. This keeps the relationship and costs you nothing you were going to collect.
• "My bank says your charge is suspicious." Ask them to approve the merchant name as it appears on their statement, and tell them the descriptor to look for.

The boundary with chasing invoices is worth knowing: our tutorial on chasing late payments with AI reminders covers one-off invoices, where the customer can dispute the amount. Card-on-file failures are different, because the customer already agreed to pay and usually just needs a nudge.

A worked example: a $24 box with 400 subscribers

Illustrative figures for a small subscription coffee business, to show what a dunning sequence is worth.

• Subscribers: 400, at $24 a month = $9,600 a month in recurring revenue.
• Failed charges in a typical month: 6% = 24 customers.
• Before the sequence: the billing tool's retries recover 9 of the 24 on their own, and the other 15 lapse. Lost monthly revenue: 15 times $24 = $360, and the subscribers are gone.
• After the three-email sequence with a hosted update link: say 9 more of the 15 update their cards. That saves 9 times $24 = $216 a month, a figure to track yourself rather than assume.
• The cost: your time to set it up (a morning), plus a few minutes a month reviewing replies.

The sum shows the limit of the exercise. You will not save every customer. Some cards are cancelled, some customers have left in all but name. Your target is the middle group who would have stayed if the fix had been easy. Count them honestly: customers recovered with an email versus those whose retry just succeeded on its own. Most billing tools report recovered payments somewhere in their dashboard; note that figure before and after the change, or count it yourself from the list of invoices paid after a failure.

Why a sequence goes wrong and how it shows up

Take a business where a customer's card was fixed on day 1, but the day 4 email still went out. The customer wrote back annoyed, quoting the email. The cause was a sequence tool scheduled on dates, not on payment status, so it did not know the invoice had been paid. Nothing flagged it; the only sign was an angry reply.

Check for these before launch:

• Does each email check the invoice status immediately before sending?
• Does a successful retry stop the sequence and send a receipt?
• Does a cancelled subscription stop it too?
• Is the "pause date" in email 3 pulled from the system, not typed in by hand?
• Do two senders (provider and you) ever email the same customer the same day?

If you are building the triggers in an automation tool such as Zapier or Make, a trigger that checks for new data on a schedule runs at an interval your plan sets (Zapier's developer docs give every 1 to 15 minutes, depending on plan), so it can lag behind the billing tool by several minutes. A failed payment does not need minute-level speed, but a fixed card does need the sequence to stop before the next email goes. Event-based triggers from the billing tool, such as Stripe's invoice.payment_failed event, are the cleaner choice where you can use them: the event's attempt_count field tells you how many attempts have been made so far, which is handy for picking email 2 or email 3.

The email before the failure: expiring cards and pre-dunning

The cheapest recovery is the one you never need. Cards expire on a known date, and your billing tool usually knows it. Stripe, for instance, can email a customer one month before the default card on file expires. Add your own short note about ten days before the date, written by AI in the same voice as the dunning emails:

Subject: Your card ends soon
Preview: A one-minute update avoids a missed payment.

Hi [first name], the card we have for your subscription expires at the end of this month. To keep things running without a hitch, you can update it here: [UPDATE LINK]. Nothing to do if you have already got a new card from your bank and it carries the same number. [your name]

Check the last sentence with your provider, because some banks reissue cards with the same number and some do not, and your tool may or may not pick up the new expiry date automatically. If you are not sure, delete that line.

The same sequence for a physiotherapy clinic care plan

A physiotherapy clinic that sells a $45-a-month care plan has different customers from a coffee box. People are mid-treatment, some are in pain, and a cancelled plan can mean a missed session. Three adjustments:

• Change the tone of email 3 from "your next box" to "your next booked session", and say that existing appointments are kept for now. Only promise that if the clinic has agreed it.
• Add a line inviting the patient to call the front desk. Some will prefer to pay by phone.
• Do not mention treatment, conditions or progress in any billing email. Billing emails go to inboxes that others may see, and health details do not belong in them.

The structure stays the same. What changes is what the pause means to the customer, which is why the facts block in your prompt has to say it in your own words.

Keeping the sequence honest and legal-safe

A few things belong outside the AI's remit. The email must say clearly what will be charged and when. It should not threaten consequences you will not apply (such as passing the account to collections when you have no such process). If you have customers in places with consumer-protection or payment-services rules, have an adviser look at what you say about pausing, cancelling and charging again. Keep a sample of what each customer received and when, in case of a dispute.

It is also kind to include one plain line in the last email that tells customers how to stop the subscription. It reduces complaints and chargebacks, and it builds goodwill that makes later restarts likelier.

Measuring whether the emails recover cards

Run the sequence for two full billing cycles before judging it. Track four numbers from your billing tool or a simple sheet:

1. Failed payments per month, as a share of charges.
2. Recovered within 14 days, as a share of failures. Split into those that recovered before email 2 (mostly retries) and those after (mostly emails).
3. Replies per 100 emails. A rise suggests confusion; read them.
4. Unsubscribes or complaints after emails 2 and 3. If these spike, soften the wording or cut email 3's frequency.

When one number looks poor, change one thing and wait a cycle. If email 1 gets opened but the link is rarely clicked, the problem is the button or the page. If it is not opened, the subject line needs work, and AI is good at generating five variants to test against each other. To judge a tool as a whole after a quarter, a 90-day review gives a simple keep, fix or cancel test, and a standing check by a person (see setting up human review without slowing down) stops a bad draft going out under your name.

Dunning questions from small subscription owners

How many dunning emails should I send?

Three is a sound default: a same-day notice, a reminder around day four or five, and a final warning a day or two before access ends. More than that tends to read as pestering, and fewer leaves little room for a customer who was away. Adjust the spacing to match your retry schedule.

Should dunning emails come from me or from the payment provider?

Use both carefully. Provider emails are reliable and carry a secure update link, but they sound generic. Your own emails can be warmer and more specific. If you send both, switch off duplicates so a customer does not get two notices on the same day.

Can AI write the whole sequence?

AI can draft the wording, the subject lines and the variants well. You still decide the timing, the access rules and the exact link, and you should read every email once before it goes live. Do not let AI invent a discount or a deadline you have not set.

Why do some failed payments never recover?

Some declines cannot be fixed by retrying, such as a lost or stolen card or a closed account, and the customer must supply a new card. Others recover after a retry at a better time. A good sequence handles both: a retry schedule for the soft failures and a clear update link for the rest.

Further reads

• AI Automation for Gyms: Failed Payments, Freezes and Win-Back Texts — A membership business's take on failed payments and freezes.
• E-Commerce AI Tools: 8 Jobs a Small Online Store Can Hand Over — Other store jobs AI can take over, with costs.
• Quote to Cash: Connect Quotes, Invoices and Payments With AI — Follow money from quote to cash, not only failed card charges.
• AI Accounts Payable: Approvals and Payment Runs Without Chaos — The supplier side of payments, for contrast.
• Best AI Chatbots for Small Shopify Stores (2026) — Handle the replies your dunning emails prompt with a chatbot.
• AI for Car Washes: Membership Marketing and Churn Messages — Turn a member export into segments, then draft win-back texts, cancellation-reason replies and plan offers for repeat single-wash customers.
• Tea Shop Marketing Ideas: Tasting Notes and Gift Sets Written With AI — Turn your own cupping notes into shelf cards and product pages, then price subscription tiers and gift sets by margin before AI writes a word of copy.
• Subscription Box Pricing: Build a Margin Model With AI — A worked margin model for a subscription box: product, packaging, postage, fees, churn and discounts, ending in a break-even subscriber count.
• AI for a Pet Food Business: Labels, Subscriptions and Customer Replies — Draft pet food labels, handle subscription pause requests, and answer ingredient enquiries using practical AI workflows.
• Can You Automate a B2B SaaS Business With AI? What to Hand Over First — A risk-ranked order for handing small B2B SaaS jobs to AI: support drafts first, onboarding next, billing chases last.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Stripe Billing documentation on Smart Retries and customer emails (docs.stripe.com) and Zapier's developer documentation on polling triggers, read 5 November 2026. Business figures in the examples are illustrative.