When you deploy your bot using the self-service widget, you can choose from a range of input options for your customers to interact with the chatbot. These input options will change if you decide to deploy on the conversations widget or if you choose to deploy on your messaging channels.
To configure the input options in a dialog, you will have to click the +Get Response option. This will show you two groups: input options and customer details. Some of these input options also support the Multiselect feature
Alphanumeric input: Use this when you need to receive alphanumeric inputs from your customer.
Articles: Display a list of articles that you’ve listed. Your customers can read through the article in the widget itself.
Button: Present the choices you’ve listed as buttons to your customer. It is advisable to use buttons when you offer a few options to the customer.
Carousel: Present a carousel with the choices that you’ve listed to your customers. They can go through multiple choices available. You can configure each item on the carousel to have many data points and display rich media content to the customer. These are especially useful when displaying a product catalog, order summaries, service items, etc.
Custom: Use this when you need to use this for custom validation using Regular Expressions (RegEx) in this field type.
Dropdown: Present the choices you’ve listed in a dropdown to your customer. It’s advisable to use the dropdown when you are presenting many options to the customer.
Number: Use this when you need to receive numerical input from your customer. This field will also be validated. So if your customer's input is not a number, and if not, will ask them to enter just numbers.
Text field: Use this when you need to receive text input from your customer.
With the options under customer details, the chatbot can validate if the response received is one of the following.
Display names and aliases
Some of the input options, such as buttons, dropdowns, and carousels, will have an option to use Aliases and the text displayed to the customer. While the display text is shown to your customers, your internal systems can process the alias value. For most use-cases, it is sufficient if the display name is the same as the internal name. However, there are some cases where you need to keep these names different. Here are a few examples of such use-cases:
E-commerce sites can use the carousel to display products from their catalog. The display name needs to have the product and brand in it, but internally, the name can be the product id or the SKU ID to run conditional logic or API calls.
Airline companies can use the display name to list the routes using the source/destination names as display names while using a shorter, specific internal name in API calls to process ticket booking or other updates,
B2B companies can have their employees' names listed in the display name, while internally, they can use an employee-specific code to manage their databases.