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

# DialNexa Fallback Settings

> Understand DialNexa fallback settings for default dynamic variables, missing launch values, transfer destinations, and safe variable defaults.

DialNexa fallback settings let users define default dynamic variable values for an agent version. These defaults are used when a prompt, welcome message, voicemail message, batch file, workflow lead, or API call references a variable but no call-specific value is supplied.

<img src="https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/agent-fallback-settings-panel.png?fit=max&auto=format&n=0efoAN-6So4r-6NC&q=85&s=fcc9e6cc0bb764fc2d38fa6d107dc5d4" alt="DialNexa Fallback Settings panel showing a default dynamic variable name, default value, and save control." style={{ width: '100%', maxWidth: '800px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="686" height="1384" data-path="images/documentation/screenshots/agent-fallback-settings-panel.png" />

<Warning>
  A default value should be safe to say out loud. If you would not want the caller to hear it, do not use it as a fallback.
</Warning>

## What The Panel Does

The builder detects placeholders such as `{{first_name}}` in prompt-related text and lists them as default dynamic variables. Users can enter fallback values, save them to the agent version, and use those values when the launch surface does not provide a replacement.

## Default Variable Sources

Fallback settings protect multiple launch paths.

| Variable appears in      | Why fallback matters                                                   |
| ------------------------ | ---------------------------------------------------------------------- |
| Prompt text              | Prevents awkward missing personalization during the main conversation. |
| Welcome message          | Protects the first spoken sentence.                                    |
| Voicemail message        | Prevents voicemail from containing unresolved placeholders.            |
| Call transfer path       | Transfer destinations may require a formatted default value.           |
| Batch or workflow launch | Protects against incomplete CSV rows or lead variables.                |

## Transfer Destination Defaults

Transfer settings deserve extra validation.

<CardGroup cols={2}>
  <Card title="Pipe-separated numbers" icon="phone-forwarded" href="/calls/call-transfer">
    Use a format such as `+1234567890|+1098765432` when a transfer variable expects multiple destinations.
  </Card>

  <Card title="Representative routing" icon="users" href="/calls/call-transfer">
    Check that each destination belongs to the intended handoff team.
  </Card>

  <Card title="Published version behavior" icon="git-commit" href="/agents/agent-versions-and-publishing">
    Fallback changes must be on the version that traffic actually uses.
  </Card>

  <Card title="Call History proof" icon="activity" href="/monitoring/retries-transfers-and-audio-cache">
    Review transfer results after testing.
  </Card>
</CardGroup>

## Fallback Mistakes

<AccordionGroup>
  <Accordion title="Leaving an empty value">
    The dashboard can block saving when detected variables have empty defaults.
  </Accordion>

  <Accordion title="Using sample data in production">
    Replace examples with safe generic fallback values.
  </Accordion>

  <Accordion title="Assuming CSV overrides always exist">
    Bad recipient files happen. Defaults are insurance.
  </Accordion>

  <Accordion title="Forgetting voicemail variables">
    The voicemail message is scanned too. Add defaults for those placeholders.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Dynamic Variables" icon="braces" href="/agents/dynamic-variables">
    Understand placeholders.
  </Card>

  <Card title="Default Variables" icon="database" href="/data/default-variables">
    See the data concept.
  </Card>

  <Card title="Call Transfer" icon="phone-forwarded" href="/calls/call-transfer">
    Configure transfer destinations.
  </Card>
</CardGroup>
