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 any of 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:

Variable NameDescriptionTypeExample Use Case

System.languageCode

The language code the conversation is taking place in. Ex. en-US

Text

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

System.utterance

The most recent message received from the human

Text

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

System.userId

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

Text

Pass to Data requests to look up information for the user.

System.conversationId

The unique id for the current conversation

Text

Pass to Data requests to identify a unique interaction.

System.sentiment

The sentiment of the user for the current exchange. Note: sentiment analysis must be enabled for the bot.

Text: POSITIVE NEUTRAL NEGATIVE

Use in a Split node to provide empathetic responses.

System.capturedIntent

Set by the User input node.

Text

Use in a Redirect node or with a Split node in and conditions

System.aiGeneratedResponse

Provides a GenAI response based on the current state of the conversation.

Text

Use in a No match connector of a User choice node to dynamically rephrase the question based on the user's utterance.

System.transcript

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

Text

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

System.channelType

Provides the channel the user is currently using.

Text

Use in a Split node to determine which channel the user is currently using.

Last updated