Dunning & Collections Agent
Failed and expiring subscriptions get one respectful, personalized recovery email each — segmented by value, capped by policy, staged for your approval, retries proposed never fired.
This recipe works the at-risk money: Stripe subscriptions with failed or expiring payment methods, upcoming card expiries, and overdue invoices — each with the exact amount, failure reason, and attempt count. Customers are segmented into value tiers using real numbers (MRR, lifetime spend, failure recency, prior recovery success), and a hard frequency cap (one touch per rolling 14 days, two per episode by default) is computed before any drafting — anyone at cap, opted out, or unverifiable is held with the rule shown, fail-closed. Each in-cap customer gets a personalized draft that names their actual plan, amount, failure reason, and the exact fix step, with tone scaled to tier and retry timing proposed as advisory math, never executed. Everything stages behind one approval gate as Gmail drafts, suppression and caps are rechecked at dispatch, and reruns within the window update the existing draft instead of double-touching a customer.
How it runs
Multi-agent orchestration — here's the flow, step by step.
Pull failed/expiring subscriptions, upcoming card expiries, failed payment attempts, and overdue invoices from Stripe with exact amounts, failure reasons, and attempt counts. Reads the read-only Stripe ledger via stripe_list_charges and stripe_get_customer only — payment mutation tools are never in scope for this phase.
payment scannerEnrich each record with plan, term, MRR contribution, and current subscription state.
subscription analystResolve dunning history, collections-hold and opt-out flags, and account owner per customer; fail closed — unverifiable customers are held with a named reason.
crm scannerSegment customers into high-value / standard / at-risk-churn tiers using lifetime spend, current MRR, failure recency, and prior recovery success — math shown.
clv analystCompute the frequency-cap ledger (one touch per rolling 14 days, two per episode) before drafting and exclude anyone at cap with the rule shown.
workflow orchestratorDraft one personalized dunning email per in-cap customer: exact amount, invoice/subscription reference, failure reason, fix step, and tier-scaled respectful tone.
email writerCompute the recommended card-retry schedule per failure reason and stage it as an advisory note — never executable.
payment followup orchestratorStage all drafts as Gmail drafts behind one approval gate; recheck suppression and caps at approval and immediately before dispatch, holding failures with named reasons.
distributorAssemble the recovery summary, drafts, held list with exclusion rules, retry-timing proposals, and dispatch receipts.
report formatterRequired Agents
9- payment-scanner
- subscription-analyst
- clv-analyst
- crm-scanner
- email-writer
- payment-followup-orchestrator
- workflow-orchestrator
- distributor
- report-formatter
Connections
Required
Optional
What it does
- Finds failed/expiring subscriptions, card-expiry risk, and overdue invoices from Stripe
- Value segmentation with the math shown — MRR, lifetime spend, failure recency
- Hard dunning-frequency cap computed before drafting (1 per 14 days, 2 per episode default)
- Fail-closed suppression: unverifiable dunning history = held with a named reason
- Personalized drafts naming amount, invoice/subscription, failure reason, and fix step
- Tone ladder per tier — relationship-preserving for high-value, never threatening
- Card-retry timing proposed as advisory math, never executed
- Staged Gmail drafts behind one approval gate, rechecked at dispatch
Example prompt
Which subscriptions are about to fail or have failed payments this month? Draft recovery emails for each — skip anyone we've already emailed recently.
Ready to deploy Dunning & Collections Agent?
Start free. One click, full agent orchestration.
Get Started Free →