1. Docs
  2. Guides

Tickets: numbers, statuses, forms & due times

Some questions take more than one chat: a bug to fix, an order to replace, a refund to check with another team. A ticket keeps track of them. Any conversation, from the messenger, email, WhatsApp or any other channel, can become a ticket with a number, a type, a status, a priority and a due time. Tickets stay in your normal inbox, and customers can follow theirs in the messenger and by email.

Turn tickets on

Tickets are off until a workspace owner or admin clicks Turn on tickets in Settings → Tickets. Turning them on adds four ticket types to start with: Question, Problem, Bug and Feature request (the Free plan gets the first 3). You can rename them, change their emoji and colour, or add your own.

Turning tickets off later hides the ticket folders, Make ticket and the messenger’s Tickets tab. Nothing is deleted: tickets keep their numbers, status and fields, and come back when you turn tickets on again.

Make a ticket

A ticket is a conversation with a little more information. It keeps the conversation’s number, so conversation #1042 becomes Ticket #1042, with all its messages, notes and files. There are several ways to make one:

  • In the inbox: open the conversation and click Make ticket in its header, or press T. Choose the type, a title (it starts with the email subject or the customer’s first message) and the priority, and fill in the type’s fields.
  • Several at once: select conversations in the list and choose Make tickets.
  • In the phone app: open the conversation, tap ⋯ and choose Make ticket.
  • The customer: from the messenger’s Tickets tab (see In the messenger).
  • Automatically: an automation rule with the action Make it a ticket, for example for every new email to your support address.
  • From your own code or an AI app: the REST API and the MCP server.
  • From WHMCS: with WHMCS ticket sync, tickets opened in WHMCS come in by themselves, and tickets opened here show in WHMCS.

To make a ticket a normal conversation again, choose Turn back into a conversation in its Ticket panel. Its status, type and fields are removed; the messages stay.

Statuses

A ticket has one of five statuses. Your team and your customers see different words for some of them:

Status (your team)The customer seesWhat it means
OpenOpenYour team is working on it. It shows in the inbox like any open conversation.
Waiting on customerWaiting for your replyYou asked the customer something. The ticket leaves your open list until they answer. With no answer after a number of days (7 at first), it is closed automatically and the customer gets a “ticket closed” email. In Settings → Tickets you can choose the number of days, or to mark it solved or move it back to Open instead.
On holdIn progressYou are waiting for something else, like another team or a delivery. Put it on hold with no end date, or until a date: then it comes back to Open by itself.
SolvedSolvedThe problem is fixed. After a few days (4 at first) the ticket becomes Closed.
ClosedClosedFinished.
  • The customer writes again: a waiting, on-hold, solved or closed ticket goes back to Open. A solved or closed ticket opens again as the same ticket, with the same number, and its reopen count goes up.
  • Solve, don’t close: for a ticket, the inbox shows Solve (X) instead of Close. Closing a ticket from anywhere else, such as bulk actions, the API or an AI app, marks it Solved.
  • Snooze: a ticket has On hold instead. Snoozing one anyway (with bulk actions or the API) puts it On hold until that time.
  • When a ticket is solved, the customer is asked to rate the conversation, the same as when a chat is closed.

Priority levels

Every conversation, ticket or not, has one of four priority levels: Low, Normal, High and Urgent. Set it from the conversation header or the details panel. Sort the list by Priority first to keep urgent ones on top. The old priority flag is the same as High, so conversations you flagged before keep their place. P still switches between High and Normal.

Ticket types, forms and fields

A ticket type says what kind of request it is. Each type has a name, an emoji and a colour, and can also have:

  • a usual priority and a team to send new tickets of this type to;
  • its own due times (see Due times), instead of the workspace’s;
  • Customers can choose it, so it shows in the messenger’s ticket form;
  • a form: the fields a ticket of this type asks for, which of them are required, and which ones the customer fills in.

Fields hold the details you need, like an order number, a device or a date. A field can be short text, long text, a number, a dropdown, multiple choice, a checkbox, a date, an email address or a link. Mark a field Needed to solve and a ticket can’t be solved until it is filled in. Mark it The customer can see it to show its value to the customer in the messenger. Fields and types you no longer need are archived, never deleted, so old tickets keep their values.

On every plan, a ticket has a type, a title and a description. Custom fields, required fields, more than 3 ticket types and shared views are included with Starter, Pro, Lifetime and Reseller accounts.

Ticket folders and saved views

Tickets don’t live in a second inbox. They show in your normal folders with a ticket chip, and in the inbox’s left column the Tickets group has these folders:

FolderShows
All unsolvedEvery ticket that is open, waiting on the customer or on hold.
My ticketsTickets assigned to you.
UnassignedTickets nobody owns yet.
OverdueOpen tickets past their due time (with due times on your plan).

