Page Comparison

...

1. Drag and drop the Text prompt from the palette onto the canvas.

   

2. 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.

3. You could create a new prompt by:

   1. Toggle to ‘New Prompt’.

   2. Add the ‘Message’ Luma should ask the user.

   3. Provide a name for the 'attribute’ to save the user’s response.

   4. Select the ‘datatype' type of information expected.

   5. Confirm if the prompt is mandatory. This means the users must provide the information to go ahead with the skill.

   6. Add the default value.

   7. Click on Create to create the attribute. This is optional. If not clicked, the attribute will be created automatically when Skill is saved.
      

      Image RemovedImage Added

   8. 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.

   9. Now you can pass global attributes to send in web widget context. This is applicable only for web widget.

4. You could also use an existing attribute.

   1. This enables you to add an existing global attribute to the skill and use the prompt added to the attribute.

   2. Toggle the switch to Choose existing Prompt.

   3. Select the attribute. This loads the Message field with the message configured in the selected attribute.

      

   4. You change the details by overriding the attribute.

      1. You could click on the pencil icon to update the message. Once done, click on the green tick to save changes.

      2. 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.

5. The Text prompt is now ready.

...

1. You may update the following KPIs:

   1. Deflected Support Requests: The KPI indicates that the skill can deflect a support request. Specify the number of minutes that the skill can save as the user request is directly resolved and a support request is avoided

   2. Resolved with Knowledge: The KPI is linked to ‘Deflected Support Requests’. Mark 'Resolved with Knowledge' if a Knowledge Article deflects the ticket.

   3. Resolved with External Information: The KPI is linked to ‘Deflected Support Requests.’ Mark 'Resolved with External Information' if the ticket is deflected using the information generated from external sources like the Internet or generative AI.

   4. Actionable Support Requests:  Use the KPI to indicate that the skill creates a well-structured, actionable ticket. Specify the number of support minutes that can be saved by creating an actionable support request through Skill. The default value is set to 5 minutes.

   5. Automated Resolutions: The KPI indicates that the skill resolves user issues using an automated service. Specify the number of support minutes that can be saved by the execution of the automated service, skill, or job by executing the Skill.

   6. Ineffective Best Response: This is a Luma Knowledge KPI. The KPI indicates that the Knowledge Articles returned in the result set are incorrect or irrelevant to the user’s request.

   7. Knowledge Gap: This is a Luma Knowledge KPI. The KPI indicates that Knowledge articles are unavailable for the user’s request and the phrase should be marked as a Gap in Luma Knowledge.

   8. Knowledge Feedback: The Luma Knowledge KPI is used to record feedback on a Knowledge Article or a FAQ presented to the end-user. Select the type of article , and provide the Artifact ID and Feedback (Helpful/Not Helpful).

   9. Skill Gap: This is a Luma VA Skill kpi. If the users response is negative during the conversation, using this kpi one can identify the cases where skill training or new skills are required.
      

      

...