Built-in variables provide information about objects that the system tracks automatically, such as the agent’s name or duration of the current call. For example, if you select Scripter.Agent Name from the list, Scripts inserts a placeholder for that variable into the component. Two sets of curly braces enclose the variable name: {{Scripter.Agent Name}}.

Built-in variables are available when a read-only text, button, checkbox, radio button, link, or markdown has focus in the script editor. 

For a list of built-in variables, click Variables . You can mix manually typed text with variables. For example:

Outstanding agent {{Scripter.Agent Name}} has been on this call for {{Scripter.Agent Call Duration}} minutes.

Selectable variables

• Variables with the Scripter prefix are available to all scripts, whether inbound or outbound.
• Variables with the Outbound prefix insert placeholders for columns in the contact list that is associated with the script. Outbound variables only appear if you enable a script’s Outbound property.
• Custom variables that you create.

Script variables

• {{Scripter.Agent Call Duration}}—Talk time that the agent was on the call.

• {{Scripter.Agent Call Start Time}} / {{Agent Interaction Start Time}}—Time when the call was connected to the agent, using the local time on the agent’s computer. This variable cannot be used for workitems.

• {{Scripter.Agent Communication ID}}—The identification number of the agent’s current communication.
• {{Scripter.Agent Email}}—Agent’s email address.
• {{Scripter.Agent Formatted Number}}—Formatted number that the contact sees as the agent’s caller identification number.
• {{Scripter.Agent Locale}}—Agent’s chosen language code, such as: en-US: English; fr: French; and es: Spanish, based on the agent’s language selection.
• {{Scripter.Agent Id}}—Agent’s Genesys Cloud ID (UUID).
• {{Scripter.Agent Name}}—Name entered for the agent user.
• {{Scripter.Agent Participant ID}}—Agent’s identification number.
• {{Scripter.Customer Call Duration}}—Total time the customer has been on the call.
• {{Scripter.Customer Call Start Time}} / {{Customer Interaction Start Time}}—Time when the call started. (Using the local time on the agent’s computer.)

• {{Scripter.Customer Communication ID}}—Identification number of customer’s current communication.
• {{Scripter.Customer Formatted Number}}—Customer’s formatted phone number.
• {{Scripter.Customer Participant ID}}—Customer’s identification number.
• {{Scripter.Interaction Id}}—Unique identification number assigned to the interaction. This variable is the same as the conversationID in the Genesys Cloud API.
• {{Scripter.Interaction State}}—Current state of the interaction. See Interaction states. 
• {{Scripter.Interaction Type}}—Type of interaction: for example, call, chat, email, or others.
• {{Scripter.Is Barging}}—Agent is barging in on a conversation.
• {{Scripter.Is Being Consulted}}—Agent is consulting in a conversation.
• {{Scripter.Is Coaching}}—Agent is coaching a conversation.
• {{Scripter.Is Consult Initiatior}}—Agent called another participant to consult on a conversation and the consult is ongoing.
• {{Scripter.Is Monitoring}}—Agent is monitoring a conversation.
• {{Message.Message Type}}—Message type for messaging services: for example, SMS, Facebook, twitter.
• {{Scripter.Page Is Invalid}}—True or false, whether the script contains an error.
• {{Scripter.Queue ID}}—Identification number of the queue this interaction is on.
• {{Scripter.Queue Name}}—Name of the queue this interaction is on.
• {{Scripter.Raw Interaction State}}—Untranslated current state of the interaction. See Interaction states. 
• {{Scripter.Raw Interaction Type}}—Untranslated type of interaction: for example, call, chat, email, or others.
• {{Scripter.Script ID}}—Identification number of this script.
• {{Scripter.Raw Agent Call Start Time}} / {{Scripter.Raw Agent Interaction Start Time}}—Untranslated call time in numeric format.
• {{Scripter.Raw Customer Call Start Time}} / {{Scripter.Raw Customer Interaction Start Time}}—Untranslated call time in numeric format.
• {{Scripter.Raw Agent Call Duration}}—Untranslated call duration in numeric format, in milliseconds.
• {{Scripter.Raw Customer Call Duration}}—Untranslated call duration in numeric format, in milliseconds.

Outbound variables

• {{Outbound.Campaign ID}}—Identification number of the campaign associated with this script’s Outbound property.
• {{Outbound.Campaign Name}}—Name of the outbound campaign associated with this script’s Outbound property.
  Note: To access a campaign’s name for the Outbound.Campaign Name variable, users must have the Outbound > Campaign > View  permission and the Outbound > Campaign > Search permission.

• {{Outbound.Contact ID}}—Identification number of the outbound contact.

Chat variables

• {{Chat.Chat Room ID}}—Identification number of the chat room.
• {{Chat.Customer Chat ID}}—The Genesys Cloud identification number for this chat interaction. The Genesys Cloud web chat widget passes the values for the following variables. If your web chat developers do not assign values to them, they do not have a value.
• {{Chat.Customer Email}}—The customer’s email address. 
• {{Chat.Customer First Name}}—The customer’s first name.
• {{Chat.Customer Last Name}}—The customer’s last name.
• {{Chat.Customer Street}}—The customer’s street.
• {{Chat.Customer City}}—The customer’s city.
• {{Chat.Customer Postal Code}}—The customer’s postal code, for example: 50163.
• {{Chat.Customer State}}—The customer’s state.
• {{Chat.Customer Phone Number}}—The customer’s phone number.
• {{Chat.Customer Phone Type}}—The customer’s phone type.
• {{Chat.Customer ID}}—The identification number for this customer, set by your web chat developers. For example, you can configure web chat to supply the account number that your organization keeps for that user. As a result, the agent can use it to look up the customer in a database.

Email variables

• {{Email.Customer Email Address}}—The address that the customer used.
• {{Email.Subject}}—The subject line of the customer’s email.

UUI variables

• {{UUI.UUIData}}—User to User Information (UUI) is the exchange or passage of data that is unrelated to the call from one application to another. Scripts support UUI data exchange. To use UUI data in scripts, enable the script’s UUI property, enable the User to User Information settings on the trunk and set a UUI Data action.

Workitem variables

• {{Workitem.Status ID}}—The identification number of the workitem’s status.
• {{Workitem.Status Name}}—The name of the workitem’s status.
• {{Workitem.Workbin ID}}—The identification number of the workbin for the current workitem.
• {{Workitem.Workbin Name}}—The name of the workbin for the Current workitem.
• {{Workitem.Workitem ID}}—The identification number of the current workitem.
• {{Workitem.Workitem Name}}—The name of the current workitem.
• {{Workitem.Worktype ID}}—The identification number of the worktype for the current workitem.
• {{Workitem.Worktype Name}}—The name of the worktype for the current workitem.
• {{Workitem.Raw Assignment State}}—The untranslated current assignment of the workitem.
• {{Workitem.Assignment State}}—Current assignment of the workitem.

Page variables

• {{page.[name of the script page].id}}—This built-in variable contains a unique identifier for a script page. Page variables exist outside the portal component and can be used throughout the script.

Schema variables

Schema variables are used by workitems and data actions. You can use a schema variable to replace several separate variables with one schema object in a data action. You can also use a schema variable to pull in custom data for a workitem from fields or variables specific to the associated worktype.