OpenDialog Docs
opendialog.aiStart BuildingTalk to an expert
  • GETTING STARTED
    • Introduction
    • Getting ready
    • Billing and plans
    • Quick Start AI Agents
      • Quick Start AI Agent
      • The "Start from Scratch" AI Agent
        • Chat Management Conversation
        • Welcome Conversation
        • Topic Conversation
        • Global No Match Conversation
        • Supporting LLM Actions
        • Semantic Classifier: Query Classifier
      • A Process Handling AI Agent
  • STEP BY STEP GUIDES
    • AI Agent Creation Overview
    • Add a new topic of discussion
    • Use knowledge sources via RAG
    • Adding a structured conversation
    • Add a 3rd party integration
    • Test and tweak your AI Agent
    • Publish your AI Agent
  • CORE CONCEPTS
    • OpenDialog Approach
      • Designing Conversational AI Agents
    • OpenDialog Platform
      • Scenarios
        • Conversations
        • Scenes
        • Turns and intents
      • Language Services
      • OpenDialog Account Management
        • Creating and managing users
        • Deleting OpenDialog account
        • Account Security
    • OpenDialog Conversation Engine
    • Contexts and attributes
      • Contexts
      • Attributes
      • Attribute Management
      • Conditions and operators
      • Composite Attributes
  • CREATE AI APPLICATIONS
    • Designing your application
      • Conversation Design
        • Conversational Patterns
          • Introduction to conversational patterns
          • Building robust assistants
            • Contextual help
            • Restart
            • End chat
            • Contextual and Global No Match
            • Contextual FAQ
          • Openings
            • Anatomy of an opening
            • Transactional openings
            • Additional information
          • Authentication
            • Components
            • Example dialog
            • Using in OpenDialog
          • Information collection
            • Components
            • Example dialog
            • Using in OpenDialog
            • Additional information
          • Recommendations
            • Components
            • Example dialog
            • Additional information
          • Extended telling
            • Components
            • Example dialog
            • Additional information
          • Repair
            • Types of repair
            • User request not understood
            • Example dialog
            • Additional information
          • Transfer
            • Components
            • Example dialog
            • Additional information
          • Closing
            • Components
            • Example dialog
            • Using in OpenDialog
            • Additional information
        • Best practices
          • Use Case
          • Subject Matter Expertise
          • Business Goals
          • User needs
            • Primary research
            • Secondary research
            • Outcome: user profile
          • Assistant personality
          • Sample dialogs
          • Conversation structure
          • API Integration Capabilities
          • NLU modeling
          • Testing strategy
          • The team
            • What does a conversation designer do
          • Select resources
      • Message Design
        • Message editor
        • Constructing Messages
        • Message Conditions
        • Messages best practices
        • Subsequent Messages - Virtual Intents
        • Using Attributes in Messages
        • Using Markdown in messages
        • Message Types
          • Text Message
          • Image Message
          • Button Message
          • Date Picker Message
          • Audio Message
          • Form Message
          • Full Page Message
          • Conversation Handover message
          • Autocomplete Message
          • Address Autocomplete Message
          • List Message
          • Rich Message
          • Location Message
          • E-Sign Message
          • File Upload Message
          • Meta Messages
            • Progress Bar Message
          • Attribute Message
      • Webchat Interface design
        • Webchat Interface Settings
        • Webchat Controls
      • Accessibility
      • Inclusive design
    • Leveraging Generative AI
      • Language Services
        • Semantic Intent Classifier
          • OpenAI
          • Azure
          • Google Gemini
          • Output attributes
        • Retrieval Augmented Generation
        • Example-based intent classification [Deprecated]
      • Interpreters
        • Available interpreters
          • OpenDialog interpreter
          • Amazon Lex interpreter
          • Google Dialogflow
            • Google Dialogflow interpreter
            • Google Dialogflow Knowledge Base
          • OpenAI interpreter
        • Using a language service interpreter
        • Interpreter Orchestration
        • Troubleshooting interpreters
      • LLM Actions
        • OpenAI
        • Azure OpenAI
        • Output attributes
        • Using conversation history (memory) in LLM actions
        • LLM Action Analytics
    • 3rd party Integrations in your application
      • Webhook actions
      • Actions from library
        • Freshdesk Action
        • Send to Email Action
        • Set Attributes Action
      • Conversation Hand-off
        • Chatwoot
    • Previewing your application
    • Launching your application
    • Monitoring your application
    • Debugging your application
    • Translating your application
    • FAQ
    • Troubleshooting and Common Problems
  • Developing With OpenDialog
    • Integrating with OpenDialog
    • Actions
      • Webhook actions
      • LLM actions
    • WebChat
      • Chat API
      • WebChat authentication
      • User Tracking
      • Load Webchat within page Element
      • How to enable JavaScript in your browser
      • SDK
        • Methods
        • Events
        • Custom Components
    • External APIs
  • Release Notes
    • Version 3 Upgrade Guide
    • Release Notes
