User Interaction

The User Interaction Step enables interaction with users by asking questions, collecting input, and validating responses. This step is highly configurable, allowing you to define the question, provide quick reply options, validate user input, and handle invalid responses. Below is a detailed explanation of its key fields and functionalities, incorporating the clarifications provided.

Key Fields and Functionalities

1. Question

   • This is the main prompt displayed to the user.

   • You can inject parameters, variables, or context values into the question field to dynamically customize the message.

   • The Translate toggle allows you to enable or disable automatic translation of the question into the user's preferred language.

2. Quick Replies

   • Quick replies are predefined response options that users can select instead of typing a free-text answer.

   • You can add multiple quick replies by clicking the + button.

3. Input Validation

   • Input validation ensures that the user's response meets specific criteria.

   • You can choose from several validation types, such as Email, Regex, Quick Replies, or None:

     • Email Validation: Ensures the input is a valid email address.

     • Regex Validation: Allows you to define a custom regular expression to validate the input.

     • Quick Replies: Only allow for an input from the Quick Replies list

     • None: No validation is applied.

4. On Invalid Answer

   • Defines how the tool should handle invalid user input. Options include:

     • Ask Again: Re-prompts the user to provide a valid answer. If this option is selected, you must specify a value greater than 0 in the Retries Before Failure field.

     • Raise Error: Stops the execution and raises an error.

   • You must also configure an Error Message to display when the input is invalid. For example, "Please try again in the following format..." or "Error. Invalid."

5. Error Message

   • A customizable message is displayed to the user when their input is invalid.

   • This field is required when input validation is enabled. For example, you can guide the user with messages like "Please try again in the following format..." or "Error. Invalid."

Example Use Cases

• Collecting User Email: Use the Email validation type to ensure the user provides a valid email address. If the input is invalid, re-prompt the user with a helpful error message and retry the operation a specified number of times.

• Custom Input Validation: Use Regex to validate specific patterns, such as phone numbers, postal codes, or custom formats.

• Guided Responses: Provide quick replies to simplify user interaction and ensure the response matches one of the predefined options. Match these with the Qucik Replies validation type to make sure the answers come in the expected format.