Email Input Action
Last updated
Last updated
This action will hold the conversation and wait for the user to input a valid email. The conversation will hold until the user inputs a correct email or if the user, when allowed, skips the question.
The action uses the following settings:
Setting | Description | |
Wrong User Input Reply | This is the text that will be displayed if the user input does not match the control expression | |
Reply Pick Mode | When using multiple Wrong Input Reply lines, this option controls how replies are chosen. | |
Max Wrong Answers | The maximum number of wrong inputs the user can send before the question is skipped. Set to 0 (zero) to never give up on wrong inputs. | |
Never Skip Question | The question cannot be skipped by user. The input will repeat indefinitely until the control expression is matched or the maximum number of wrong inputs is reached | |
Intent Skip Question | The user can skip the question if his reply matches a specific intent | |
Text Skip Question | The user can skip the question if his reply matches a specific text or Regular Expression |
This action is halting the conversation. The chatbot is halted at the input point and will not proceed unless the conditions specified in the settings are met.
Email verification is formal and not based on real host/dns verification. Crafted email addresses may still pass the formal verification and may be further be checked using a third party API integration.
If the maximum number of wrong answers is reached the Successful User Input will still be triggered: you should check the contents of input fail trigger variable to verify if the input was successful or not.
Reply Pick Mode options will pick a wrong reply (if more than one is specified) in the following way:
Mode | Result |
Random | The reply will be picked randomly from the list of possible replies |
List | The bot will pick the first reply at the first wrong input, then the second and so on. The bot will keep saying the last one when the end of the lis is reached |
Round-Robin | Similar to list, except that when the end of the list is reached, the bot will restart from the first answer |
Successful User Input. This action will trigger any child operation as soon as the user input is matching the specified Control Expression.
This action produces the following variables after being triggered:
Variable | Description |
user_email | The email specified by the user |
input_fail_count | The number of times the user has failed to match the control expression |
input_fail_triggered | True if the maximum number of wrong inputs has been reached. Otherwise empty. |
Channel specific availability follows the table below:
Channel | Availability |
Fully Available. | |
Fully Available. | |
Telegram | Fully Available. |
Web | Fully Available. |
Alexa | Not Available. Alexa does not allow direct input halting. |
Google Assistant | Fully Available. |
Slack | Fully Available. |
API | Fully Available. |
This action can be used only inside interactions and not as child of other actions.
