Conversation Node - Input Parameters


Overview


Once you have identified the end user's intent, you would now like to capture and save some key information from the end user.

Example:
If we have identified the user intent as purchasing car insurance.

You would want to capture information related to the car, which would help you compute the insurance premium for the customer. The car information could be registration date, RTO location, car manufacturer, model details, etc. This information needs to be saved, so that we can use the same to process in future.

Input parameter node helps you to capture and save information from the customer. The message under Bot Say's field is first message displayed to the user and then the information provided by the user is processed and stored in the variable which you have indicated by the variable name. This variable then can be consumed at different node to process that information.

Variable Node


Node Name


Name your node corresponding to the information or action required.

Bot Say's


Message in the Bot Say's field corresponds to what information is expected from the user.

Variable Name


Variable name should be easy and unique that will help to connect in the subsequent conversation node where you would like to consume that information.

Variable Types

There are different variable types supported by the conversation node, which helps you to easily capture and process the information.

Variable Type Description When to use
UI Controls More information about UI Controls. UI Controls helps you provide the user with next generation digital experience. Supports controls like List, Radio, Checkbox, Single Select, Multi Select, Date Picker, Single Value Slider and Double Value Slider.
Entity Please refer to Key concept - Entities documentation for custom defined entities. When user wants to use custom defined entities like Pincode, Indian Airports, Schengen Countries, Dealers locations etc.
Confirmation Yes: Yes, hmm, correct, sure
No: No, Na, I don't know.
When a user confirmation is needed.
Date Date is accepted in all date recognized formats like dd/mm/yy, mm/dd/yyyy, yyyy/dd/mm etc. However by default the system would always have DD/MM/YYYY format precedence.That means if user puts 09/10/2016 as date, it would by default would be treated as 9th Oct 2017 and not 10 Sep 2017.
It also recognizes today, tomorrow, next sunday, last year etc. and stores the corresponding date in DD/MM/YYYY format.
When a user input type date is required. Example: Enter registration date, Nominee birthdate etc.
Email Email entity accepts user input as valid email format When user email needs to be accepted. Example: Please provide registered email address, Provide email id on which you want me to send a soft copy.
Currency Possible values: 80000, 80k, 1 l, 2lac, 1 cr, 2million, 5M etc. When user is expected to insert values related to currency. Example: Kindly let me know your monthly income, Please help me with your liabilities amount, What IDV are you looking for? etc.
Language Possible values: English, Japanese, Marathi, Hindi, German etc. When user is expected to input Language. Examples: Please let me know which languages do you speak.
Link Hypertext links like www.google.com or https://amplifyreach.com When user is expected to provide any link. Example: Kindly upload your document and provide the system generated url.
Location Possible Values: Cities, Area, Countries etc. When user is expected to provide location. Example: Please enter destination where you want to book hotel or Please enter destination where you want to book a cab etc.
Name Possible Values: Firstname, Lastname, Fullname etc. When user is expected to enter names. Example: Please help me with your name or Please help me your name as written on Passport etc.
Number Possible values: 0,1, 1.5, 2.0942 etc. When user is expected to enter values which are numbers whole or fractions. Example: Please enter number of dependents or Please enter number of years with current organization.
Organization Name of the organization like Infosys Systems, Microsoft, Facebook, TATA Steels etc. When user is expected to enter organization. Example: Please let me know your current employer.
Percent Possible values: 10 ,12.5 etc. When user is expected to insert values in percentage. Example: What is rate of interest are you paying on your home loan? Or What is last year’s NCB as per the policy document?
Product Possible values: iPhone 5s, Macbook Pro, Fitbit Flex2 etc. When user is expected to enter any product name. Example: Please let me know which phone you currently use or Which laptop are you looking for?
Time Possible values are 10 AM, Noon, fifteen minutes etc. When user is expected to input time. Example: When can I schedule an appointment for tomorrow?
Text No validation is done for variable type text. When user wants any text to be taken as input. Examples: address, message, tweet etc.
Regx Any user input that needs to be validated by regular expression. When an input is not amongst the pre-defined entities like phone number, email etc and that needs to be validated before proceeding in the conversation, regular expression should be used. Example: Please enter 4 digit OTP sent to your registered mobile number. Here to confirm that user is entering only 4 digits, regx type variable should be used. Regular Expression to accept 4 digits is ([0-9]{4}).
Phone number Valid mobile number When user is expected to enter a mobile number. Example: Please insert your Paytm registered mobile number.

Entity


Entities can be used in many different scenarios. It is very powerful when you have a scenario where there are different synonyms for conveying the same information. Check documentations on Entities for more information on creating entities.
  • Variable Type: Entity.
  • Map Entity Name: Enter the name of defined Entity in the Entities.
  • Variable Name: Enter the name of the variable where the Value of the Entity would be captured for the synonyms mentioned by the end user.

Example:
We create an entity named motorType.
Then we add a value Car and synonyms as Car, Four Wheeler, Motor, Jeep.
Then we add a value Bike and synonyms as Bike, Two Wheeler, Scooter, Motorcycle.

If we have used this entity motorType in the Input Parameters node and variable name as mType. If user has entered Jeep / I have a Jeep then variable mType would hold the value Car.

If user input doesn't match any of synonyms mentioned in the entity then the system would show "Invalid User Input" message from System Messages.

Confirmation


Use this variable type when you are looking for confirmation from the user. The variable would have the value yes or no.

If user answers like "Yes, Yup, Hum, Sure" are translated into yes.
If user answers like "No, Na, I don't know" are translated into no.

If user input doesn't match any of the confirmation answer then the system would show "Invalid User Input" message from System Messages.

If the input data doesn't match the variable type, the system would detect an error and print the Invalid input message from the system messages, which are configurable.

Jump to, only when user doesn't have specific details


This is special jump only available for Input Parameter node. You can use this jump when the user specifies that he / she doesn't have the required information for satisfying the intent.

Example:
If you have an Input node to collect policy number and if the user doesn't have the policy number you can still proceed by asking the registered mobile number.

So if the user specifies some thing like "I don't have the policy number" or "Don't know my policy number". The system internally detects that the user doesn't have the information that you are trying to collect. In this case you can have a Jump to a node specified, which could ask for alternative information from which system can pull the policy number for the user or convey that Policy number is required to proceed and again ask for Policy number.

DO YOU WANT TO ASK A CONFIRMATION QUESTION?


Check this if you want to ask a confirmation question to the end user. This is important when you want to verify critical piece of information with the end user.

Example:
If you are trying to capture user's mobile number, where you want to send an OTP or use that number for doing further validation.

Bot Says: Please enter your Mobile Number.
Variable Name: phoneNumber
Variable Type: Phone Number
Confirmation Questions: Please confirm &phoneNumber is your mobile number ?

The same rule applies as we had for confirmation input type. So if the user enters Sure, Yes, Ya, Yup would be considered as confirmation.