Skip to main content
About the Resource Center

Architect built-in variables

Built-in variables provide information about things the system tracks automatically, such as the caller’s phone number, or the contact list associated with an outbound flow. This article lists the default system variables built into Architect for each type of flow. You can also access descriptions in the embedded Function and Operator help.

Architect contains various system-scoped variables that begin with Min or Max. These variables hold the minimum and maximum value allowed for certain data types and are similar to constants in many programming languages. In Architect, they are built-in and read-only system variables. For example, the System.MinDateTime variable holds the minimum allowed value of a DateTime data type, which is January 1st, 1800 at 12:00:00 a.m.

Showentries
NameTypeCollection?Read Only?Description
Call.Ani
String
No
Yes
The caller’s origination phone number for the active call (Automatic Number Identification).
Call.CalledAddress
String
No
Yes
The called address that caused the caller to enter this flow. For a new inbound call, this value is the same as Call.CalledAddressOriginal, but changes for a flow entered by a transfer, for example.*
Call.CalledAddressOriginal
String
No
Yes
The called address received when the call first entered the system; typically the phone number dialed by the caller to reach the system. For a specified call, this value never changes.*
Call.ConversationID
String
No
Yes

The conversation identifier for the active call. 

Call.ExternalContactId
String
No
Yes

A unique identifier for the external contact.

Note: Architect does not support multiple external contact IDs. It selects the first contact on the conversation based on startDate. 

Call.ExternalTag
String
No
Yes

The external tag for the active call.

Call.Language
String
No
Yes

The IETF language tag lowercase string value set on the current interaction. 

Note: Within call flows, construct comparisons with IETF language tag string values in a case-insensitive manner.

Call.RemoteName
String
No
Yes
Remote name for the active call.

Call.UUIData

String
No
Yes

Reflects the user-to-user call information (UUI) set on the call.

Note: When you transfer a call from flow to flow, or when the flow disconnects, the variable value does not automatically follow to the next flow.

Flow.IsTest
Boolean
No
Yes
Indicates whether the flow is running in debug mode.
*Note: Various actions cause a call to enter a flow, including, but not limited to:
  • An inbound call arrives.
  • A call transfers to a flow by another flow.
  • A call transfers to a flow by a user. 

Each flow makes available to the flow author two "called address" variables. Consumers typically see these addresses as phone numbers, but they can contain other identifies like a SIP address used for voice conversations over the Internet.