{"Status":true,"Message":"","Response":{"post":{"postuid":"d353e517-63c7-41e7-a816-90a5b3733fbf","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"fc6490ac-7527-4f49-b06e-46f701280e85","title":"Setting Up Ticketing","slug":"article/setting-up-ticketing","html":"\u003Cp\u003ETicketing turns conversations that need follow-up into tickets. A ticket is the same conversation with a few fields added: a number (such as \u003Cb\u003E#1042\u003C/b\u003E), 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 \u003Ca href=\u0022/article/working-with-tickets\u0022\u003EWorking with Tickets\u003C/a\u003E.\u003C/p\u003E\u003Cp\u003ETo set it up, open your messenger and click \u003Cb\u003ETicketing\u003C/b\u003E in its sidebar. Owners and admins can change it.\u003C/p\u003E\u003Ch2 id=\u0022turning_ticketing_on\u0022\u003ETurning ticketing on\u003C/h2\u003E\u003Cp\u003EThe switch at the top of the page saves as soon as you flip it. Turning it off asks first. While it\u0027s off, the rest of the page is hidden and your settings are kept for when you turn it back on, and the inbox\u0027s ticket views are hidden too.\u003C/p\u003E\u003Cp\u003EEvery other change brings up a bar at the bottom of the page counting your changes, with \u003Cb\u003EDiscard\u003C/b\u003E and \u003Cb\u003ESave changes\u003C/b\u003E. Ctrl\u002BS (\u2318\u002BS on a Mac) saves too, and your browser warns you if you try to leave with unsaved changes.\u003C/p\u003E\u003Ch2 id=\u0022making_tickets\u0022\u003EMaking tickets\u003C/h2\u003E\u003Cp\u003EChoose what happens \u003Cb\u003Ewhen the AI agent hands off\u003C/b\u003E a chat to your team:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EDon\u0027t make a ticket\u003C/b\u003E: handoffs stay ordinary conversations.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EMake a ticket if nobody picks it up within\u003C/b\u003E a number of minutes (15 by default): quick handoffs your team answers live stay conversations, and the rest become tickets so they aren\u0027t forgotten.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EMake a ticket right away\u003C/b\u003E: every handoff becomes a ticket.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EWhatever you choose, teammates can always use \u003Cb\u003EMake ticket\u003C/b\u003E on a conversation (the \u003Cb\u003E\u22EF\u003C/b\u003E menu, or the T key) and \u003Cb\u003ENew ticket\u003C/b\u003E for phone or in-person requests.\u003C/p\u003E\u003Ch2 id=\u0022email\u0022\u003EEmail\u003C/h2\u003E\u003Cp\u003EThese settings apply once email is connected to the messenger (\u003Cb\u003EIntegrations \u2192 Email\u003C/b\u003E). Until then they\u0027re shown dimmed, with a link to set it up.\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003ESetting\u003C/th\u003E\u003Cth\u003EWhat it does\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003EEach new email thread becomes a ticket\u003C/td\u003E\u003Ctd\u003EOn by default. You can change it for each address under \u003Cb\u003EIntegrations \u2192 Email\u003C/b\u003E, for example support@ as tickets and sales@ as ordinary conversations.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EAdd the ticket number to subjects\u003C/td\u003E\u003Ctd\u003EReplies go out as, for example, \u003Ci\u003ERe: Refund request [#1042]\u003C/i\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ESend a \u0022We\u0027ve received your request\u0022 email when a ticket opens\u003C/td\u003E\u003Ctd\u003EWhen a ticket is opened from a customer\u0027s email, or by a teammate with \u003Cb\u003ENew ticket\u003C/b\u003E, the customer gets an email with the ticket\u0027s number and subject, a progress bar and what they wrote. It\u0027s in the same email thread, so replying to it adds to the ticket. Chats handed off to your team don\u0027t get one, since the messenger already tells them.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u0022View this ticket\u0022 link\u003C/td\u003E\u003Ctd\u003EOptional. An https address on your own site with \u003Ccode\u003E{number}\u003C/code\u003E where the ticket number goes, for example \u003Ccode\u003Ehttps://app.example.com/support/{number}\u003C/code\u003E. It adds a link to ticket emails. Leave it empty to leave the link out.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Ch2 id=\u0022due_times\u0022\u003EDue times\u003C/h2\u003E\u003Cp\u003EThe time to the first reply, for each priority, in hours or days:\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EPriority\u003C/th\u003E\u003Cth\u003EDefault\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003EUrgent\u003C/td\u003E\u003Ctd\u003E4 hours\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EHigh\u003C/td\u003E\u003Ctd\u003E8 hours\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ENormal\u003C/td\u003E\u003Ctd\u003E1 day\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ELow\u003C/td\u003E\u003Ctd\u003E3 days\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003ELeave one empty for no due time. The clock pauses while a ticket is \u003Cb\u003EPending customer\u003C/b\u003E or \u003Cb\u003EOn hold\u003C/b\u003E, and picks up where it left off when the ticket is open again. Overdue tickets show in red and in the \u003Cb\u003EOverdue\u003C/b\u003E view.\u003C/p\u003E\u003Ch2 id=\u0022closing\u0022\u003EClosing\u003C/h2\u003E\u003Cp\u003E\u003Cb\u003EClose solved tickets after\u003C/b\u003E 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 \u003Cb\u003EClosed\u003C/b\u003E themselves.\u003C/p\u003E\u003Ch2 id=\u0022ticket_types\u0022\u003ETicket types\u003C/h2\u003E\u003Cp\u003EThe choices for a ticket\u0027s \u003Cb\u003EType\u003C/b\u003E field, in the order they\u0027re 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.\u003C/p\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EAdd\u003C/b\u003E a type by typing it in the \u003Cb\u003E\u002B\u003C/b\u003E box at the end of the list and pressing Enter.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EReorder\u003C/b\u003E by dragging a type by its grip. With the keyboard, focus the grip and press Space or Enter to pick it up, the up and down arrows to move it, and Space or Enter again to drop it (Esc puts it back).\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ERename\u003C/b\u003E by clicking a type\u0027s name, typing the new one and pressing Enter (Esc cancels). When you save, tickets with the old name are renamed too.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ERemove\u003C/b\u003E a type with its \u2715. If tickets use it, you\u0027re asked what to change them to: another type, or none. The change is made when you save.\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022custom_fields\u0022\u003ECustom fields\u003C/h2\u003E\u003Cp\u003EExtra fields on every ticket\u0027s details panel, up to 20. Click \u003Cb\u003EAdd a field\u003C/b\u003E and give it a name and a type:\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EType\u003C/th\u003E\u003Cth\u003EUse it for\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003EText\u003C/td\u003E\u003Ctd\u003EAnything short, such as an order reference\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ENumber\u003C/td\u003E\u003Ctd\u003EA quantity or amount\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EDate\u003C/td\u003E\u003Ctd\u003EA date, such as when something is expected\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EDropdown\u003C/td\u003E\u003Ctd\u003EA fixed set of choices, which you list and can reorder like ticket types\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ELink\u003C/td\u003E\u003Ctd\u003EA value that opens a page in another system. Give it a link address with \u003Ccode\u003E{value}\u003C/code\u003E where the field\u0027s value goes, for example \u003Ccode\u003Ehttps://admin.example.com/orders/{value}\u003C/code\u003E.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003ETeammates fill fields in on the ticket\u0027s details panel, and each change is noted in the ticket\u0027s activity. A field\u0027s name can be changed later without losing the values already entered.\u003C/p\u003E\u003Ch2 id=\u0022github_freshdesk_and_reports\u0022\u003EGitHub, Freshdesk and reports\u003C/h2\u003E\u003Cp\u003ETo let teammates link GitHub issues and pull requests to tickets, list your repositories under \u003Cb\u003EIntegrations \u2192 GitHub\u003C/b\u003E. If your team works tickets in Freshdesk instead, \u003Ca href=\u0022/article/connecting-freshdesk\u0022\u003Econnect Freshdesk\u003C/a\u003E. The \u003Cb\u003ETickets\u003C/b\u003E tab of the messenger\u0027s \u003Ca href=\u0022/article/chat-reports\u0022\u003EReports\u003C/a\u003E shows tickets opened and closed, time to close, first responses against your due times, and satisfaction.\u003C/p\u003E","publish_status":0,"post_type":"Article","author":{},"featured_image_updating":false,"meta_description":"Learn how to set up and customize ticketing in your messenger, including ticket creation, email settings, due times, types, custom fields, and integrations.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":0,"date_published":"2026-11-15T17:38:42.087","date_updated":"2026-11-15T17:38:42.863","date_created":"2026-11-14T23:41:57.39"}}}