Skill developers use Conversation constructs to build conversations between the user and Luma. Each Construct represents the steps Luma performs to complete a task. The constructs are added in the sequence of expected execution. Using these constructs, you can ask users for information, integrate with a third-party application, show search results, or conditionally branch to a skill to exit the conversation.
The constructs are available on the Visual Designer palette. You can drag and drop the controls on the canvas and link them together to form the skill.
Luma Virtual Agent provides a wide range of Conversation Items that can be used to perform various actions during a conversation. Following are the conversation items available on the Skill Builder:
Let's look at the constructs available in Visual Designer and how these can be used:
Start
The Start block is the entry point of the skill. It indicates the different methods by which the skill can be triggered. Skill developers use this section to define and configure various ways to initiate the skill, providing flexibility in how users interact with Luma.
A user can trigger the skill using the following:
User Phrases: User Phrases are a set of phrases used to train Luma’s Natural Language Processing (NLP) engine. The Users Phrases are often referred to as utterances when discussing NLP.
Commands: Command is the special phrase to identify and trigger the skill. Commands bypass the NLP component to identify the skill. Based on the command, the associated skill is executed.
On Canvas, the Start step shows the Skill Name and the first user phrase of the skill. You can click on the Skill name to open the Skill Details. For more details, refer to Creating a Skill with Visual Designer | Skill Information
On the Properties panel, you can:
Add User Phrases. By default, two phrases are added by default to the skill based on Skill name and description.
Toggle the switch to Enable User Phrases for the Skill.
Add the user phrases.
You can also tag a word in one of the user phrases and link it to an attribute. To do so, double-click on the word and link to an attribute. If the user phrase is used, the attribute will be automatically filled with the tagged word. For more information, refer to Creating Skill using Classic Designer | Tag Attributes to User Phrases.
Add the command for the skill.
Toggle the switch to enable the command for the Skill.
Add the command.
There can only be one Start in a skill. The construct in not available in the palette and also cannot be deleted from the skill.
Prompts
Prompts are used to fetch and retain information during a conversation between the bot and the user. With Prompt Control, Luma can gather information from users and design the user’s experience. Prompt Control empowers Luma to ask the right questions at the right time.
Following are the prompts available in Visual Designer:
Prompt- Text
Text prompts provide flexibility, allowing users to respond with detailed information. Here you can define the message to be displayed and the attribute to be used to hold and refer to the user’s response.
To add a Text prompt, do the following:
Drag and drop the Text prompt from the palette onto the canvas.
On the properties, change the step name from Prompt to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
You could create a new prompt by:
Toggle to ‘New Prompt’.
Add the ‘Message’ Luma should ask the user.
Provide a name for the 'attribute’ to save the user’s response.
Select the ‘datatype' type of information expected.
Confirm if the prompt is mandatory. This means the users must provide the information to go ahead with the skill.
Add the default value.
Click on Create to create the attribute. This is optional. If not clicked, the attribute will be created automatically when Skill is saved.
To add more details to the attribute, such as NLP extraction method and validations, before saving it, click on the Advanced Configuration under the create button.
You could also use an existing attribute.
This enables you to add an existing global attribute to the skill and use the prompt added to the attribute.
Toggle the switch to Choose existing Prompt.
Select the attribute. This loads the Message field with the message configured in the selected attribute.
You change the details by overriding the attribute.
You could click on the pencil icon to update the message. Once done, click on the green tick to save changes.
Alternatively, click on the attribute name and make the required changes on the attribute override pop-up screen.
For more details on attribute override, refer to Building Conversation Flow | Attribute Override.
The Text prompt is now ready.
Prompt -Quick Replies
Quick Reply prompts offer a selection to the end user. Using Quick Replies, skill developers can build personalized conversations. Here you can define the message to be displayed, Options to be presented, and attributes to be used to hold and refer to the user’s response.
To add a Quick Reply prompt, do the following:
Drag and drop the Quick Reply prompt from the palette onto the canvas.
On the properties, change the step name from Prompt to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
You could create a new prompt by:
Toggle to ‘New Prompt’.
Add the ‘Message’ Luma should ask the user.
Two options are added by default. These are presented to the users as quick reply buttons.
Add as many options as required. Click on the tag icon to change the payload, which is the value saved in the attribute when the option is selected. For more information, refer to Build User Prompts.
Provide a name for the 'attribute’ to save the user’s response.
Select the ‘datatype' type of information expected.
Confirm if the prompt is mandatory. This means the users must provide the information to go ahead with the skill.
Add the default value.
Click on Create to create the attribute. This is optional. If not clicked, the attribute will be created automatically when Skill is saved.
To add more details to the attribute, such as NLP extraction method and validations, before saving it, click on the Advanced Configuration under the create button.
You could also use an existing attribute.
This enables you to add an existing global attribute to the skill and use the prompt added to the attribute.
Toggle the switch to Choose existing Prompt.
Select the attribute. This loads the Message field with the message configured in the selected attribute.
You change the details by overriding the attribute.
You could click on the pencil icon to update the message and options. Once done, click on the green tick to save changes.
Alternatively, click on the attribute name and make the required changes on the attribute override pop-up screen.
For more details on attribute override, refer to Building Conversation Flow | Attribute Override.
The Quick Reply prompt is now ready.
Decision Prompt- Quick Reply
Decision Prompts are designed to create dynamic decision paths in a skill. Decision Prompt - Quick reply is a combination of Quick reply prompts and Conditions. The construct guides users through the skill based on their selections. With Decision Prompt, skill developers can design simple paths within your skill, tailoring the conversation flow based on user preferences. From conditional prompts to custom outcomes, the construct can be used to create engaging and intuitive conversations.
To add a Decision Prompt- Quick Reply prompt, do the following:
Drag and drop the Decision Prompt- Quick Reply prompt from the palette onto the canvas.
On the properties, change the step name from Prompt to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
You could create a new prompt by:
Toggle to ‘New Prompt’.
Add the ‘Message’ Luma should ask the user.
Two options are added by default. These are presented to the users as quick reply buttons.
Add as many options as required.
You can rename the options. The option names are saved as values to the attribute when the option is selected.
Provide a name for the 'attribute’ to save the user’s response.
Select the ‘datatype' type of information expected.
Add the Validation error Message.
Click on Create to create the attribute. This is optional. If not clicked, the attribute will be created automatically when Skill is saved.
To add more details to the attribute, such as NLP extraction method and validations, before saving it, click on the Advanced Configuration under the create button.
You could also use an existing attribute.
This enables you to add an existing global attribute to the skill and use the prompt added to the attribute.
Toggle the switch to Choose existing Prompt.
Select the attribute. This loads the Message field with the message configured in the selected attribute.
You change the details by overriding the attribute.
You could click on the pencil icon to update the message and options. Once done, click on the green tick to save changes.
Alternatively, click on the attribute name and make the required changes on the attribute override pop-up screen.
For more details on attribute override, refer to Building Conversation Flow | Attribute Override.
The Decision Prompt- Quick Reply prompt is now ready.
The options added to the prompt can now be used to build a path in the skill. When the user takes one of the options, the associated path is taken.
You could also add a Default path to the prompt, which is taken when the user does not take any of the provided options and provides any other value. To do so, select the 'Add Default Path'.
Message
In Luma VA, Messages play a vital role in facilitating the flow of information during conversations between the user and the bot. It enables Luma to send messages to the user without waiting for a response. Primarily, Messages are used to provide timely updates or communicate the outcomes of third-party integrations. These messages can be simple text messages, Quick Replies (providing a range of options to drive subsequent actions), or Text with Image. By leveraging Messages, Luma ensures seamless communication and enhances the user experience throughout the conversation.
Following are the Messages available in Visual Designer:
Message- Text
Text Messages allow skill developers to add simple text messages to be displayed to the user. You could add variations of the message to make the conversation more natural. Luma automatically picks one of the messages and displays it to the user.
To add a Text Message, do the following:
Drag and drop the Text Message from the palette onto the canvas.
On the properties, change the step name from Message to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
Add the ‘Message’ to be displayed.
The Text Message is now ready.
Prompt -Quick Replies
Quick Reply Message offers a selection to the end user. Using Quick Reply Messages, skill developers can build personalized conversations. Here you can define the message to be displayed, and the Options to be presented, providing a range of subsequent actions that can be taken.
To add a Quick Reply Message, do the following:
Drag and drop the Quick Reply prompt from the palette onto the canvas.
On the properties, change the step name from Message to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
Add the ‘Message’ to be displayed. This is optional.
Add as many options as required. You could add buttons that trigger another skill or conversation using ‘+Options' or open a URL using '+URL’
Click on the tag icon to change the value. This is the action taken when the option is selected. For more information, refer to Building Conversation Flow | Show Message.
The Quick Reply Message is now ready.
Image- Message
Image Messages allow skill developers to add simple text messages and images to be displayed to the user.
To add an Image Message, do the following:
Drag and drop the Image Message from the palette onto the canvas.
On the properties, change the step name from Message to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
Add the ‘Message’ to be displayed.
Add the Image URL and a Tooltip. Note: This is not a clickable image. The image used to provide additional information along with the text message.
The Text Message is now ready.
Utilities
In Bot Builder, Utilities are additional tools that enhance the skill-building process. These tools are used to build the logic behind the skill, allowing you to create conditional flows, assign attribute values, transform attribute values, and branch to other skills. By utilizing these constructs, a skill developer can design dynamic and responsive experiences for users.
The following are the constructs available in Utilities:
If Else
The If Else construct in Luma VA is similar to the "Add Conditions" feature in Classic Designer. It empowers skill developers to construct rule-based conditional flows. It dynamically guides users along specific paths within the skill, tailoring the experience based on their inputs. This feature proves particularly valuable when users make generic requests and you wish to steer them towards more specific requests or skills through the course of the conversation flow. With the If Else construct, you gain the flexibility to create customized and personalized interactions, enhancing the overall user experience.
To add an If-Else construct, follow the below steps:
Drag and drop the If-Else construct from the palette onto the canvas.
On the properties, change the step name from If Else to a user-friendly name to identify and define what the step does. This improves the readability of the skill.
Each Rule added on the properties panel appears as a new path in the canvas. The Default path is the fallback path that is taken when none of the Rules are fulfilled or evaluated as ‘true’.
The next step is to define the rules.
On the properties panel, click on the Rule to configure the conditions that form the rule.
Add/Change the Rule Name. Use a user-friendly name.
Now add one or more conditions that should be fulfilled for the skill to take the corresponding path.
You could configure the rule to fulfill ALL, ANY one or CUSTOME (some) of the conditions.
Repeat step 5 to add as many Rules or as many conditional paths as required on the Canvas.
Once the rules are ready, you can add steps to each rule. The defined path is taken when the rule is evaluated as true.
The count 1,2,3… on the links of each Rule indicates the sequence in which the rules are evaluated. Else determines the fallback path that is taken when none of the rule is true.