Skip to main content
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. DialNexa Fallback Settings panel showing a default dynamic variable name, default value, and save control.
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.

​
How DialNexa Fallback Settings Work

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.

​
Transfer Destination Defaults

Transfer settings deserve extra validation.

Pipe-separated numbers

Use a format such as +14155552671|+919876543210 when a transfer variable expects multiple destinations.

Representative routing

Check that each destination belongs to the intended handoff team.

Published version behavior

Fallback changes must be on the version that traffic actually uses.

Call History proof

Review transfer results after testing.

​
Fallback Mistakes

The dashboard can block saving when detected variables have empty defaults.
Replace examples with safe generic fallback values.
Bad recipient files happen. Defaults are insurance.
The voicemail message is scanned too. Add defaults for those placeholders.

Dynamic Variables

Understand placeholders.

Default Variables

See the data concept.

Call Transfer

Configure transfer destinations.