Input Cells
Last updated
Last updated
The input cell just stops the flow, so the user can insert a very specific information that will be interpreted later by an entity.
This information is user-specific, and it might be a birth date, a ZIP code or a token, for example.
Important:
In the Input cell, avoid accents when writing the stored input field, and in compound words, prefer underline ( _ ) over spaces. With this syntax, you will make it easier when programming in technical cells, such as rule and code.
Here, the user insert a specific date, ex January 3. This template activates a calendar where the user can select a date.
The user insert a specific time, ex 3:15 pm. This template activates a clock where the user can select a time slot.
You define, using a specific pattern, the input structure. This is useful for country-specific information, such as ID numbers. In the Pattern field, your front-end team must enter the code that defines the field.
Present in all types of Input Cell, the switch “Remember Input” (shown in the image above) will save the information the user inserted for later use in the same session. In other words, this information will be stored for the duration of the interaction between user and virtual agent.
When building a flow, you may need to catch many user data to send to a company and return a response. For example, in a bank account opening flow: you ask name, birth date, ID... Send this information to the institution and then inform the best bank account to the future client.
In cases like this, you should create several Input cells and store all this information throughout the session will be stored (remember to hit the "Remember Input" button). And, very importantly, give different names, call to action, and descriptions to each Input cell.
To make this "bridge" with the company, remember to add a at the end.
