In this page, you find the list of Standard Variables available in XCALLY Motion application.
You can see here how to set the variable syntax, based on section you need to configure.
Voice Channel
Inbound Call
Title | Variable | Description |
|---|---|---|
Unique ID | uniqueid | unique identifier associated with each call |
Caller Number | calleridnum | parameter indicating the caller's telephone number |
Caller Name | calleridname | parameter indicating the name associated with the caller's telephone number |
Queue | queue |
Called Number
destcalleridnum
Called Name
destcalleridname
this variable indicates the destination queue or group of agents that handled the call | ||
Hold Time | holdtime | indicates the time spent on hold during call handling |
Talk Time | talktime | indicates the total time spent in conversation |
Connected Time | agentconnectAt | indicates the moment when an agent connects to the incoming call and becomes active in handling it |
Called Time | agentcalledAt | indicates the moment when an agent was called to handle an incoming call |
DNID | destexten | used to identify the destination extension or department to which the call was routed |
Complete Time | agentcompleteAt | provides information on the time when the agent finished interaction with the caller and ended the call |
No Answer Time | agentringnoanswerAt | indicates the moment when an agent was called but did not answer within a certain time interval |
Recording URL
|
| recordingURL | indicates the URL or access path to the audio recording of the call |
Outbound Call
Title | Variable | Description |
|---|---|---|
Unique ID | uniqueid | unique identifier associated with each call |
Caller Number | calleridnum | used to specify the caller ID number: it allows the caller to check the number that appears on the recipient's caller ID display |
Caller Name | calleridname | used to specify the caller ID name: it allows the caller to customize the name associated with the caller ID number |
Called Number | destcalleridnum | used to specify the recipient's phone number or the number to which the call is being directed |
Called Name | destcalleridname | used to specify the recipient's name |
Start Time | starttime | used to indicate the start time or initiation time of the call. It represents the moment when the outbound call was first initiated or placed |
Answer Time | answertime | used to indicate the time when the call was answered. It represents the moment when the call was picked up or connected |
Complete Time | endtime | used to indicate the time when the call ended. It represents the moment when the call was terminated, either by the caller or the recipient. |
Recording URL | recordingURL |
Member Name
indicates the URL or access path to the audio recording of the call |
Motion Bull
| Note |
|---|
The Motion Bull variables must be used with all lowercase characters in the triggers within {{ }}, while in the Square projects they must be used with all uppercase characters within { } |
Title | Variable |
|---|
Description | ||
|---|---|---|
Queue Campaign ID | xmd-voicequeueid | Available for Queue Campaign to identify a voice queue |
IVR Campaign ID | xmd-campaignid | Available for IVR Campaign to identify the id of IVR |
Caller ID | xmd-callerid | Refers to the caller ID information. |
Contact ID | xmd-contactid | Used to uniquely identify and reference a specific contact or customer |
Contact's Fields | xmd-{name_field} | name_field is the name of a contact's field in Contact Manager. |
You have to replace the field with e.g. xmd-firstname, xmd-phone, xmd-email and so on |
Contact's Custom Fields | xmd-cf_{ID} | ID is the custom field's ID. |
You have to replace the field: if e.g. the contact has a custom field with ID=5, the variable name will be xmd-cf_5. |
Chat Channel
At the first contact with a new customer, the interaction object is created, which acts as a “container”.
A high-level interaction variable is then created which contains general data e.g. creation date and contact ID, but other variables such as the body message will not be present at interaction level, but within the message itself.
Recipient of trigger action
Message
Note.id.bodymessage.in or outmessage.message.message.message.message.channelmessage.eventRecipient of trigger actionEmail Channel
Message
Recipient of trigger action
SMS Channel
Message
Recipient of trigger action
Recipient of trigger action
Openchannel
Agent interface
interface
Recipient of trigger action
Message
Title
Variable
Note
Message ID
id
Text message
body
Message direction
direction
Openchannel Account ID
OpenchannelAccountId
Openchannel Interaction ID
OpenchannelInteractionId
Agent ID
UserId
Contact ID
ContactId
Message create timestamp
createdAt
Creation timestamp
Channel
channel
Event type
event
Agent interface
interface
Recipient of trigger action
Fax Channel
| Status | ||||
|---|---|---|---|---|
|
Interaction
Title
Variable
Note
Interaction ID
id
Jscripty
Title
Variable
Note
Event field
{{name_field}}
name_field depends on the type of event.
For the full complete list, refer to the below section:
User field
{{user.name_field}}
name_field is one of the following:
id
username
fullname
email
userpic
alias
Contact field
{{contact.name_field}}
name_field is name of a contact's field in Contact Manager.
Example: contact.firstname, contact.phone, contact.email and so on
It is available only when you reply to email or click to email.
Variables for Omni Channels: Notification, Templates, Canned Answers, Routing and App Zone
In this section you find the variables that can be used in OmniChannels Notifications,Templates, Routing, Canned Answers and App Zone.
The syntax that must be used to embed the variable within the template is as follows:
Example 1:
Account: {{account.name}}
Example 2 (for Notifications):
{{#queue}}Queue: {{queue.name}}{{/queue}}
In this case only if (#) the queue variable exists, the template renders the queue variable