Ticketing turns conversations that need follow-up into tickets. A ticket is the same conversation with a few fields added: a number (such as #1042), a status, a priority, a due time, a type and tags. Its whole history stays in one thread, and tickets get their own views in the inbox. How your team works them is in Working with Tickets.
To set it up, open your messenger and click Ticketing in its sidebar. Owners and admins can change it.
The switch at the top of the page saves as soon as you flip it. Turning it off asks first. While it's off, the rest of the page is hidden and your settings are kept for when you turn it back on, and the inbox's ticket views are hidden too.
Every other change brings up a bar at the bottom of the page counting your changes, with Discard and Save changes. Ctrl+S (⌘+S on a Mac) saves too, and your browser warns you if you try to leave with unsaved changes.
Choose what happens when the AI agent hands off a chat to your team:
Whatever you choose, teammates can always use Make ticket on a conversation (the ⋯ menu, or the T key) and New ticket for phone or in-person requests.
These settings apply once email is connected to the messenger (Integrations → Email). Until then they're shown dimmed, with a link to set it up.
| Setting | What it does |
|---|---|
| Each new email thread becomes a ticket | On by default. You can change it for each address under Integrations → Email, for example support@ as tickets and sales@ as ordinary conversations. |
| Add the ticket number to subjects | Replies go out as, for example, Re: Refund request [#1042]. |
| Send a "We've received your request" email when a ticket opens | When a ticket is opened from a customer's email, or by a teammate with New ticket, the customer gets an email with the ticket's number and subject, a progress bar and what they wrote. It's in the same email thread, so replying to it adds to the ticket. Chats handed off to your team don't get one, since the messenger already tells them. |
| "View this ticket" link | Optional. An https address on your own site with {number} where the ticket number goes, for example https://app.example.com/support/{number}. It adds a link to ticket emails. Leave it empty to leave the link out. |
The time to the first reply, for each priority, in hours or days:
| Priority | Default |
|---|---|
| Urgent | 4 hours |
| High | 8 hours |
| Normal | 1 day |
| Low | 3 days |
Leave one empty for no due time. The clock pauses while a ticket is Pending customer or On hold, and picks up where it left off when the ticket is open again. Overdue tickets show in red and in the Overdue view.
Close solved tickets after a number of days with no reply: 4 by default, up to 90. A closed ticket is locked. If the customer replies by email after that, a new follow-up ticket is started instead of reopening the old one. Teammates can also set a ticket to Closed themselves.
The choices for a ticket's Type field, in the order they're offered. You start with Question, Problem, Refund and Feature request, and can have up to 20, each up to 40 characters. Each type shows how many tickets use it.
Extra fields on every ticket's details panel, up to 20. Click Add a field and give it a name and a type:
| Type | Use it for |
|---|---|
| Text | Anything short, such as an order reference |
| Number | A quantity or amount |
| Date | A date, such as when something is expected |
| Dropdown | A fixed set of choices, which you list and can reorder like ticket types |
| Link | A value that opens a page in another system. Give it a link address with {value} where the field's value goes, for example https://admin.example.com/orders/{value}. |
Teammates fill fields in on the ticket's details panel, and each change is noted in the ticket's activity. A field's name can be changed later without losing the values already entered.
To let teammates link GitHub issues and pull requests to tickets, list your repositories under Integrations → GitHub. If your team works tickets in Freshdesk instead, connect Freshdesk. The Tickets tab of the messenger's Reports shows tickets opened and closed, time to close, first responses against your due times, and satisfaction.