Failed-Payment Recovery Brief

Goal

Generate a unified failed-payment recovery brief that ranks accounts by recovery priority, flags write-off approvals, provides tailored customer outreach drafts, and includes a verify-complete checklist for each account plus a portfolio summary.

Inputs to gather

• Scope and filters (single account or batch, days-past-due threshold, geos) — defines which records to process.
• Stripe export files (customers, subscriptions, invoices, payment_intents/charges) — primary source for payment failures and links.
• Invoice records export (CSV/XLS/JSON/PDF metadata) — validates amounts, dates, currencies.
• CRM notes export (owner, recent notes, tags, last contact dates) — informs outreach tone and next steps.
• Customer email threads export (latest inbound/outbound content and timestamps) — gauges engagement and sentiment.
• Write-off & escalation policies (small-balance limit, max days outstanding, approver list) — drives approval flagging.
• Priority-scoring weights, if different from defaults — affects recovery ranking.
• Communication tone guidelines or preferred templates — ensures message consistency.
• Reporting currency — needed for monetary normalization.

Before doing any work, ask the user for these inputs in ONE message. Skip anything they already provided. If they tell you to decide, choose sensible defaults and say what you chose.

Workflow

1. Clarify scope and policies with the user based on the gathered inputs; confirm any missing details.
2. Use Read to load the Stripe, invoice, CRM, and email files the user supplies.
3. Normalize all datasets into canonical fields (account_id, invoice_id, amounts, dates, payment method, etc.).
4. Reconcile and deduplicate records, preferring the most recent Stripe data, then invoice data, then CRM/email context.
5. Determine each account’s status: Current, Past Due (1-7 d), Dunning (8-21 d), Delinquent (22-60 d), Severely Delinquent (>60 d), Canceled with Balance, Disputed, or Churned/Closed; identify primary failure driver.
6. Compute a 0-100 recovery-priority score per account using default weights (40 % MRR/ARR, 25 % delinquency_days inverse, 15 % engagement, 10 % historical segment recovery rate, 10 % payment-method risk) unless the user supplied alternatives; convert to High/Medium/Low tiers.
7. Flag approval-needed write-offs when policy thresholds are met (small balance, >120 d age, disputes, legal holds, etc.), citing evidence and recommended approver.
8. Pause and show the user the portfolio summary (statuses, scores, top-10 list) for confirmation before drafting outreach.
9. Draft ≤180-word customer follow-up emails tailored to each failure reason and the user’s tone guidelines; include hosted_invoice_url, update-payment link, deadline, and support offer.
10. Build a verify-complete checklist for every account covering identity reconciliation, amounts, tax, links tested, dunning settings, compliance, owner assignment, and next follow-up date.
11. Assemble the final brief: portfolio header, per-account sections (Summary, Key Facts, Priority, Flags, Next Action, Email Draft, optional Call Script for High priority, Checklist, Source References).
12. Run quality and compliance checks: redact sensitive PII, validate links, sanity-check amounts/dates, respect regional collection rules.
13. Use Edit to save the report as markdown; offer CSV/JSON extracts of the summary table if requested.
14. Present the deliverable to the user and ask if further adjustments are needed.

Output

A markdown report containing:
• Portfolio summary (counts by status & priority, total ARR/MRR at risk, ranked top-10 accounts).
• For each account: Summary, Key Facts table, Recovery Priority score & tier, Approval-Needed Flags with reasons, Recommended Next Action, Tailored Follow-Up Email Draft, optional Call Script, Verify-Complete Checklist, and Source References.
Offer an accompanying CSV/JSON of the summary table on request.