FINANCE

Agentic Dunning Recovery Playbook

An agent investigates each failed Stripe payment, decides retry vs. outreach vs. escalation from the customer's full context, and drafts a tailored CSM handoff in Outlook.

CategoryFinance
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe invoice.payment_failed webhookStripeStripe
  • ActionGather billing history from PostgresPostgreSQLPostgres
  • ActionPull account context from HubSpotHubSpotHubSpot
  • LogicAgent decides retry, self-serve, or escalate
  • ActionReschedule retry in Stripe when chosenStripeStripe
  • OutputSend tailored CSM handoff via OutlookOutlook

What it does

Instead of a fixed retry ladder, this workflow hands each failed payment to an agent that reasons over the customer's billing history, plan value, support sentiment, and decline reason, then chooses the right recovery action and drafts the human handoff.

When to use it

Use it for high-value accounts where a one-size-fits-all dunning sequence is too crude — for example, where a hard decline on an enterprise plan warrants immediate personal outreach but a soft decline on a small plan can just retry.

How it works

  1. 1A Stripe `invoice.payment_failed` webhook starts the run with invoice and customer IDs.
  2. 2The agent pulls billing history and plan tier from Postgres and the account record and recent notes from HubSpot.
  3. 3It reasons over decline code, account value, and tenure to choose: schedule a smart retry, send a self-serve update link, or escalate now.
  4. 4For retries it calls Stripe to reschedule; otherwise it proceeds to handoff.
  5. 5It drafts a context-rich, account-specific CSM email and sends it via Outlook for the owner to act on.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  4. 4
    Connect OutlookMail, calendar, contacts.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.