When creating your Forms, you will find in Clevy OnDemand several fields you can use to create rich user experiences.
The main objective of these fields is to simplify the collection and formatting of the data you want to collect while offering powerful possibilities to enhance the end-user experience, as all those fields are natively multichannel (adapt to the web version in the Portal or Conversational Use in the Virtual Assistant).
Learn how to use the different content fields available in Clevy OnDemand!
How to add new Fields
When you create a new Form, three default fields will appear:
A "Text Input" field - titled "Firstname."
A "Text Input" field - titled "Lastname."
A "User Email" field - titled "Your email address" is marked as required (" *. ")
While the first two are merely placeholders to help you get started, the 3rd one is compulsory. Without it, the results of the forms filled out by your employees won't be accessible in your inbox, as it won't be possible to link an end-user to a specific Form result.
The Forms fields - the Content blocks
In addition to the Standard text component (the same as in the article editor), there are ten different types of Inputs you can create
Most of those Input components have different configuration options:
Title: the title you want to give to the Input you are asking for ("name", "Lastname", "email,"...). The Title can also be a question, e.g.," what's your name?" to make the experience more conversational.
Description: Description you want to give to the field. It's the advice you give to end-user to let them fill out the fill in the right way or context about the data you want to collect.
Placeholder: the value that will appear as a light example to give the end-user an example of the type of value you expect (for a date, it could be, for instance, "MM/DD/YY")
Default value: A default value you want to be in the field as there is a high chance you know the value, and it won't change from one end-user to another (e.g., name of your company when a Company Name is required in an official field)
Required toggle: Activate it if you want to make the field compulsory. When activated, the user won"t be able to submit the form without filling out that field.
Minimum and Maximum length: Minimum and maximum length you accept for the input, counting the characters.
Some Input Components require specific configuration options. Let's look at the components now.
Text Input: Simple text input lets you ask for one single input data like a name or a date.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
|
 |
 |
Textarea: Creates a Text area to ask for more than simple values, like an address, a bank account, or details to explain an issue
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
Email Input: asks for an email and checks if the value is type email. If not, a validation message will appear, asking the user to enter a valid email.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
User Email Input: Important to link the Form to the user filling the form. Compulsory if you want to receive the data in your inbox.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
Number Input: Asks for a number. Checks if the value is a number and lets the user increment the number with an up and down arrow by a "step," meaning by a certain number you choose ("0,3", "1", "10,"...)
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
File Upload: This lets you collect one or various attached files in a form and decide the minimum and the maximum number of files you'll accept.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
Select: It Lets you ask a user to choose one among many options, either in the form of radio buttons or a dropdown.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
Multiselect Input: This Lets you ask a user to choose more than one among many options, either in the form of checkboxes or a dropdown.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
Public Tags: Asks a user to select a category among the Tags you set up as public. To know more about public tags, read this article.
EDITION MODE | VIEW IN PORTAL | VIEW IN ASSISTANT |
 |
 |
 |
💡 Pro tips:
When an employee fills out a form, it will create a ticket containing all the data filled out by the employee. You can then use those data in your normal workflows, answer the employee their request has been processed and close the ticket.