> ## 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.

# Playground: Test Recovery on Fake Data Safely

> The Airdun playground fires fake payment failures through the real recovery pipeline on sandbox data — no customer is contacted and your live configuration is never changed.

The playground lets you fire a **fake payment failure** through Airdun's **real** recovery pipeline and watch the strategy it produces — on sandbox data, with no customer ever contacted. Use it to see how the [recovery strategy](/how-it-works/recovery-strategy) reacts to a given failure, customer, and channel setup before it ever runs on a live case.

<Note>
  Everything in the playground is a sandbox. No real customer is messaged, nothing is created in Stripe, and your live [Auto-Pilot](/how-it-works/autopilot) configuration is never modified — the panel overrides are an overlay that applies to test runs only.
</Note>

## Before you start

The playground builds fake customers and invoices **on top of your Stripe connection** — nothing is written to Stripe itself. If Stripe isn't connected yet, you'll be prompted to [connect it](/quickstart) first.

## The three parts of the page

The playground has a configuration panel on the left, and the test composer plus the runs list on the right.

### 1. Sandbox configuration

The left panel mirrors your live settings so you can tweak them **for the test only**:

* **Channels** — turn channels on or off for this run. Coming-soon channels (e.g. WhatsApp) appear but can't be enabled. See [Channels](/features/channels).
* **Business context** — override the product and company description the model writes against. See [Business Context](/configuration/business-context).
* **Autopilot settings** — language/timezone, payment-failure consequences, and escalation, exactly as on the live page. See [Autopilot Settings](/configuration/autopilot-settings).
* **Voices** — adjust the email sender identities used to write recovery emails. See [Voices](/configuration/voices).

Any field you change shows a **Modified** badge and can be reset. These overrides never touch your live workspace — resetting them or leaving the page changes nothing in production.

### 2. Launch a test

Compose the fake case, then fire it:

* **Scenario** — the failure type to simulate (card declined, insufficient funds, and so on). Use **Generate test data** to fill everything with a random, realistic case.
* **Product, price, currency, interval** — the subscription that failed. Pick one of your real Stripe products, a preset, or a custom one.
* **Customer name, email, language** — the fake customer. Language drives translation; **Unknown** lets the [language resolver](/configuration/autopilot-settings) fall back on its own.
* **First payment failure / After trial** — whether this is the subscription's very first charge (a cold signup, or one right after a free trial). This shifts the strategy from onboarding-friendly to standard recovery.
* **Customer enrichment** — optionally provide the same fields your [enrichment endpoint](/enrichment) would return, to see how they change the messages.

Press **Fire test** and Airdun generates the strategy through the live pipeline. Watch it appear in the runs list below.

### 3. Test runs

Each fired test appears in **Test runs** with its status. Open one to inspect the full generated strategy — every touchpoint, its channel, timing, and the message copy. **Reset all** deletes every test run (and their strategies and steps); it never touches your live data.

## Real sending

By default, nothing leaves Airdun — the run generates a strategy without delivering anything. The **Real sending** section lets you receive the actual messages for inspection:

* **Test emails** are delivered to an address **you** choose, stamped `[TEST]` — never to the fake customer.
* **WhatsApp / SMS** can be really sent, but only to a phone number **you** enter, and only if that channel is connected.

<Warning>
  Real WhatsApp and SMS sends go to the exact number you type. Always use **your own** number, in E.164 format (e.g. `+33612345678`) — never a real customer's.
</Warning>

## What the playground does not do

* It does not message your real customers.
* It does not create or charge anything in Stripe.
* It does not change your live channels, voices, business context, or autopilot settings.

<Note>
  Because the pipeline is the real one, a playground run is the closest preview you get to how a live case would actually be handled. For the mechanics behind what you see, read [Recovery Strategy](/how-it-works/recovery-strategy) and [Recovery Cases](/how-it-works/recovery-cases).
</Note>