Dunning is the process of recovering revenue from failed payments — through retries, email reminders, or direct outreach. A well-tuned dunning process recovers 30–60% of involuntary churn that would otherwise be lost.

Failed payments alert

Real-time alert when a paying customer's card fails. AI surfaces the account, ARR, reason, and next step for finance and CS.

Use this template How automations work

Runs daily Data change Delivered to Slack

Active

Trigger

Runs daily

Instructions

Every 30 minutes, check for new failed payments in Stripe (or other billing systems).

Delivery

Slack

Example output

A realistic sample of what this automation delivers — your version draws on your data.

Failed payments alert Runs daily · Sent to Slack

Sample output

Failed payment — NorthwindCo ($72K ARR)

Reason: card_declined (insufficient funds).
Charge: $6,000 (annual renewal), May 25 at 03:14 UTC.
Customer state: Healthy. CSAT 9/10, 38 weekly active users, no support tickets.
History: First failure on this account. Smart Retries scheduled for May 27 and May 30.

Recommended next step. Email Lara (billing contact) by EOD. Most renewals like this are AP timing — a one-line note avoids the dunning sequence escalating to her CTO.

The prompt

Copy, paste, customize.

Drop this into a Basedash automation. AI fills in the numbers from every source you've connected.

Instructions

Every 30 minutes, check for new failed payments in Stripe (or other billing systems).

For each failure on a paying account, post a single Slack message in #revenue-alerts:

⚠️ **Failed payment: <Account name> ($<ARR>)**
- Reason: <Stripe failure code, plain English>
- Card last 4: <****>
- CSM: <owner>
- Recommended: <one sentence — e.g., update card via portal, contact AP, retry in 24h>

Skip free-tier failures and any failure that has been retried successfully within 1 hour. Group multiple failures from the same account into a single message.

Data sources