Advanced messaging + functionality

Learn about the advanced configuration options for your conversation nodes in NLX's Dialog Studio

Advanced messaging

A bot relays messages to users when a node they've reached has Bot messages entered. Below are options to help enhance your use of this feature.

Not all nodes require messages and may not have a Bot messages section to configure. You may you use a Basic node before or after in these instances.

Adding more than one message to a node breaks up large messages into a series of smaller ones, making it easier for users to consume. This is especially helpful with text channels when multiple messages appear in succession as individual chat bubbles.

  • Add messages to a node by clicking +Add message on a node's side panel

  • Repeat the above as often as needed on a single node

  • To delete a message, choose the three-dot menu beside the message and select Delete

Add functionality

Several advanced actions can be applied to nodes on the Canvas. Simply expand the Add functionality section of a node's side panel and select from the following:

Assign tags to nodes for tracking and later evaluating their performance in your flow using Analyze mode. You may choose from system tags as well as any custom tags set up in your workspace settings. While in Analytics mode of your intent flow, for example, you can view the number of unique visits to the node from conversations with users.

  • Choose Analytics tags from the Add functionality menu of a node's side panel

  • Search or select a tag from the dropdown to assign the node*

  • Repeat as often as needed

  • To delete a tag, click the delete icon beside it

*Don't see a tag that you need? Add it from the Analytics tags tab in your workspace Settings

Any number of tags may be added to the same node, but it is recommended that you use only one tag per node to avoid double counting.

System variables

The following table defines the available system variables and potential use cases:

VariableDescriptionSample use case


Set by the User input node

Use in a Redirect node or with a Split node using conditional rules


The unique id for the current conversation

Pass to Data requests to identify a unique interaction


Provides the channel the user is currently using

Use in a Split node to route the user based on the channel used in conversation


Indicates the time (in UTC) recorded by the system when triggered in conversation (returns the number of milliseconds elapsed since the epoch, defined as midnight at the beginning of January 1, 1970, UTC)

Use in a Split node to route the user if their query is time sensitive or for changes to verbiage (e.g., “Good morning”) or processes during or outside of hours of operation


The language code that the conversation is using (e.g., en-US)

Pass to Data requests as a parameter to support translation in the Data request response


The last intent visited by the user in the conversation session

Use in a Split node at the beginning of an intent to route the path of a user based on the context of where they were in a conversation


The value (out of 100) that the NLP confidently matched a user's input to an intent

Use to ask clarifying questions if below a threshold to ensure the correct intent has been matched


The bot message played back when an intent is resumed from a previous interruption

Enabled on the Start node of an intent to pick up where a user left off


The sentiment of the user (Positive, Neutral, Negative) for the current exchange. Note: sentiment analysis must be enabled for the bot

Use in a Split node to provide empathetic responses


Provides the complete exchange between the human and the bot. Any sensitive information will be redacted

Use as a payload field in a Data request that creates a ticket in a help desk system


The user id identifying the human in the conversation. Value varies by channel

Pass to Data requests to look up information on the user


The most recent message received from the human

Use in a Split node and the Contains operator to determine if the user said a specific keyword


The user's detected time zone in the conversation

Determine the real time a user means for NLX.Date or NLX.Time slots when passing to a Data request

Last updated