Forms

Forms collect structured feedback from visitors and automatically create tickets in your boards. The form builder provides a visual interface with three synchronized panels for designing, previewing, and editing form fields.

Form Builder Overview

The form builder provides a visual interface for creating and customizing feedback forms. Forms collect structured information from users and automatically create tickets in your helpdesk system.

Form Builder

Learn how to use the form builder interface to create and customize your forms with different input types, validation rules, and field configurations.

Form Configuration

Beyond individual field settings, forms have additional configuration options accessible through the Settings modal.

Form Name
string required
Display name for the form in the dashboard and board management.
Associated Board
string required
Links the form to a specific board where submissions will create tickets.
Screenshot Collection
boolean
Automatically captures and attaches screenshots with form submissions.
Recording Collection
boolean
Includes screen recordings with form data for detailed feedback.
Email Collection
boolean
Requires users to provide an email address for follow-up communications.

Connection to Boards and Tickets

Forms serve as the bridge between customer feedback collection and your ticket management system. When users submit forms, their responses automatically become structured tickets within the associated board.

How Forms Create Tickets

  1. Form Submission: Visitors fill out and submit the form through your widget or direct link
  2. Data Structure: Responses are captured as structured data with field types and validation
  3. Ticket Creation: A new ticket is automatically created in the linked board
  4. Workflow Processing: Tickets enter the board's workflow columns for team processing

Board Integration

Forms are directly connected to boards, which organize tickets into logical categories:

  • Board Types: Forms can be associated with Bug, Feature Request, or Custom boards
  • Column Workflow: Tickets from forms follow the board's defined processing stages
  • Public Forms: Feature request forms can be made public for customer-facing roadmaps
  • Data Consistency: Form structure ensures consistent data collection across submissions

Ticket Data Structure

Each form submission creates a ticket containing:

  • Structured Form Data: All field responses with proper typing and validation
  • Metadata: Screenshots, recordings, email addresses, and timestamps
  • Board Organization: Automatic placement in the appropriate board and column
  • Processing Workflow: Team assignment, status tracking, and resolution handling
Forms transform unstructured customer feedback into organized, actionable tickets that your team can efficiently process through defined workflows.

Best Practices

Choose Appropriate Input Types

Match field types to the information you need - use single choice for categories, multiple choice for features, and numeric scales for satisfaction ratings.

Keep Forms Focused

Limit forms to essential questions only. Long forms have lower completion rates.

Use Clear Question Text

Write clear, specific questions that users understand immediately.

Configure Validation Wisely

Only mark fields as required when absolutely necessary for processing.

Test Form Preview

Always preview your form before publishing to ensure it looks and functions correctly.

Form deletion is permanent and removes all associated form data. Always archive forms instead of deleting if you need to preserve historical submissions.