Dunning Management Automation
A failed charge is not a lost customer. Not yet, anyway.
Unmeshed runs dunning management automation end to end. A failed payment triggers a scheduled retry instead of a single failed charge, and an account that exhausts every retry routes to a person for manual follow-up instead of quietly churning.
Built By
The team behind Netflix Conductor.
Now orchestrating workflows for teams across
- SGSingapore
- CACanada
- UKUnited Kingdom
- USUnited States
What Changes
A failed payment gets the same retry schedule every time. Only an exhausted account needs a person.
Trigger
A failed charge starts the workflow
The payment processor sends a webhook the moment a charge fails, and the workflow picks it up immediately instead of waiting for someone to notice.
- RULE
Payment failure webhook triggers the workflow
- RULE
No manual kickoff, no missed failures
- RULE
Every failure gets logged before the first retry fires
Trigger Path
Charge Failed
# payment_failed_webhook
Log Failure
# log_failure
Start Retry Schedule
# start_retry_schedule
Retry Loop
Backoff Wait
# backoff_wait
Retry Charge
# retry_charge
Log Attempt
# log_attempt
Retry
Each retry waits on a schedule
The workflow retries the charge on a backoff schedule, waiting longer between each attempt instead of hammering the card on repeat.
- RULE
Retry the charge on a scheduled backoff
- RULE
Wait between attempts, no custom timer code
- RULE
A successful retry closes out the run immediately
Decide
The retry count decides the path
A successful retry closes the workflow out, and the account stays current. An account that exhausts every retry attempt branches to a person instead of silently failing for good.
- RULE
Check whether the retry succeeded or the limit was reached
- RULE
A successful retry closes the run; the account stays current
- HUMAN
An exhausted account branches to manual follow-up
Decision Path
Check Retry Result
# check_retry_result
Close Run
# close_run
Manual Follow-Up
# manual_follow_up
Follow-Up Path
Team Follow-Up
# wait_for_follow_up
Clear or Hold Account
# resolve_account
Log Outcome
# log_outcome
Follow Up or Hold
An exhausted account waits for a real decision
An account that exhausts its retries sits with a person on your team, with the full retry history already attached. Once they act, the workflow resumes and either clears the account or places a hold.
- HUMAN
A team member reaches out or updates the payment method
- RULE
A successful follow-up resumes the workflow and clears the account
- RULE
Every attempt and every outcome is logged against the account
A failed charge is not a lost customer. The retry schedule runs on every failure, free. A person only gets involved once every retry is spent.
Retries on schedule
Backoff wait, zero model cost
Only exhausted accounts
Reach a person for follow-up
Full trace
Every attempt and outcome in one record
Integrations
Works with the payment processor and CRM you already run.
Trigger on failure
The webhook fires the workflow immediately; no one has to notice the failed charge.
Retry on backoff
Each attempt waits longer than the last, no custom timer code.
Escalate on exhaustion
Only accounts that spend every retry reach a person, with the full history attached.
Full trace
Every attempt and outcome is logged in one record.
Why It Holds Up in Production
Built so a failed charge never quietly becomes churn.
Schedule-based
Retries run on a backoff, not a single blunt attempt.
Context attached
A team member sees the full retry history before reaching out.
Full run history
Every attempt and outcome is logged and readable.
Resumable waits
Exhausted accounts wait on a real decision, no custom polling code.
Frequently asked questions
Still have questions? Talk to us.
Stop losing customers to a card that just expired.
Connect your payment processor, and this workflow handles the retry schedule, the backoff, and the escalation automatically.
Free tier, no credit card required