{"Status":true,"Message":"","Response":{"post":{"postuid":"3221e6b6-7c47-4fb0-913f-880c025ac377","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"fc6490ac-7527-4f49-b06e-46f701280e85","title":"Working with Tickets","slug":"article/working-with-tickets","html":"\u003Cp\u003EWhen ticketing is on, conversations that need follow-up can become tickets. A ticket is the same conversation with a few fields added: a number (\u003Cb\u003E#1042\u003C/b\u003E), a status, a priority, a due time, a type and tags. The thread keeps its whole history, whether it started as a chat, an email or a WhatsApp message. An admin turns ticketing on and sets it up; see \u003Ca href=\u0022/article/setting-up-ticketing\u0022\u003ESetting Up Ticketing\u003C/a\u003E.\u003C/p\u003E\u003Ch2 id=\u0022how_a_conversation_becomes_a_ticket\u0022\u003EHow a conversation becomes a ticket\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EFrom the AI agent:\u003C/b\u003E when it hands a chat to your team and nobody takes it within the time set on the Ticketing page, or straight away if that\u0027s how it\u0027s set.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EFrom email:\u003C/b\u003E each new email thread, when that\u0027s switched on.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EBy you:\u003C/b\u003E \u003Cb\u003EMake ticket\u003C/b\u003E in the conversation\u0027s \u003Cb\u003E\u22EF\u003C/b\u003E menu, or press \u003Cb\u003ET\u003C/b\u003E with the conversation open.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ENew ticket\u003C/b\u003E (the \u003Cb\u003E\u002B\u003C/b\u003E next to \u003Ci\u003ETickets\u003C/i\u003E in the sidebar) for a phone call or someone at the desk: the requester\u0027s name and email, a subject and a first note. Replies go by email.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EThe AI writes a subject for each new ticket, and for a handoff it notes what your help articles didn\u0027t cover.\u003C/p\u003E\u003Ch2 id=\u0022ticket_views\u0022\u003ETicket views\u003C/h2\u003E\u003Cp\u003EUnder \u003Ci\u003ETickets\u003C/i\u003E in the \u003Ca href=\u0022/article/using-the-chat-inbox\u0022\u003Einbox\u003C/a\u003E sidebar are \u003Cb\u003EMy tickets\u003C/b\u003E, \u003Cb\u003EUnassigned\u003C/b\u003E, \u003Cb\u003EOverdue\u003C/b\u003E (in red), \u003Cb\u003EAll tickets\u003C/b\u003E and any saved views. On a computer they open as a table across the whole window; on a phone, as a list. Tickets also stay in the ordinary views, with their number next to the name, and open there in the usual inbox layout.\u003C/p\u003E\u003Ch3 id=\u0022the_ticket_table\u0022\u003EThe ticket table\u003C/h3\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EPart\u003C/th\u003E\u003Cth\u003EWhat it does\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003ETabs\u003C/td\u003E\u003Ctd\u003ENarrow by status: \u003Cb\u003EActive\u003C/b\u003E (open, pending and on hold), \u003Cb\u003EOpen\u003C/b\u003E, \u003Cb\u003EPending customer\u003C/b\u003E, \u003Cb\u003EOn hold\u003C/b\u003E and \u003Cb\u003ESolved\u003C/b\u003E, each with its count.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ESearch\u003C/td\u003E\u003Ctd\u003EMatches the subject, the requester\u0027s name or email, the ticket number and message text. Searching \u003Cb\u003E#1042\u003C/b\u003E opens that ticket.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EFilters\u003C/td\u003E\u003Ctd\u003ETeam, Priority, Assignee, Type, Channel, Due and Tags, plus Created, Updated, Requester, Source and Account under \u003Cb\u003E\u002B More filters\u003C/b\u003E. \u003Cb\u003EClear all\u003C/b\u003E resets the filters and search, not the tab.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ESorting\u003C/td\u003E\u003Ctd\u003EClick a column heading, and again to reverse it. The newest updated tickets come first by default.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EBulk actions\u003C/td\u003E\u003Ctd\u003ETick rows (or press \u003Cb\u003EX\u003C/b\u003E on a row) and a bar appears: \u003Cb\u003EAssign\u003C/b\u003E, \u003Cb\u003ESet status\u003C/b\u003E, \u003Cb\u003EPriority\u003C/b\u003E, \u003Cb\u003EAdd tag\u003C/b\u003E and \u003Cb\u003EMerge\u003C/b\u003E (into the first ticket ticked; the same customer\u0027s only). Tick the header box to select the page, then \u003Cb\u003ESelect all \u2026 matching\u003C/b\u003E for every ticket the filters match, up to 1,000.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EExport\u003C/td\u003E\u003Ctd\u003EDownloads the current result as a CSV file.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ESave view\u003C/td\u003E\u003Ctd\u003EKeeps the tab, filters, search, sort and columns as a view of your own under \u003Ci\u003ETickets\u003C/i\u003E. Admins can share a view with the whole team.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EBottom bar\u003C/td\u003E\u003Ctd\u003ERows per page, \u003Cb\u003EColumns\u003C/b\u003E (show, hide and reorder them), density and the pages. Your columns, density and rows per page are remembered in your browser.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EKeyboard: \u003Cb\u003E\u2191/\u2193\u003C/b\u003E move between rows, \u003Cb\u003EEnter\u003C/b\u003E opens one, \u003Cb\u003EX\u003C/b\u003E ticks it. Ctrl-click (\u2318-click on a Mac) opens a ticket in a new tab.\u003C/p\u003E\u003Ch2 id=\u0022working_a_ticket\u0022\u003EWorking a ticket\u003C/h2\u003E\u003Cp\u003EA ticket opened from the table has a bar on top with \u003Cb\u003E\u2190\u003C/b\u003E back to the view (same tab, filters, sort and place in the list), what the view is filtered by, and \u003Cb\u003E\u2039 \u203A\u003C/b\u003E (or \u003Cb\u003EJ / K\u003C/b\u003E) to step through the tickets without going back.\u003C/p\u003E\u003Ch3 id=\u0022statuses\u0022\u003EStatuses\u003C/h3\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EStatus\u003C/th\u003E\u003Cth\u003EMeans\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003EOpen\u003C/td\u003E\u003Ctd\u003EIt\u0027s your team\u0027s turn\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EPending customer\u003C/td\u003E\u003Ctd\u003EYou\u0027re waiting on the customer. The due clock stops.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EOn hold\u003C/td\u003E\u003Ctd\u003EYou\u0027re waiting on someone else. The due clock stops.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ESolved\u003C/td\u003E\u003Ctd\u003EDone. The customer can still reply, which reopens it.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EClosed\u003C/td\u003E\u003Ctd\u003ELocked, a few days after Solved (set on the Ticketing page), or when a teammate picks Closed. An email reply then starts a follow-up ticket.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EA customer replying on a \u003Cb\u003EPending customer\u003C/b\u003E, \u003Cb\u003ESolved\u003C/b\u003E or \u003Cb\u003EClosed\u003C/b\u003E ticket sets it back to \u003Cb\u003EOpen\u003C/b\u003E. It stays with your team; it never goes back to the AI.\u003C/p\u003E\u003Ch3 id=\u0022replying\u0022\u003EReplying\u003C/h3\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003ESend\u003C/b\u003E is a split button: \u003Cb\u003ESend and set Pending\u003C/b\u003E by default. The arrow beside it has \u003Cb\u003ESend and set Solved\u003C/b\u003E, \u003Cb\u003ESend and keep Open\u003C/b\u003E and \u003Cb\u003ESend and set On hold\u003C/b\u003E, and the inbox remembers your last choice.\u003C/li\u003E\u003Cli\u003EIf the status you send with takes the ticket off the tab you\u0027re on (say, \u003Cb\u003ESend and set Pending\u003C/b\u003E on the \u003Cb\u003EOpen\u003C/b\u003E tab), the next ticket opens, with \u003Cb\u003EUndo\u003C/b\u003E.\u003C/li\u003E\u003Cli\u003ENext to the Reply and Note tabs, \u003Cb\u003Evia Chat \u25BE\u003C/b\u003E shows where the reply goes. For a chat customer with an email address on file, you can switch it to \u003Cb\u003EEmail\u003C/b\u003E.\u003C/li\u003E\u003Cli\u003EChanging the status in the details panel sends nothing to the customer.\u003C/li\u003E\u003Cli\u003EReplying on a \u003Cb\u003EClosed\u003C/b\u003E ticket asks whether to reopen it first.\u003C/li\u003E\u003C/ul\u003E\u003Ch3 id=\u0022the_details_panel\u0022\u003EThe details panel\u003C/h3\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003ETicket:\u003C/b\u003E Status, Priority, Assignee, Team, Type, \u003Cb\u003EDue\u003C/b\u003E (with whether the first reply was on time; \u003Cb\u003EChange\u003C/b\u003E sets it by hand), Tags and any custom fields. Type a custom field\u0027s value and press Enter or click away to save it.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ERequester:\u003C/b\u003E the customer, their account, and links to their earlier tickets and chats.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ELinked tickets:\u003C/b\u003E \u003Cb\u003E\u002B Link ticket\u003C/b\u003E adds a related ticket by its number; the link shows on both.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EGitHub:\u003C/b\u003E when your admin has listed your repositories, \u003Cb\u003E\u002B Add\u003C/b\u003E links an issue or pull request by its number or address, shown as, for example, \u003Cb\u003Eweb-app #482 \u2197\u003C/b\u003E. Up to 10 per ticket.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EAI agent:\u003C/b\u003E what the AI did before the handoff and, when it couldn\u0027t finish, what your help articles didn\u0027t cover, with \u003Cb\u003EDraft article from this ticket\u003C/b\u003E. That writes a draft article from how you solved it, with personal details removed, and opens it in the editor. Solving such a ticket offers it once.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EActivity:\u003C/b\u003E the ticket\u0027s changes, newest first, such as \u0022You set the status to Pending customer\u0022.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EOn a closed ticket the fields are read-only, with \u003Cb\u003EReopen\u003C/b\u003E in the header. Linked tickets, GitHub issues and the account stay editable.\u003C/p\u003E\u003Ch3 id=\u0022in_the_thread\u0022\u003EIn the thread\u003C/h3\u003E\u003Cp\u003EA ticket made from a chat with the AI folds that chat into one line (\u003Cb\u003EShow chat\u003C/b\u003E opens it), with the AI\u0027s handoff summary underneath. Customer messages are tagged \u003Cb\u003EChat\u003C/b\u003E, \u003Cb\u003EEmail\u003C/b\u003E or \u003Cb\u003EWhatsApp\u003C/b\u003E. Status, priority, assignment and merge changes appear as grey lines.\u003C/p\u003E\u003Ch3 id=\u0022other_actions\u0022\u003EOther actions\u003C/h3\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003ERename\u003C/b\u003E a ticket by clicking its subject (Enter saves, Esc cancels).\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EMerge\u003C/b\u003E brings another of the same customer\u0027s conversations or tickets into this one and closes it.\u003C/li\u003E\u003Cli\u003EThe \u003Cb\u003E\u22EF\u003C/b\u003E menu has \u003Cb\u003EPrint\u003C/b\u003E, \u003Cb\u003ECopy link\u003C/b\u003E and \u003Cb\u003ERemove ticket\u003C/b\u003E (it stays a conversation).\u003C/li\u003E\u003Cli\u003EType \u003Ccode\u003E/ticket_status\u003C/code\u003E in the reply box to post the ticket\u0027s status as a card only your team sees, or \u003Ccode\u003E/ticket_status 1042\u003C/code\u003E to check another ticket. See \u003Ca href=\u0022/article/using-the-chat-inbox#commands_and_result_cards\u0022\u003EUsing the Chat Inbox\u003C/a\u003E.\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022emails_the_customer_gets\u0022\u003EEmails the customer gets\u003C/h2\u003E\u003Cp\u003EA ticket opened from an email, or with \u003Cb\u003ENew ticket\u003C/b\u003E, sends the customer a \u003Ci\u003EWe\u0027ve received your support request\u003C/i\u003E email with the ticket number, unless your admin has switched it off. Replies by email show the ticket\u0027s status and progress, come from your first name and team (for example \u003Ci\u003ERob from Acme Support\u003C/i\u003E), and can carry the ticket number in the subject. Emails stay in one thread, so the customer can simply reply.\u003C/p\u003E\u003Cp\u003EIf your team uses Freshdesk instead of Docent\u0027s tickets, see \u003Ca href=\u0022/article/connecting-freshdesk\u0022\u003EConnecting Freshdesk\u003C/a\u003E.\u003C/p\u003E","publish_status":0,"post_type":"Article","author":{},"featured_image_updating":false,"meta_description":"Learn how to manage support tickets, including creating, viewing, updating statuses, replying, and organizing tickets efficiently in your inbox.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":0,"date_published":"2026-11-15T17:38:44.947","date_updated":"2026-11-15T17:38:45.663","date_created":"2026-11-14T23:42:53.72"}}}