Default Variable Behavior
Defaults are saved per agent version.| Behavior | Meaning |
|---|---|
| Detected from text | Placeholders in prompt, welcome, and voicemail text create variable rows. |
| Saved to version | Defaults are patched to the selected agent version. |
| Used as fallback | If launch data omits a value, the default can be used. |
| Transfer validation | Transfer destination variables can require a specific number format. |
| Published state | Editing 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
Do not use secrets
Do not use secrets
Defaults can appear in prompts, logs, or exports.
Use neutral fallback text
Use neutral fallback text
For a missing first name, a generic greeting may be safer than an incorrect name.
Retest after changing defaults
Retest after changing defaults
Published routes may still use another version.
Related Reading
Dynamic Variables
Understand call-time values.
Fallback Settings
Edit defaults in the builder.
Batch Recipient Files
Use variables in CSVs.