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

# Keep Your Brand Voice Across Every Recovery Message

> What you configure to control how recovery messages read: sending domain, brand tone, sender personas, and auto-translation.

Recovery messages are sent from your domain under your sender names, and do not display the Airdun name. Four things control how they read.

## Sending domain

Emails are sent from your own domain, not from `airdun.com` or a shared sending address. Each sender address requires SPF and DKIM records on your domain before it can be used — see [Sender Personas](/configuration/sender-personas).

## Brand tone

You define the tone Airdun applies when generating messages. It is applied consistently across every channel and every step of the sequence.

## Sender personas

Rather than sending everything from one address, you configure several team personas, and Airdun assigns one per stage of the sequence. A typical arrangement:

* **First touch** — the customer's account manager
* **Escalation follow-up** — a support lead
* **Final notice** — a billing contact

Each persona has its own name, email address, and title, all on your domain. Airdun selects which persona appears at each touchpoint; you cannot assign them per message.

## Auto-translation

Airdun detects each customer's language and translates messages automatically. You configure your voice once in your primary language. The configured tone is preserved across languages — a formal brand stays formal in French, a conversational brand stays conversational in Portuguese.

<CardGroup cols={2}>
  <Card title="Sender Personas" icon="user-group" href="/configuration/sender-personas">
    Set up personas and their SPF/DKIM authentication.
  </Card>

  <Card title="Channel Setup" icon="sliders" href="/configuration/channels-setup">
    Configure sending domains, tone settings, and channel-level preferences.
  </Card>
</CardGroup>