Airdun Autopilot: One Autopilot per Kind of Failed Payment

Airdun recovers three kinds of failed payment, and runs a separate autopilot for each one. Each autopilot has its own messages, channels, rules, and status, so you can run Renewals with one setup and Free trials with another, or turn on only the ones you need. You find all three under Autopilot in the sidebar. Each card shows its status, its open cases, and what is left to set up.

​

The four states

​

Turn on, go live, pause, turn off

• Turn on moves an autopilot from Off to Setting up. Nothing is sent yet. Cancel setup takes it back to Off.
• Go live is available once every required step of the checklist is done. From then on, every new failed payment of this kind opens a case.
• Pause asks what to do with the cases already open:
  • New cases only: no new case opens; open cases continue until they end.
  • Everything: no new case opens, and Airdun stops working on open cases. They pick up again when you Resume.
• Turn off also asks:
  • Let open cases finish: open cases continue until they end.
  • Stop everything now: Airdun stops working on open cases and hides the in-app wall on them. Escalated cases stay with your team.
  After Let open cases finish, Stop the remaining cases… stops the cases still running and hides the in-app wall on them. To turn an autopilot back on after turning it off, you go through its setup again.

Each use case changes state on its own: pausing Renewals has no effect on Free trials.

​

The setup checklist

The checklist floats at the bottom of the app while something is left to set up. It has two parts:

• Workspace steps, shared by every use case and done once: confirm your Stripe settings, review your Recovery Profile, verify your sending domain, describe your business, and the recommended ones (customer enrichment, installing the in-app wall script on your site).
• Steps of each use case, such as setting up its messages, describing what happens when payment fails, and confirming its sending rules.

Steps marked Required must be done before Go live. Recommended steps never block going live; they stay in the list until you do them. Each step links to the page where you do it.

​

What Airdun handles on its own

Once an autopilot is live:

• Detecting every new failed payment of its kind from your Stripe webhooks, as Stripe reports them.
• Opening and enriching a recovery case with the failure reason, the customer data, and your enrichment data.
• Reaching out: the right message, on the right channel, at the right time, in the customer’s language and time zone. New customers follow a fixed sequence instead: one email, then one text if the invoice is still unpaid, within the day the payment failed.
• Stopping as soon as the payment succeeds: the case closes and every pending message is canceled.
• Escalating cases that match your rules: Airdun sends nothing on them and alerts your team.

​

What each use case lets you set

Each use case has its own page under Autopilot, grouped like this:

• Outreach: its Messages (your own sequence of templates, or the AI writer with your voices) and the channels it uses (Email, SMS, WhatsApp).
• In your app: the in-app wall, with its own wording, hard lock, and appearance.
• Payment: adaptive retries, charge attempts placed by Airdun on top of Stripe’s own retries.
• Rules: sending rules, payment failure consequences, and escalation rules. See Use Case Settings.

A feature that does not apply to a use case is not shown for it. New customers has no in-app wall, no consequences, no adaptive retries, no AI writer, and no WhatsApp, because its sequence ends within the day. The payment failure consequences and the wall’s custom CSS can be copied from another use case with Import from another use case. Nothing stays linked after the import.