Skip to main content
DialNexa default variables are fallback values saved on an agent version for dynamic placeholders. They protect calls when the launch surface does not provide a value for a placeholder used in the prompt, welcome message, voicemail message, transfer path, batch row, or workflow lead.
A default value should sound acceptable to a caller, not just acceptable to a form validator.

Default Variable Behavior

Defaults are saved per agent version.
BehaviorMeaning
Detected from textPlaceholders in prompt, welcome, and voicemail text create variable rows.
Saved to versionDefaults are patched to the selected agent version.
Used as fallbackIf launch data omits a value, the default can be used.
Transfer validationTransfer destination variables can require a specific number format.
Published stateEditing may be blocked on published versions.

Where Defaults Prevent Bad Calls

Defaults are most useful where data quality varies.

Batch CSV gaps

Protect incomplete recipient rows.

Manual test calls

Avoid saying unresolved placeholders during tests.

Voicemail messages

Prevent awkward voicemail output.

Workflow leads

Keep workflow actions from missing important text values.

Default Variable Rules

Defaults can appear in prompts, logs, or exports.
For a missing first name, a generic greeting may be safer than an incorrect name.
Published routes may still use another version.

Dynamic Variables

Understand call-time values.

Fallback Settings

Edit defaults in the builder.

Batch Recipient Files

Use variables in CSVs.