Payment recovery funnel
Shows how much failed payment revenue you get back, which retry attempt recovers it, and how much is still at risk.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Follow failed payments to recovery
Coming soonBlu builds a step
About this recipe
When to use it
A failed payment isn't automatically lost revenue - but it is if your recovery flow isn't working. This tracks per-attempt success rate through your dunning flow, plus the actual revenue-at-risk figure, from real billing events.
What it delivers
Builds a dunning recovery funnel from real billing events, tracking success rate at each recovery attempt and the total revenue-at-risk from unrecovered failures.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Shows how much failed payment revenue you get back, which retry attempt recovers it, and how much is still at risk.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Follow failed payments to recoveryCreate a Funnel report called "Payment Recovery Funnel". Steps: 1. Event "Invoice payment failed": "Payment Failed" 2. Event "Email opened" where the email is part of the dunning campaign (filter by Email sent.campaign_id matching dunning template): "Opened Recovery Email" 3. Event "View page" where Page URL contains "/billing" or "/account": "Visited Billing Page" 4. Event "Invoice paid" within 14 days of step 1 (same customer_id): "Payment Recovered" Conversion window: 14 days Breakdown: By "attempt_number" property on Invoice payment failed (1st attempt, 2nd, 3rd, 4th+): the canonical event has attempt_number Compare: Previous period (prior 14 days) For each step, also surface: - Revenue at stake at this stage (sum of amount_due_cents / 100 for users currently at this step) - Median time-to-recover for users who reach the final step Annotations: - Flag the recovery rate (Step 4 / Step 1) and benchmark against 70%. - Highlight which attempt_number has the lowest recovery rate (later attempts typically recover at lower rates: informs when to escalate to manual outreach). Surface the total revenue recovered vs. revenue lost in the period. Taxonomy notes: - Invoice payment failed has attempt_number, amount_due_cents, next_retry_at. - Invoice paid has amount_paid_cents. - "failure_reason" is not a property on Invoice payment failed; if reason-level breakdown is needed, use Charge failed.failure_code or failure_message instead.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /payment-failure-recovery-funnel in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 