Powered by GitBook
On this page
  • Finding the message editor
  • Finding specific messages
  • Adding or editing a message
  • Enriched user experience
  1. CREATE AI APPLICATIONS
  2. Designing your application
  3. Message Design

Message editor

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

PreviousMessage DesignNextConstructing Messages

Last updated 1 month ago

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.

  • Open your OpenDialog application

  • Select the Scenario you would like to edit

  • Go to the Design section in the right hand navigation panel

  • Click on the arrow to reveal the drop down

  • Select 'Messages'

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. This will take you directly to the messages related to the conversational component you are on (scenario, conversation, scene, turn or intent)

  • Open your OpenDialog application

  • Select the Scenario you would like to edit

  • Go to the Design section in the right hand navigation panel

  • Select 'Conversation'

  • When on the conversation page, navigate to the top right hand corner

  • Click on the message bubble, which is the middle option of three icons

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 example, for a Welcome intent, we can have a message specifically geared towards new users, and one geared towards existing users.

Our search functionality allows you 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.

  • Open your OpenDialog application

  • Select the Scenario you would like to edit

  • Go to the 'Search' section in the right hand navigation panel

  • Click on the button to reveal the search pop up

  • Start typing in what you are looking for

  • Select the message you want from the results

Note that the displayed messages in the message catalog are the sample message you have defined upon intent creation. The sample message is there to help you with the conversation design, and recognizing intents throughout the OpenDialog platform. When editing a message, this will not edit the sample message.

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 following options are available in the Edit Message screen:

  • Message name: the name is purely to help you identify specific messages. The message name will automatically be prepopulated with the name of the app intent it is related to. Make the message names something that is easy to recognize and place. For ease of use and recognition, define your naming convention upfront when you start creating your conversational application.

    We recommend using the intent name, optionally followed by the condition if you are using one.

    For example: WelcomeIntent - userID not set

  • Preview: shows a preview of your message. More complex messages don't have a full preview available and are labeled in the preview by their message type.

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

  • For example: if userID is not set

  • Behaviours:

    • "Disable free-form user input field for this message" will ensure that the user is not able to send free-form text messages in response to this message. This is usually best used alongside a message block that the user can interact with, such as a button message or form message.

    • "Hide the avatar for this message" will ensure that Webchat doesn't display the avatar alongside the message.

Enriched user experience

OpenDialog's modular approach to messages allows you to take advantage of rich UI components, surface specific messages on your terms and personalize them to make them relevant to specific users or use cases. Check out the following sections to take your conversational application from simple question answering to a truly personalised hybrid experience :

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

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.

: in the conditions tab you will be able to define when your message gets selected by defining conditional rules.

"Exclude markdown code from attribute filling" will ensure that any curly-braces {}included inside (single or triple back ticks) will not be used in attribute filling. By default OpenDialog will presume any curly braces are being used as and attempt to fill it's value, this behaviour excludes markdown code from being filled. This behaviour is useful if you need to use curly braces for things such as code snippets within your messages.

Layout:
Conditions
markdown code blocks
attribute syntax
message types
Design option - not expanded
Design option - expanded
How to find the message editor
Search across Intents and Messaes using the search functionality in the main scenario menu
Enter your search query in the search bar that appears when selecting Search in the main scenario menu
Message catalog
Multiple messages associated with a single intent
Edit Message screen
Cover

Tailor the user experience

Cover

Surface relevant messages

Cover

Personalize the messages

Master the art of crafting powerful messages tailored to your specific needs, utilising OpenDialog's diverse range of to their fullest potential.

Take advantage of OpenDialog's unique approach, using to surface relevant messages at the right moment in the conversation.

OpenDialog's system will allow you to taylor your messages using these variables to surface personalised information.

message types
conditions
attribute