> ## Documentation Index
> Fetch the complete documentation index at: https://docs.airdun.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Airdun Autopilot: Fully Automated Payment Recovery

> What Autopilot handles on its own — detection, enrichment, sequencing, retries, auto-stop — and which settings remain under your control.

Autopilot is the mode Airdun runs in by default. Once Stripe is connected and your channels are active, Airdun monitors every charge, opens a case when one fails, builds and executes the recovery plan, and closes the case when the payment succeeds. You set the configuration; Airdun operates within it.

## 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 sender persona at each step.
* **Stopping the sequence when payment succeeds** — the moment Stripe confirms a successful charge, Airdun closes the case and cancels every pending message or retry in the queue.
* **Alerting you on high-value escalations** — when a case opens for an account above your configured MRR or tier threshold, Airdun alerts your team so you can act personally alongside the automated sequence.

## What you control

* **Which channels are active** — enable or disable email, in-app, SMS, and WhatsApp independently. Airdun only uses channels you have switched on.
* **Notification preferences** — which events trigger alerts (case opened, case recovered, high-value escalation) and where they go (email, Slack, or both).
* **Sender personas** — the team member names and avatars Airdun uses at each step of a sequence.
* **In-app wall behavior** — whether Airdun shows a payment wall inside your product, and whether it is a soft or hard block.

<Note>
  Autopilot never cuts an active recovery sequence mid-flight. If a case is in progress when your account reaches a plan limit, Airdun sees that sequence through to completion.
</Note>

<CardGroup cols={2}>
  <Card title="Set Up Your Channels" icon="satellite-dish" href="/configuration/channels-setup">
    Activate and configure email, in-app, SMS, and WhatsApp.
  </Card>

  <Card title="Configure Notifications" icon="bell" href="/configuration/notifications">
    Choose which events trigger alerts and set your high-value escalation thresholds.
  </Card>
</CardGroup>
