{{date}}. When a call starts, Deepslate replaces each variable with its value before the model sees the prompt.
Fields that support variables
Deepslate replaces variables in these fields only:
Other fields, such as the greeting (
systemPromptGreeting), are used as written.
Built-in variables
Both variables use German formatting and default to UTC.
Time zones
To use a different time zone, add a colon and the zone after the variable name:- An IANA time zone name, such as
Europe/BerlinorAmerica/New_York. The value follows daylight saving time. - A fixed UTC offset, such as
+01:00or-05:00. The value does not change with daylight saving time.
{{date:Pacific/Auckland}} is 4. November 2026.
User values
Outbound bots also take user values: call-specific data, such as the name of the person the bot calls. You define the keys once on the outbound bot and set the values for each planned call. Each key is a variable in the outbound bot’s system prompt template. For example, this system prompt template:date user value replaces {{date}}, but not {{date:Europe/Berlin}}.
Set user values in the dashboard
- Open the outbound bot. Under User Values, add each key and choose its type.
- Use each key as
{{key}}in the System Prompt Template. - Create a planned call for the outbound bot. Enter the values under Parameters for followed by the bot’s name.
Set user values with the API
- Define the keys in the agent’s
userValueTypes. See Create Agent. - Set the values in the task’s
userValues. See Create Agent Task.
Placeholders that stay unchanged
If Deepslate can’t resolve a placeholder, it leaves the text unchanged and the model sees the literal placeholder. This happens when:- The variable name is unknown, such as
{{foo}}, or the planned call has no value for the key. - The time zone is unknown, such as
{{time:Mars/Olympus}}. - The time zone is empty, such as
{{date:}}.
${{date}} becomes the literal text {{date}}. To write a dollar amount, put the currency after the value as a word, for example {{price}} dollars.