Dashboard Ticket Management

Find, read, reply to, and manage tickets across all your bots from the dashboard

Tickets is the ticket queue for every bot you own or manage as dashboard staff. You can search and filter it, save your filters, open a ticket to read the full conversation and internal notes, reply, claim, close, export, and act on many tickets at once.

It is the place to work tickets when you are not in Discord, and the only place to see tickets from several servers side by side.

Opened from inside a server (with Tickets in the sidebar, or View all under Recent tickets on the server's home page), the same page shows only that server's tickets; Show all servers under the title switches back.

Everyone with dashboard access can use the Tickets page for the bots they own or manage. Some actions are owner-only, in particular Purge. Numbers and charts are on their own page; see Stats.

Go to Tickets

Finding tickets

The list updates live as tickets are created, closed, claimed, or reopened. Twenty tickets are shown per page, one row each: the member, the ticket's title, its status and time, and a line with the ticket number, ModMail or Thread for tickets opened by a DM to the bot or in a thread, priority, VIP with the role's name when a role under Priority support set it, who claimed it, and message and note counts. A closed ticket the AI solved on its own shows Solved by AI in place of Closed, in the list and on the ticket page; see Analytics for how that is decided.

Three tabs sit above the list: Open (the default, with a count), Closed (closed tickets and tickets whose channel was deleted), and All. Next to the search box:

ControlOptionsDefault
Search ticketsTicket number, the member's name or Discord ID, subject, channel name, server, or bot; up to 100 charactersempty
Filters → ServerAll servers, or one serverAll servers (or the server you came from)
Filters → BotAll bots, or one bot. Shown when you have more than one botAll bots
Filters → Your accessAll servers you can see, Servers you own, Servers where you are staff. Shown when you both own servers and are staff elsewhereAll servers you can see
Filters → TypeAny type, Channel, Thread, ModMail: how the ticket was openedAny type
Filters → PriorityAny priority, Urgent, High, Medium, Low, NoneAny priority
Filters → Claimed byAnyone or nobody, Me, Nobody yetAnyone or nobody
Filters → TagsAny number of tags; a ticket must carry every selected tagnone
Filters → OrderRecent activity first, Oldest activity first, Newest tickets first, Oldest tickets first, Recently updated first, Least recently updated first, Highest priority first, Lowest priority firstRecent activity first

Filters apply as soon as you change them. The subtitle identifies a selected server or, when only a bot is selected, the servers managed by that bot. The Filters button shows how many are active, and each active filter also appears as a chip under the search box; click a chip to remove it, or Clear all. The tag list shows the tags already used on your tickets plus the suggested tags from each server's Staff → Tags block.

The ⋯ menu next to Filters holds Select tickets (see Bulk Operations), Save these filters, and Refresh, which forces a reload with a short cooldown.

Saved views

Set up a search and filter combination, open ⋯, choose Save these filters, and give the view a name of 1 to 48 characters. Saved views appear as chips above the list; click one to apply it.

Each chip has its own menu to Rename it, Set as default (the page then opens on it) or Clear default, and Delete it. You can keep up to 25 saved views, and names must be unique. Views are personal to your account.

The ticket page

Click a ticket to open it. The header shows the member's avatar, the ticket's title, one line saying who opened it, in which server, and when, and pills for its status (Solved by AI in place of Closed when the AI solved it on its own), ModMail or Thread when it was opened that way, its priority, VIP with the role's name when a role under Priority support set it, and who claimed it. The ticket's tags are under the pills; you can add and remove them while the ticket is open. On a wide screen, AI Help, linked game accounts and the ticket summary sit in a column beside the conversation; on a narrower one they are under it.

A ticket opens on its latest message. On most screens an open ticket's reply box is in view too, so you can read and answer without scrolling the page; on a short window, scroll the page down to reach it. Scroll up in the conversation to read earlier messages.

Opening a ticket from a bot's or server's queue keeps that bot or server in the dashboard navigation. Tickets at the top of the page (Back to tickets on a phone or tablet) returns to the same list with its filters and page, including saved views, and, within 30 minutes, scrolls to the ticket you just looked at if the list still shows it (a ticket you closed is not in a list of open tickets). The browser's back button does the same. Reloading a saved view also keeps its current page; choosing a different view or changing filters starts at page 1.

When Ticket summary is on (AI assistant → Atlas), a card beside the conversation (under it on narrower screens) sums up what the member needs, with its urgency and the member's mood. Click the card to see the best place for the ticket, next steps, and what Atlas noticed. While the ticket is open, Update asks Atlas for a fresh summary (Create when there is none yet); the card says Out of date when new messages arrived after it was made. When no AI tokens are left, the last summary stays on the card and Update tells you why it cannot make a new one. See AI features.

Below are the tabs:

  • Conversation: every message and system event (opened, claimed, closed, first response recorded, and so on) in order, with the reply box at the bottom.
  • Notes: Staff notes that are internal and never shown to the member. Write in the box at the bottom (1 to 1,000 characters) and press Add note or Ctrl/⌘ + Enter. The bin button on a note deletes it after you confirm.
  • Approval: shown only when the ticket has an approval request: who asked and when, the urgency, the reason, and each decision so far. Members of the approver role get Approve (a reason is optional) and Reject (a reason is required). See Approval Workflows.
  • Mood: how the member felt from start to finish: How it started, How it ended, the Change, Ups and downs, the mood through the ticket with how many messages were positive, neutral, or negative, and the Feelings noticed. It is worked out when the ticket closes, when Mood history is on (Enterprise).

Replying from the dashboard

At the bottom of the Conversation tab, open tickets have a reply box. Type up to 2,000 characters and press Send message or Ctrl/⌘ + Enter. The bot posts your message in the ticket channel under your Discord name and avatar. Attachments cannot be sent from the dashboard. Text you have not sent, here or in the Notes tab, stays in its box when you switch tabs or open another ticket and come back. It is kept until you close that browser tab.

Mentions work as in Discord. Type # to pick a channel of the server, or @ to pick someone who wrote in the ticket; the box shows the mention by name before you send it, and Backspace removes it whole. To mention anyone else, type their mention as Discord writes it, such as <@123456789012345678>. In the conversation, mentions of channels, roles and members show their names; one whose name cannot be found, such as a deleted channel, shows as #unknown, @deleted-role or @unknown-user.

In a ModMail ticket the reply box says Reply to the member in their DMs.... Your reply works the same as one typed in the ticket channel:

  1. The bot sends it to the member by DM, signed with your team name (Support Team unless you set your own) when Hide staff names is on, and translated or polished by the ModMail translation settings.
  2. It then posts a copy under your name in the ticket channel.

Both use your versions of the Staff reply and Staff reply copy messages, if you changed them on the Messages page.

AI Help on the ticket page

When AI Help is on for the server (AI assistant → Atlas → AI Help drafts, with the Atlas switch on), an open ticket has an AI Help panel beside the conversation (under it on narrower screens). It is the dashboard version of /ai-help: it reads the ticket's opening details and its recent messages, your help content, and what Atlas remembers about the member, and only staff see it. It needs the bot owner to be on Pro or Enterprise; on a lower plan the panel says so. It is not shown for email tickets or closed tickets, and in a ticket Atlas is kept away from it says so instead of answering.

Pick what you want above the box:

  • Draft a reply: press send with an empty box for a draft, or type instructions first (up to 500 characters), such as ask for their order email. To change the draft, type what to change, such as shorter or mention the refund policy, and AI Help rewrites it. Drafts use your own writing style when you set one with /ai-style. A Note for you under a draft is something to check before sending; it is never put in the reply. Use draft puts the draft in the reply box (it asks first when the box already has text), and Try again writes a new one. Nothing is sent until you press Send message, and the reply then counts like any message you type. A draft that follows up with the member, or tells them something happened, starts with their mention (shown as @name), so sending it pings them; ask for a ping in your instructions, such as ping them, to add one. Drafts only mention people in the ticket (how pinging works).
  • Ask about this ticket: ask a question, such as What has the member already tried?, and get a short answer for you, from this ticket only. When the ticket does not say, the answer tells you.

You can switch between the two at any time in the same chat, and AI Help keeps what was said. The chat is not saved: it is cleared when you leave the ticket or reload the page. Each new draft or answer uses the bot owner's AI tokens, like /ai-help. You can send up to 10 requests a minute, one at a time.

Ticket actions

Claim (or Unclaim) and Close ticket are buttons in the header while the ticket is open; a closed ticket shows Reopen instead, except a ModMail ticket, which cannot be reopened (the member's next DM to the bot opens a new ticket). Everything else is in the ⋯ menu (More actions).

ActionWhereWhat it doesNotes
Claim / UnclaimButtonAssigns the ticket to you, or releases itSame as /claim and /unclaim
Close ticketButtonCloses the ticket with an optional reason (up to 1,000 characters)Follows the server's close settings (transcript, deletion, ratings)
ReopenButtonReopens a closed ticketNot shown for ModMail tickets. Tickets whose channel was deleted cannot be reopened
Escalate⋯ menuTransfers the ticket to a configured support team with a required reasonBasic or higher; open channel tickets only
Set priority⋯ menuNone, Low, Medium, High, or UrgentOpen tickets only
Rename ticket⋯ menuChanges the channel or thread name, up to 80 charactersOpen tickets only; the ticket number is kept, as with /rename
Add a member / Remove a member⋯ menuGrants or removes a Discord user's access to the ticketTakes a user ID; open tickets only. On thread tickets, adds the user to the thread or takes them out
Send transcript⋯ menuSends the transcript to the server's transcripts channelNot available for tickets whose channel was deleted; download it instead
PDF, HTML, JSON, CSV⋯ menuDownloads the ticket in that format
Delete⋯ menuDeletes the Discord channel or thread; click twice to confirmThe ticket stays in your history until purged

To set up destinations, the bot owner opens Staff → Staff roles and adds Escalation destinations. Escalating shares the existing conversation and reason with the receiving team and releases the current claim. Each destination can move the channel to a category and keep or remove the previous team’s role access. See /escalate for the full workflow.

Transcripts and exports

  • A single-ticket export downloads immediately in the chosen format, with metadata included. Choose the format in the ticket's ⋯ menu, or with Export as in a row's menu on the list.
  • Every transcript the bot posts in your transcripts channel has a View online button that opens the conversation in the browser, with its messages, attachments and timestamps, so nobody has to download the HTML file. The file stays attached to the same post.
  • Transcript links of the form ticketcord.com/transcripts/... (the View online button) require signing in with Discord. They open for the bot owner and for members the owner gave dashboard access under Staff → Staff roles, card Dashboard access. They are not public: anyone else who gets the link sees that they have no access.
  • To let your support staff read transcripts without giving them the dashboard, the bot owner turns on Let staff read transcripts online in the same card. A signed-in member who is staff for that ticket can then open its transcript and attachments: someone holding one of your staff roles (or, for a ticket limited to certain staff roles or handed to another team, one of those roles), the server owner, or an administrator. While a ticket is open and claimed with exclusive claims on, only the staff member who claimed it, your supervisor roles, the server owner and administrators can open it online, the same people who keep the channel in Discord. Once it is closed, all of its staff can read it again. Discord is asked each time the page loads, so removing the role ends the access within seconds. They can only read: no exports, no dashboard, no settings. It is off by default. Tickets opened before late October 2026 from a button limited to certain staff roles did not record that limit (thread tickets have recorded it since late September 2026), so any of your staff roles can open those online.
  • The online transcript shows the ticket's saved messages. Once they are removed after the time set in Keep closed tickets for (General → Privacy and data), the page still opens with the ticket's details but shows no messages. The file in your transcripts channel stays.
  • To rename or hide the button, edit Transcript post on the Messages page.
  • The transcript of a ticket opened by email holds the customer's emails, the emails sent to them and the bot's messages. What staff type in its channel is never saved, so it is not in the transcript. See Email Inbox.
  • Exporting several tickets at once is covered under Bulk Operations: the tickets you select on one page (up to 20, or 10 for PDF), delivered as a zip.

Deleting and purging

Delete is a soft delete. The ticket's Discord channel or thread is removed (an open ticket is closed first), and the ticket stays in your history under the Closed tab, with its conversation (marked Deleted in Discord) and notes. Deleted tickets cannot be reopened. Once a delete starts, Reopen is refused until it finishes, so a ticket never ends up open without its channel or thread. A panel ticket whose channel or thread is deleted in Discord directly (or with the channel its thread was in) ends the same way within about a minute while the bot is online, and stops counting toward the member's ticket limits. If the bot was offline at the time, the ticket is cleaned up the next time its member reaches the open-ticket limit. ModMail tickets are closed instead, the next time the member writes.

Purge permanently erases tickets whose channel was already deleted from TicketCord: the ticket record, stored messages and transcript links, archived attachments, staff notes, SLA and feedback data, analytics contributions, and any knowledge base learning derived from them. Select the tickets (⋯ → Select tickets) and choose Purge N from history; it appears only for deleted tickets on bots you own. It cannot be undone.

Limits and gotchas

  • Twenty tickets per page; use the tabs, search, and filters or a saved view rather than paging through hundreds.
  • Search text is limited to 100 characters and a saved view can hold at most 10 tag filters.
  • The dashboard reply box is text only. For images or files, reply in Discord.
  • Actions on the ticket page are subject to the same rules as the slash commands: for example Reopen works only on closed tickets, and Delete is not offered for a ticket whose channel is already gone.
  • Dashboard staff (people whose role the owner added under Dashboard access on Staff → Staff roles) can do everything on this page except Purge.

Troubleshooting

SymptomCauseFix
A ticket you expect is missingYou are on the Open tab, a filter or saved view is hiding it, the page shows one server only, or it belongs to a bot you do not manageSwitch to All, clear the filter chips, and click Show all servers
The reply box is not shownThe ticket is closed, or you are in read-only modeReopen the ticket
Purge is missing or skipped ticketsYou are dashboard staff rather than the bot owner, or the selected tickets still have their channelAsk the bot owner; delete before purging
Rename ticket, Add a member, and Remove a member are missingThe ticket is closed, or you are in read-only modeThese actions apply to open tickets only
"You can save up to 25 ticket views."The saved-view limit was reachedDelete a view you no longer use
"A saved view with this name already exists."Names are compared case-insensitivelyChoose a different name
Export of a large ticket failsThe export exceeded the size limitsExport in a lighter format such as JSON or CSV
Changes made in Discord do not appearThe live update was missedChoose ⋯ → Refresh

Common questions

Can I reply to a ticket from the dashboard? Yes, for any open ticket: use the reply box at the bottom of the Conversation tab, up to 2,000 characters. In a ModMail ticket the bot sends your reply to the member by DM. Attachments cannot be sent from the dashboard.

Where are the tickets from my other server? All servers appear in one list unless you opened Tickets from inside a server; click Show all servers under the title. Use Filters → Server, Filters → Bot, Filters → Your access, or search by server name to narrow it down.

Where are closed tickets? On the Closed tab. The list opens on Open; All shows both.

What is the difference between Delete and Purge? Delete removes the Discord channel and keeps the ticket, with its data, under the Closed tab. Purge permanently erases tickets whose channel was already deleted and is restricted to the bot owner.

Can a deleted ticket be restored? No. Tickets whose channel was deleted cannot be reopened. Their transcript and notes remain readable until they are purged.

Are internal notes visible to the customer? No. Notes on the Notes tab are only visible to dashboard users with access to the ticket.

How do I download a transcript? Open the ticket, click ⋯, and pick PDF, HTML, JSON, or CSV. For many tickets at once, choose ⋯ → Select tickets on the list and use Export in the selection bar.

Why do transcript links ask me to sign in? Transcript pages are private. Only a dashboard account with access to that ticket's bot can open them.

Member Profiles

Open a ticket in Tickets, then select Member profile under its heading. The profile is specific to that bot and server. Bot owners and authorized dashboard staff can see the member’s retained ticket history, visible ratings, ticket tags and handling staff. History is paginated, with 50 tickets per page. Open a ticket to read its conversation and ticket notes.

Member details holds private notes and up to 20 member tags, separate from ticket tags. Select Save details after editing. Notes support up to 4,000 characters. Each tag supports 40 characters. If another staff member saves first, reload the profile before saving your changes.

Only the bot owner can use Manage fields. Add up to 20 text fields, each with a unique key of up to 32 lowercase letters, numbers or underscores, starting with a letter. Labels support 80 characters; values support 200. Staff can fill in these fields, for example an order ID. Removing a definition hides that field. Saving member details keeps only the currently defined fields.

Use Filter members to find exact matches on a current custom field value. The results show the member count, retained ticket count and average visible rating for the matching members in this server. The member list shows up to 100 matches; totals cover all matches. These are current profile attributes, not snapshots of what the member’s fields contained when a ticket opened.

While Remember members is on under Help your staff in AI assistant → Atlas, AI Help drafts also read the member’s filled-in field values, with their labels, to fit a draft to the member. A draft never quotes the values to the member. The ticket summary does not read them.

Memory

With member memory (Pro and Enterprise), the profile shows a Memory section under Member details: short support facts Atlas learned from the member’s own messages when their tickets closed, such as their platform or setup. Each fact shows its topic, when it was last confirmed and the ticket it came from. The section is read-only: nobody can add or edit a fact. Staff can delete one fact, choose Forget everything, or choose Stop remembering to stop learning and using facts about this member until Resume remembering. These actions work on any plan and with the server setting off. Members cannot see their memory; a member who wants it shown or removed asks your staff.

Estimated Handling Time

Profiles show each participating staff member’s estimated handling minutes beside their name when recorded. The estimate is saved when a ticket closes. It adds intervals of up to five minutes between consecutive replies by the same staff member on the same ticket. Longer gaps start another session and add no time; a single reply contributes zero minutes. Reading, typing, voice conversations and work outside the ticket are not measured. Staff may work on overlapping tickets, so this is an estimate of reply sessions, not a timesheet. Older tickets without the measurement show no estimate.

Last updated on

On this page