Creating Forms

Brief Overview

You can collect all types of inputs, responses, feedback, or any other desired information from your end-users, all of this without requiring any additional coding or engineering resources, simply by using Userpilot's native form fields and radio buttons. 

Userpilot forms include three patterns that assure you to further increase your engagement with your end-users: Input, large Input, and radio buttons.

Common use cases

  • Collecting end-users contact details and data such as emails, phone numbers, websites URLs, etc.
  • Getting feedback and thoughts on a newly implemented design.
  • Collecting the date of establishments for your end-users companies.
  • Getting info from users who didn't complete certain Userpilot experiences.
  • Asking multiple-choice questions on whether your users like a certain feature or not.

Creating a form

To find your form options, create any UI pattern, and hover the mouse pointer on the section you want to hold a form. Click on the green '+' icon and head over to forms to select the intended form pattern.

Important: Steps must have a button that is not set to dismiss the experience for form responses to be successfully saved. 


Form Types

Userpilot provides you with three form patterns that you can use depending on your use case. 

Input: This type of form allows you to let users enter answers with a certain type of data.

Large Input: This type of form allows you to let users enter any answer they want in their own words.

Radio Buttons: This type of form allows you to let users choose only one response from a list of answer choices.


Where can I view form responses?

You can view responses on a user basis by choosing responses from the User Identification dropdown that is available on the Users page in your Userpilot's dashboard.

After choosing responses, you can set user identification conditions to have a more clear overview of your users' responses. Each response will appear under its unique label. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.