Versions Compared

Version Old Version 1 New Version 2
Changes made by

Bhavani.tvr (Unlicensed)

sneha.tripathi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Problem Statement: Customers with Luma enabled public KIOSKs, encounter multiple user logins in a given day with the kiosk being the same. So every time a new user comes to the KIOSK even if we clear the user context every time the widget gets closed, there seems to be no default way to verify the user first before we actually get into the typical user registration process. This is a problem when luma is implemented in public channels like a kiosk where no single user is registered to a channel.

...

The following are the steps to configure the skill:

Table of Contents

Step 1: Define Attribute

  1. Create an attribute OTP_Send Username to store a Random OTP number generated by the Systemthe username.

    1. On Skill Builder--> Attribute tab, click on Create Attribute.

    2. Add attribute details such as Name and Data type

    3. Click Save.

  2. Follow the above steps and create the below attributes:

    1. Phonenumber to store the phone number received from the Luma API

    2. OTP_Send to store a Random OTP number generated by the System.

    3. OTP_Check to store the OTP OTPc number entered by the user.

Step 2: Create an Integration

  1. Define Integration to Burst SMS with the “Send SMS to a number” operation.

    1. On the tenant menu, click on Integration.

    2. Create an Application with the integration type as REST.

    3. Add an instance to the SA Instance environment to send SMS messages.

    4. Configure the ‘Send SMS to a number’ Operation.

    5. Fetch the access token received as a response from the web service and save it in a local attribute Token.

  2. Follow the above steps and create the following integrations:

    1. ‘Get user (for a specific user)’ ‘GetContact’ to get the registered mobile number for the user from Azure ADfrom the user’s Luma profile. Fetch the mobile number received as a response from the web service and save it in a local global attribute mobile phone.

    2. ‘Send SMS to a number’ to send OTP number to the user's registered mobile number.

    3. Phonenumber.

Step 3: Build a Skill

  1. On Skill Builder--> Create Skilltab, enter Skill details such as Skill Name, Category, Description, and KPI Metrics

  2. Under Invocation type, add User Phrases such as ‘Register in Luma,’ ‘Register user in Luma’.

  3. Under Conversation flow,

    1. Add attribute Username to collect Luma VA username from the end-user.

    2. Add the Integration operation GetContact to fetch the user's registered mobile number from the Luma profile and store it in Phonenumber.

    3. Add a Ruleset to authenticate the user by validating OTPuser’s phone number. Configure the following rules.

      1. If user.phone Not equal to NULL or user.phone is not empty continue with the next steps.If user.phone equal to NULL or user. phone is the user’s Phonenumber is found,continue executing the skill. Set Execute to Continue.

      2. If the user’s Phonenumber is not found, i.e. is NULL or empty, prompt the user that the mobile number is not available, and exit the skill. Set Execute to Exit.

    4. Add Set attributeAttribute-->transform and use Transformation Function- Random to generate a Random OTP number and store it in the attribute OTP_SendShow message OTP_Send.

    5. Add the Integration operation Send SMS to a number to send the random OTP number OTP generated in OTP_Send to the user's registered mobile number in the local attribute mobile phone, available in Phonenumber.

    6. Add attribute OTP_Check to prompt the user to collect provide the OTP received by the user on the registered mobile phone number.

    7. Add a Ruleset to validate the OTP and authenticate the user by validating OTP. Configure the following rules.

      1. If OTP provided by the user ( in OTP_Check Equal to ) is the same as the OTP send to the user (in OTP_Send, continue with the next steps.If OTP Check Not equal to OTP Number), branch to the out of the box System skill, User Registration. Set Execute to Skill and select User Registration skill for execution.

      2. If OTP provided by the user ( in OTP_Check) and the OTP send to the user (in OTP_Send) do not match, prompt the user that the provided OTP is incorrect invalid and exit the skill. Set Execute to Exit.

  4. Click Save to finish building the skill.

  5. The next step is to add permission to the skill. Click on Permission and the Users or Groups who should be able to execute the Skill.

  6. Run Build and Publish to make the skill available in Virtual Agent.

  7. Once the skill is Published, Go to the Test Widget to test the skill. Click on Debug Logs and execute the skill to view the runtime Skill execution logs.

Your skill is now ready to use. Go to Conversation History to view the list of conversations where the end-user requested the skill.

Additional Resources

Visit the below Wiki Documentation for more information on:

  1. Creating an Attribute on Create Global Attributes

  2. Configure a 3rd party Web service integration on REST Integrations

  3. Creating and Managing Skills is at Create SkillsOverride an Attribute on Create Skills → Override Attribute

  4. Using Transformation Functions: Random is at Transformation Function Random

  5. Using local attribute in skills on Use Variables in Skills

  6. Using Ruleset on Using Rule Sets

  7. User Registration Skill on Configure System Skills

  8. Publishing Skill on Build and Publish

  9. Understanding Conversation logs on Conversation History.

  10. Provide permissions to users or groups at Permission

  11. Test your Skill on Test your Bot

  12. Debugging skill on Debug Skills