Airdun Autopilot: Fully Automated Payment Recovery

​

What Autopilot handles

• Detecting every new failed payment — Airdun listens to your Stripe webhook stream in real time. Every failure is caught when Stripe reports it, with no polling delay and no manual import.
• Opening and enriching recovery cases — a structured case is created immediately, populated with the failure reason, customer data, usage signals, and patterns from similar past cases.
• Running the sequence per case — the strategy algorithm designs a multi-touchpoint plan and executes it: messages in the customer’s language, at the right local time, through the right channels, using the right voice for each email.
• Stopping the sequence when payment succeeds — the moment Stripe confirms a successful charge, Airdun closes the case and cancels every pending message in the queue.
• Escalating cases that match your rules — when a new case matches an escalation rule you’ve defined (or looks like a fraudulent decline), Airdun flags it to your team in Slack and the in-app bell so you can step in alongside — or instead of — the automated sequence.

​

What you control

• Which channels are active — enable or disable email, in-app, and SMS independently. Airdun only uses channels you have switched on.
• Notification preferences — which case events notify you (case opened, recovered, lost, delivery failed) and whether each goes to Slack, the in-app bell, or both.
• Voices — the sender names, roles, and tones used for recovery emails.
• In-app wall — whether the wall is shown inside your product. By default it is a soft, dismissible prompt; you can optionally enable hard lock, which blocks the product after a delay you choose until the payment is fixed.
• Escalation rules — the conditions that flag a case to your team.