Tickets

The Tickets system provides a structured way to collect and manage customer feedback, feature requests, and support issues through intake forms and visual kanban boards. Unlike live chat conversations, tickets are asynchronous submissions that can be processed and tracked through defined workflows.

Where tickets live

Open Conversations → Tickets in the left-hand menu. That entry lists one row per board you can see, with + New board as its last row. There is no separate page that lists your boards — the sidebar is the list, and the Tickets entry only appears once you can see at least one board.

A board is one place with three tabs in the title bar, next to the board's name, each with its own address so it can be bookmarked:

  • Tickets — the kanban board itself
  • Forms — the intake forms that create tickets on this board
  • Settings — the board's name, its type, its roadmap widgets, and the danger zone
A new account starts with two boards, Bugs and Feature Requests. Both are marked as defaults and cannot be deleted. Bugs comes with the columns Open, In Progress, To Test and Done, and Feature Requests with Under Review, Planned, Closed and Released. A board you create yourself starts with a single column named New.

Core Components

Boards

The foundation of your ticket management system, boards organize tickets into logical categories and define workflow stages. Each board contains columns that represent different phases of ticket processing.

  • Board Types: Bug, Feature request or Custom
  • Columns: The stages of your workflow, such as Open, In Progress and Done
  • Chat widget: A Feature request board can be published as a public roadmap on a chat widget, chosen at Brand → (your brand) → Chat widget → Widget tabs → Roadmap

Ticket Management

Individual tickets contain all the information submitted through forms, along with metadata and processing controls.

  • Form Responses: Structured data collected from visitors
  • Workflow Tracking: Assignment, priority, and status management
  • Team Collaboration: Internal comments and decision communication
  • Media Evidence: Screenshots, recordings, and conversation history

Board Views

Interactive kanban interfaces provide visual ticket management with drag-and-drop functionality.

  • Drag and drop: Column-based organization with drag-and-drop status updates
  • Filtering & Search: Find tickets by priority, assignee, visitor, country, widget, form, label, or the text of the answers
  • Bulk Operations: Archive or delete all the tickets of a column at once, and mark a whole board as read

How It Works

  1. Submission: Visitors submit tickets through the intake forms on your chat widget — your team can also add one from the board with New ticket
  2. Filing: Each form files its submissions on the board it belongs to
  3. Processing: Agents review, assign, and move tickets through the columns
  4. Resolution: Teams provide decisions via email and update ticket status
  5. Archiving: Completed tickets are archived while preserving historical data

Key Features

  • Custom forms: Intake forms with validation and multiple field types
  • Visual workflow: Kanban boards with drag-and-drop ticket movement
  • Team Collaboration: Internal comments and assignment capabilities
  • Customer Communication: Professional decision emails and response tracking
  • Public Roadmaps: Share feature request boards as customer-facing roadmaps
  • Comprehensive Filtering: Search and filter tickets by multiple criteria
  • Media Integration: Attach screenshots, recordings, and chat transcripts
  • Labels: Short colored tags, defined per board, that group tickets independently of their column
  • Import and Export: Move a board in or out as Trello JSON, a CSV spreadsheet, Markdown, or a full Yaplet backup
  • Copy for AI: Put a ticket, a column, or a whole board on your clipboard as readable text for ChatGPT or another assistant
  • Duplicating a board: Reuse a proven setup — columns, labels and tickets — on a new product

Who can do what

Three separate rights control tickets, and each one changes what appears on screen rather than refusing you afterwards:

  • Tickets — see a board and work it; it is also required to move, edit, archive, delete or comment on a ticket.
  • Board management — adds the + New board row, the board's Settings tab, and duplicating a board.
  • Forms — adds the board's Forms tab. Without it the tab is not shown at all.

On top of those, access is granted board by board, on the team screen: open the account menu at the bottom of the left-hand menu (your avatar and name), choose Manage team, expand a member and use the Board access switches. An organization owner bypasses that and sees every board; an administrator does not — an admin can legitimately be limited to some boards.

All three rights come together with the Feedback boards & bug tracker add-on ($15/month), and with the Starter and Growth plans. During your free 14 days they are open too; after that, on the free plan, your boards stay as they are but switch off until you buy a plan or the add-on. There is no separate Forms product to buy, even though the add-on's own card does not mention forms.

Limits

Boards, tickets, labels and comments have generous limits, set far above normal use. If you ever reach one, write to [email protected].

Boards

Where boards live, how to create one, what its three tabs hold, and how to duplicate or delete a board.

Board Settings

Rename a board, change its type, see which widgets publish it as a roadmap, and delete it.

Board View

Use the interactive kanban interface to manage tickets with drag-and-drop functionality and advanced filtering.

Ticket View

Review detailed ticket information, manage assignments, communicate decisions, and access supporting evidence.

Forms

Build the intake forms that create tickets on a board, and decide what each one collects.

Importing and Exporting Boards

Bring a board in from Trello or a spreadsheet, and take one out as a file or a backup.

Board Access and Permissions

The three rights that control tickets, and how access is granted one board at a time.

Getting Started

  1. Open Conversations → Tickets in the left-hand menu
  2. Use + New board at the bottom of that list — it creates a board with a default name and drops you straight on its Settings tab, where you rename it and choose its type
  3. Add the intake forms that will feed it on the board's Forms tab
  4. Shape the workflow columns on the board itself
  5. For a Feature request board, publish it as a public roadmap at Brand → (your brand) → Chat widget → Widget tabs → Roadmap
Start with a "Bug Reports" board for technical issues and a "Feature Requests" board that can be made public. Use clear naming conventions and configure columns that match your actual workflow stages.

The ticket system bridges the gap between live chat support and structured feedback collection, providing a scalable solution for managing customer interactions that don't require immediate responses.

© 2026 Yaplet. All rights reserved.