Your last payment didn’t go through. Would you tell us what went wrong?

When a payment fails, the billing tool retries for a couple of weeks and then cancels the subscription. Nobody writes to the customer. Most of the time they cancelled the card on purpose: it is a cancellation that never says so. This watches Stripe for payments that fail and, three hours later, writes them the same short note Cancel Emails writes, with the first line changed.

What it does

• Finds every subscription whose latest payment failed, on request or every hour on a verified schedule.
• Waits three hours after the payment fails, so a card that goes through on the first retry never gets a note.
• Writes one short note: sorry, thank you, would you tell us what didn’t work. No offer, no discount, no link, no reminder about the card.
• One note per customer, ever: never to someone Cancel Emails already wrote to.
• Leaves it in the sender’s Gmail Drafts until you turn on auto-send. Then it sends it itself, and only this note.
• Marks the customer’s row on the team’s customer list.

The reveal

A card fails on Tuesday morning. By lunch the customer has a four-line note from a real person on your team. The reply comes that evening: “Honestly, I cancelled the card because we stopped using it after the first week.” Now Why They Leave knows the real reason, and so do you.

Configuration

• Where payments fail: Stripe, read with the account you connect.
• Who sends the note: one person on the team, from their own account.
• The note: the four lines, as the team wants them.
• Auto-send: off until the sender turns it on in chat.
• How often: when you ask, or every hour if an available scheduler can run the work and you approve it.

What it doesn’t do

• It doesn’t send until you turn on auto-send.
• It doesn’t chase the payment. No card reminder, no link, no offer.
• It doesn’t change anything in Stripe. It only reads.
• It doesn’t write twice. One note per customer, ever.

Triggers

Runs when you ask (“whose payment failed”, “email failed payments”). Hourly checks need a verified scheduler and your approval; otherwise it runs a bounded check now and saves where it got to.