Forms

Intake forms collect structured feedback from visitors and automatically create tickets on the board they belong to. The form builder provides a visual interface with three synchronized panels for designing, previewing, and editing form fields.

Where forms live

A form belongs to the board it feeds. You find and build them at Conversations → Tickets → (board) → Forms. That tab lists only the forms that create tickets on that board, with Add form, plus clone and delete on each row. Its heading reads Intake forms, with the line "Forms that create tickets on this board — a visitor fills one in, and the submission lands here as a ticket." The form your account was created with on each of its two starting boards is marked as that board's default: its delete action is grayed out with the tooltip Cannot delete the default form, so clone it if you need a variant.

There is no organization-wide forms page. The form builder has its own address; inside it a trail reads Board › Forms › form name, and the back arrow returns to that board's Forms tab.

Building forms needs the Forms right. A colleague with only the Tickets right does not see the Forms tab at all. Launching an existing form into a live conversation from the inbox's Start button is a separate matter: that only needs the add-on on your workspace, not your own Forms right.

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. Click Settings in the form builder's title bar to open them in the panel on the right, where a question's own settings usually go. They are saved together with the questions by the one Save changes button in the title bar (it shows Unsaved changes beside it, and Discard undoes your edits); leaving the builder with unsaved changes asks first ("You changed this form but haven't saved it.").

Name
string required
The form's name on the board's Forms tab and anywhere the form is picked from. Only your team sees it.
Board
string required
The board this form files its submissions on ("Submissions become tickets on this board."). A form created on a board is attached to that board from the start, and this picker always has a board selected, so a new form never ends up without one.
Screenshot
boolean
Visitors can attach a screenshot of the page they are on.
Screen recording
boolean
Visitors can record their screen to show what happened.
Ask for an email address
boolean
If the visitor's email isn't known yet, the form asks for it, so you can reply.

The two attachment switches sit under What visitors can attach. They add extra buttons to the widget's form and appear only on websites, not in the phone app. At the bottom of the Settings panel, Delete this form removes the form (widgets that use it stop showing it, and it cannot be undone).

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 on the associated board.

How Forms Create Tickets

  1. Submission: A visitor fills the form in through your chat widget, or an agent fills it in from the dashboard — from the inbox's Start button or the board's Add ticket dialog
  2. Capture: Responses are captured as structured data with field types and validation
  3. Ticket creation: A new ticket is automatically created on the linked board
  4. Processing: Tickets enter the board's 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
  • Columns: Tickets from forms follow the board's stages from the moment they arrive
  • Public roadmaps: A form filed on a Feature request board produces tickets that can appear on a public roadmap
  • Consistency: Form structure ensures consistent data collection across submissions

What a ticket from a form contains

Each form submission creates a ticket containing:

  • The answers: All field responses, shown under Submitted answers in the ticket
  • Extras: Screenshots, recordings, email addresses, and timestamps
  • Placement: Automatic placement on the right board
  • Handling: Team assignment, status tracking, and resolution — see Ticket View
Forms transform unstructured customer feedback into organized, actionable tickets that your team can efficiently process through defined workflows.

What you need to buy

Forms come with the Feedback boards & bug tracker add-on ($15/month), which grants Tickets, Board management and Forms together. The Starter and Growth plans include them, and they are open during your free 14 days. There is no standalone Forms module to buy, even though the add-on's own card says only "Feedback boards & bug tracker" and does not mention forms.

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 there is no archive to fall back on — clone a form before deleting it if you want to keep a copy of its structure. The default form on each starting board cannot be deleted at all. Deleting a board also deletes the intake forms that feed it; the confirmation says how many, and warns that anyone using them in a widget stops being able to submit.

© 2026 Yaplet. All rights reserved.