In a ticket folder the status control above the list offers Unsolved (open, waiting and on hold together), Open, Waiting on customer, On hold, Solved, Closed and All tickets, and you can filter by type and priority and sort by Due first. Every ticket in a list shows its type, number, status, priority and due time.

Saved views keep a set of filters (status, type, priority, assignee, team, tag, channel, overdue) as a folder of their own, such as “Urgent bugs” or “Billing waiting on customer”. Your views are only yours; workspace admins can also share a view with the whole team. Views also work for conversations that are not tickets.

Due times and overdue tickets

In Settings → Tickets you can set, for each priority level, how long your team has for the first reply and to solve a ticket. A ticket type can have its own times instead. The times are calendar hours (nights and weekends count), and they are worked out again when the priority or the type changes, unless a teammate set the due date by hand.

  • A ticket is overdue when it is Open and either its solve time has passed or its first-reply time has passed without a reply. Waiting and on-hold tickets are never overdue.
  • Overdue tickets show a red Overdue badge and move into the Overdue folder. The assignee, or the workspace’s owners and admins when nobody is assigned, get one alert in the bell and as a push notification.

Due times, the Overdue folder, overdue alerts and the SLA numbers in Reports are included with Pro, Lifetime and Reseller accounts. After a downgrade, due times are hidden and nobody is alerted; nothing is deleted.

In the messenger

With tickets on, the messenger gets a Tickets tab. Customers see their tickets with the status in their own language, open one to read and answer it, and can send a new ticket with a short form: the type, the type’s fields for customers, a title, a description and attachments. You can hide the tab, or keep the list and turn off the form, in Settings → Tickets.

  • Customers see tickets of their own conversations only. Tickets that came by email show in the messenger only for verified signed-in users with that email address.
  • A ticket sent from the messenger is not answered by the AI assistant or a chatbot, unless its type has AI assistant answers first on.
  • Open the Tickets tab or the form from your own code: TalkingDot('showSpace', 'tickets') and TalkingDot('showNewTicket', typeId). See the JavaScript API.

Emails to customers

Customers get an email when their ticket is opened, and when it is waiting for their reply, solved or closed. Each one can be turned off in Settings → Tickets.

  • The “ticket opened” email goes only to an email address the customer has proven: from a signed-in user, an email the customer sent you, or an address confirmed with a code; otherwise the confirmation shows in the messenger only. Status emails also go to other addresses once your team has replied in the conversation. See ticket emails for the details.
  • Replies your team sends to a ticket have the number and the title in the subject, like [#1042] Printer won’t connect, and the status under the message. Tickets that came by email keep their own subject, so they stay in the same email thread.
  • The customer can answer any of these emails to continue (see replying by email). Every email has an unsubscribe link.
  • Tickets on WhatsApp, Telegram, Instagram and Facebook Messenger don’t get automatic status messages, because those apps only allow replies for a short time.

Automation and macros

  • Rules in Automation → Rules can run when a ticket is created (as well as when a visitor starts a conversation). Their conditions can check the ticket type, the priority, the ticket source (a teammate, the messenger form, the API, a rule, an AI app or email) and each custom field. Their actions can make it a ticket, set priority, set ticket status and set ticket type.
  • Macros (saved replies with actions) can set the priority level, the ticket status and the type. The status and type only change tickets; a plain conversation ignores them.

Reports

Reports → Tickets shows tickets created and solved over time, the median time to the first reply and to solve, tickets by type, priority and where they came from, the tickets waiting right now by status, how often tickets were reopened, how many are overdue now and, with due times on your plan, the share solved in time. Download it as a CSV file.

In the phone app

The Android and iPhone app (version 1.3 and later) shows the number, status and priority of each ticket in the list and has the ticket folders. In a ticket, the card at the top changes the status, the priority and the type, and fills in the fields; ⋯ → Make ticket turns a conversation into a ticket.

REST API, webhooks and MCP

  • The REST API lists, creates and updates tickets, and returns the ticket with every conversation.
  • Webhooks send ticket.created, ticket.status_changed, ticket.updated and ticket.overdue.
  • The MCP server lets AI apps find tickets, make them and change their status.

Good to know

  • Merging: when you merge two tickets, the one you keep keeps its type and fields (empty fields are filled from the other one), the busier status and the earlier start time. Merging a ticket into a plain conversation moves the ticket there.
  • Deleting: a ticket is deleted with its conversation, including by your workspace’s auto-delete period. Unsolved tickets are not removed by the plan’s history limit.
  • Data export: conversation exports have the ticket columns at the end.
  • Free plan limit: a conversation locked by the Free plan’s monthly limit can’t become a ticket until the plan is upgraded.
Last updated November 18, 2026 Something unclear? Tell us