Page Comparison

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.

...

1. Create an attribute Username to store the 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. ContactId to store user’s contact id received from the Luma API.

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

   4. OTP_Check to store the OTP number entered by the user.

...

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. ‘GetContact’ to get the registered mobile number from the user’s Luma profile using Luma API.

      1. Fetch the Count of Matching users from Luma VA and save it in a local attribute Userlistsize.

      2. Add the following Error Handling rules:

         1. If a matching user is found, i.e. Userlistsize is 1, fetch

            1. Fetch the Mobile number received as a response from the web service and save it in the attribute Phonenumber.

            2. Fetch the user’s Contact ID in Luma received as a response from the web service and save it in the attribute ContactId.

         2. If no matching user or more than one matching user is found, i.e. Userlistsize is 0 or more than 1, set an error message and exit the skill

   2. ‘MapUserToChannelAccount’ to associate the user (contact id in Luma) to the channel account.

      1. Pass the Channel account ID and Contact ID to API as Outbound Payload.

      2. Fetch the Status received as a response from the web service and save it in the local attribute AuthenticationStatus.

      3. Define the bot behavior and response as Success Handling rule:

         1. If the user is successfully mapped and AuthenticationStatus is ‘Success’,continue executing the skill. Add Success Message such as “User Registered successfully.“ and set Execute to Continue.

         2. If the AuthenticationStatus is not ‘Success’,add a failure message and set Execute to Exit.

Step 3: Build a Skill

1. On Skill Builder--> Create Skill tab, 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 verify the user’s phone number. Configure the following rules.

      1. If 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 Attribute-->transform and use Transformation Function- Random to generate a Random OTP number and store it in the attribute OTP_Send.

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

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

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

      1. If OTP provided by the user ( in OTP_Check) is the same as the OTP send to the user (in OTP_Send), branch set Execute to Continue to the out of the box System skill, User Registration. Set Execute to Skill and select User Registration skill for execution.execute the next step.

      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 invalid and exit the skill. Set Execute to Exit.

   8. Add the Integration operation MapUserToChannelAccount to associate the user's contact id to the channel account.

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.

...

This list of Skills will be displayed as skill recommendations when a New user or Anonymous user accesses Luma Virtual Agent.

Download a sample skill definition. Note that the integration details should be replaced with your organization-specific instance details.

Additional Resources

Visit the below Wiki Documentation for more information on:

...