Working with Tickets
When ticketing is on, conversations that need follow-up can become tickets. A ticket is the same conversation with a few fields added: a number (#1042), 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 Setting Up Ticketing.
How a conversation becomes a ticket
- From the AI agent: 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's how it's set.
- From email: each new email thread, when that's switched on.
- By you: Make ticket in the conversation's ⋯ menu, or press T with the conversation open.
- New ticket (the + next to Tickets in the sidebar) for a phone call or someone at the desk: the requester's name and email, a subject and a first note. Replies go by email.
The AI writes a subject for each new ticket, and for a handoff it notes what your help articles didn't cover.
Ticket views
Under Tickets in the inbox sidebar are My tickets, Unassigned, Overdue (in red), All tickets 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.
The ticket table
| Part | What it does |
|---|---|
| Tabs | Narrow by status: Active (open, pending and on hold), Open, Pending customer, On hold and Solved, each with its count. |
| Search | Matches the subject, the requester's name or email, the ticket number and message text. Searching #1042 opens that ticket. |
| Filters | Team, Priority, Assignee, Type, Channel, Due and Tags, plus Created, Updated, Requester, Source and Account under + More filters. Clear all resets the filters and search, not the tab. |
| Sorting | Click a column heading, and again to reverse it. The newest updated tickets come first by default. |
| Bulk actions | Tick rows (or press X on a row) and a bar appears: Assign, Set status, Priority, Add tag and Merge (into the first ticket ticked; the same customer's only). Tick the header box to select the page, then Select all … matching for every ticket the filters match, up to 1,000. |
| Export | Downloads the current result as a CSV file. |
| Save view | Keeps the tab, filters, search, sort and columns as a view of your own under Tickets. Admins can share a view with the whole team. |
| Bottom bar | Rows per page, Columns (show, hide and reorder them), density and the pages. Your columns, density and rows per page are remembered in your browser. |
Keyboard: ↑/↓ move between rows, Enter opens one, X ticks it. Ctrl-click (⌘-click on a Mac) opens a ticket in a new tab.
Working a ticket
A ticket opened from the table has a bar on top with ← back to the view (same tab, filters, sort and place in the list), what the view is filtered by, and ‹ › (or J / K) to step through the tickets without going back.
Statuses
| Status | Means |
|---|---|
| Open | It's your team's turn |
| Pending customer | You're waiting on the customer. The due clock stops. |
| On hold | You're waiting on someone else. The due clock stops. |
| Solved | Done. The customer can still reply, which reopens it. |
| Closed | Locked, 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. |
A customer replying on a Pending customer, Solved or Closed ticket sets it back to Open. It stays with your team; it never goes back to the AI.
Replying
- Send is a split button: Send and set Pending by default. The arrow beside it has Send and set Solved, Send and keep Open and Send and set On hold, and the inbox remembers your last choice.
- If the status you send with takes the ticket off the tab you're on (say, Send and set Pending on the Open tab), the next ticket opens, with Undo.
- Next to the Reply and Note tabs, via Chat ▾ shows where the reply goes. For a chat customer with an email address on file, you can switch it to Email.
- Changing the status in the details panel sends nothing to the customer.
- Replying on a Closed ticket asks whether to reopen it first.
The details panel
- Ticket: Status, Priority, Assignee, Team, Type, Due (with whether the first reply was on time; Change sets it by hand), Tags and any custom fields. Type a custom field's value and press Enter or click away to save it.
- Requester: the customer, their account, and links to their earlier tickets and chats.
- Linked tickets: + Link ticket adds a related ticket by its number; the link shows on both.
- GitHub: when your admin has listed your repositories, + Add links an issue or pull request by its number or address, shown as, for example, web-app #482 ↗. Up to 10 per ticket.
- AI agent: what the AI did before the handoff and, when it couldn't finish, what your help articles didn't cover, with Draft article from this ticket. 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.
- Activity: the ticket's changes, newest first, such as "You set the status to Pending customer".
On a closed ticket the fields are read-only, with Reopen in the header. Linked tickets, GitHub issues and the account stay editable.
In the thread
A ticket made from a chat with the AI folds that chat into one line (Show chat opens it), with the AI's handoff summary underneath. Customer messages are tagged Chat, Email or WhatsApp. Status, priority, assignment and merge changes appear as grey lines.
Other actions
- Rename a ticket by clicking its subject (Enter saves, Esc cancels).
- Merge brings another of the same customer's conversations or tickets into this one and closes it.
- The ⋯ menu has Print, Copy link and Remove ticket (it stays a conversation).
- Type
/ticket_statusin the reply box to post the ticket's status as a card only your team sees, or/ticket_status 1042to check another ticket. See Using the Chat Inbox.
Emails the customer gets
A ticket opened from an email, or with New ticket, sends the customer a We've received your support request email with the ticket number, unless your admin has switched it off. Replies by email show the ticket's status and progress, come from your first name and team (for example Rob from Acme Support), and can carry the ticket number in the subject. Emails stay in one thread, so the customer can simply reply.
If your team uses Freshdesk instead of Docent's tickets, see Connecting Freshdesk.