This action will add a new empty form container that can hold both input fields and layout components. A form is a standalone input page that can be displayed independently from the chatbot to collect complex user data.
The action uses the following settings:
Like every other input, this action will hold the conversation until the user has successfully filled or canceled the given form.
When the Suppress chat Prompt flag is enabled, conversation will continue until the end of the current interaction but the input position will still be held on the form step. Using the Suppress chat Prompt you can create custom buttons or cards referring to the Xenioo Form activation URL. To show how the conversation will continue let's take a look at the following flow, where Suppress chat Prompt flag has been enabled.
The flow above will generate a Form Url that will be displayed by the Text Action that follows. The conversation will be held waiting for the form. Once the user confirms (or closes) the form, the action associated with the filter will be executed.
The form is available in all non-voice channels. Where possibile a button will be displayed to activate the form, otherwise a direct link.
The open automatically option is available only when the chatbot is hosted inside a web page. Some channels may actively block auto-open and as a result no button or flow may happen.
If the form is configured as a full page browser pop-up prevention may stop the form from appearing.
Using an empty title for the form will fully hide the floating area title zone. Hiding both confirm and cancel button will hide the floating area buttons zone. You can use both effects to obtain a full page form using all of the chat area space.
Form rendering mode can be used to choose how the form will appear on mobile or desktop browsers according to the following table:
This action does not trigger any event. You should instead evaluate the form return value to react to form results.
This action will change the value of the last_form_result variable depending on how the user has interacted with the form. Possible values are listed in the following table:
Channel specific availability follows the table below: