Message Editor

The Message editor gives us access to the messages in the scenario and allows us to add, edit and delete messages.

Finding the Message Editor

There are two ways to access messages:

Option 1: The Messages functionality is available as part of the Design functionality. Design includes both Conversation, where the conversation design occurs and Messages, where we access the message editor and work on everything to do with the content and assistant prompts. If Messages is not viewable in the sidebar, click the carrot (down arrow) to the right of Design to expand.

Option 2: From within the Conversation designer, navigate to the Message editor by clicking on the message icon in a Scenario, Conversation, Scene, Turn or Intent:

Finding specific messages

Which messages you see in the list of messages depends on the level at which you enter the Message Editor. For instance, if you entered the editor at the scene level, you would only see the messages for that scene. If you enter the editor at the highest level, you see all messages for the scenario.

Messages are associated with intents. For instance, a welcome message can be associated with an intent called "Welcome".

Several messages can be associated with a single intent. For our Welcome intent, we can have a message specifically geared towards new users, and one geared towards existing users, whose name we have access to and we can greet the existing users using their name.

Our search functionality makes it a breeze if you want to edit a specific word, sentence, or message. You can use OpenDialog Search to find a message or group of messages that contain the exact phrases or words you're looking for.

You can access the 'Search' functionality in the main scenario menu, which searches for content throughout Intents and Messages.

To search for a specific message, click on the 'Search' item in the main scenario menu, and the search modal will appear right in the middle of your workspace. Then, enter your query in the search bar, and the modal will display the results instantly.

By clicking on the appropriate search result from the list, you'll be directed to the chosen component, giving you the opportunity to edit the selected message with ease.

Adding or editing a message

In the intent list, click the Edit icon for an existing message or click "Add a new message". An existing message can also be copied or deleted:

The Edit Message screen allows us to change the Message Name and customise the layout using a number of different message types. These types are covered in the next pages of this section.

The following options available in the Edit Message screen:

  • Message name: the name is purely to help you identify specific messages. Make the message names something that is easy to recognize and place

  • Layout: this is where you can build your message content, add conditions to your messages and set behaviours such as disabling text input and hiding the app avatar

  • Preview: shows a preview of your message

  • Conversation Designer: shows the current position in the Scenario where this message is/will be located

Designing a message

To design your message, click on any message block(s) to add those to the designer. You will see each of them appear, one after each other. You can then go ahead and add your message content as required.

Each block can be deleted or duplicated using the relevant icons.

Message types

The list of available message types:

If you can not find the message type you require below, you can find a full list of supported messages not available via the UI through "Custom Message" and an explanation of the underlying XML structure here.

Message conditions

Message conditions can be defined by clicking on Conditions in the Layout and adding context, attribute and other details. More information about context and attributes is a available in the next page on Attributes in Messages.

We define conditions so that the system can evaluate which message to use. In the image below, two messages are associated with the intent called The message called gets used when the user is not an existing customer. If they are, the message is used. Existing_customer is an attribute of the user context. More information about using attributes in messages can be found in the next page, "Attributes in messages".

Continuing our example above, where we want to show different messages to users depending on whether they are a new user or a returning user. To do this we would us Conditions to tell the system which message it should show depending on the value of attributes saved against the user.

For our example, then we would set the 'Attribute' to seconds_since_last_seen , 'Context' to user, 'Operation' to Equals and the 'Value' to '0' - meaning only show this message if the user has not been seen yet.

Where as for the returning user, we would change the 'Operation' to be Greater than. Meaning only show this message if the user has been seen before.

Conditions are really powerful for enabling personalised experiences for users. The key functionality that drives Conditions are Attributes and you find out more about them here.

Last updated