Collect / Recover
Pre-dunning card update
The charge that fails next week doesn't have to. The agent sees the expiring card today and gets it fixed before dunning ever starts.
What it does
Most involuntary churn is visible in advance: a card expiring before the next renewal, a history of soft declines, a charge date approaching an account that looks unlikely to clear it. By the time dunning emails start, the relationship is already strained and the recovery odds are falling. The agent works upstream of the failure: it flags the upcoming charge, gets the card on file updated through a secure link, offers auto-pay or direct-debit enrollment at natural moments such as the welcome conversation, and sends payment reminders timed by judgment rather than by a fixed blast schedule.
How it works
- 1Trigger. time and risk signals: card expiry inside the renewal window, an upcoming charge date, prior soft declines, or a payment-risk score crossing its threshold.
- 2Decision. the agent weighs the signal against the customer's memory and history: has a charge failed before, which channel do they actually respond on, is a reminder helpful here or just noise. The quality judge gates every message before it is sent.
- 3Action. a short, specific nudge on the customer's preferred channel, carrying a secure link to the payment provider's hosted card-update page; the agent never touches card data itself. At the welcome moment, the same flow offers auto-pay or direct-debit enrollment through the same secure hand-off.
- 4Follow-through. a completed update writes back to billing and cancels any pending reminders for that cycle. If the charge date passes cleanly, the loop closes silently. If the charge fails anyway, the full context hands off to failed-payment recovery so the customer never repeats themselves.
Configuration
How the agent is wired for this use case.
- Billing platform · read subscription state, payment-method metadata, and the upcoming charge schedule; write back a completed update
- Payment provider · serve the hosted card-update page and the auto-pay / direct-debit enrollment page; the agent never touches card data
- Messaging channel · send a short, specific nudge on the customer's preferred channel and offer enrollment at the welcome moment
- Customer memory store · read channel preference and decline history to decide whether a reminder helps
- Failed-payment recovery flow · hand off full context if the charge fails anyway
What you need
The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.
Signals
card-expiry dates inside the renewal window, upcoming charge schedule, soft-decline history, payment-risk scores
Data
subscription and billing state, payment-method metadata (expiry, type), customer memory, channel preference and consent
Guardrails
secure payment hand-off only, no card data in any conversation; judge gating and frequency caps on reminders; reminder cancellation once the card is updated or the charge clears; risk-score outreach bounded to payment topics
Metrics it moves
- involuntary-churndown: the failure is prevented upstream, so the dunning funnel never has to fire
- renewal-rateup: charges clear on schedule because the payment method is healthy before the charge date
- contact-ratedown: auto-pay enrollment at the welcome moment removes a whole class of future payment conversations
Related use cases
See it on your own customer journey
Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.
Book a demo