Discord ticket dashboard and web inbox. Reply from either surface.
Discord is useful for conversation; the dashboard inbox is designed for support work. Triage, prioritise, and resolve from a focused view while the ticket stays connected to Discord.
No card required. After 14 days the account moves to Free, which shows TicketCord branding, unless you pick a plan. Basic and up remove the branding.
Discord was not built for support shifts. This inbox is.
Dense lists, focused shortcuts, internal notes, and retention-aware ticket search. The same conversation on a surface designed for work.
Six workflow capabilities.
One queue across every bot
Triage from one inbox across the servers and bots the signed-in account can access.
Filter the work
Filter by status, tag, priority, or text search to find unassigned and high-priority tickets.
Staff-only notes
Internal notes remain staff-only and stay with ticket metadata after closed-ticket content is purged.
Retention-aware search
Closed-ticket content remains searchable until its configured retention policy purges it. Ticket metadata, purge audit fields, and staff-only internal notes remain.
Reply from either surface
Dashboard replies appear in Discord, while Discord replies are reflected in the dashboard workflow.
Designed for support shifts
Dense lists, a predictable layout, and light and dark themes support longer triage sessions.
Dashboard replies land in Discord. Discord replies land back in the dashboard.
The reply box posts up to 2,000 characters straight into the ticket channel, and the timeline updates live as staff or the customer add messages in Discord, so nobody has to refresh to see the latest line. The reply box is text only: images and files still go through Discord. In a ModMail ticket the bot sends your reply to the member by DM.
Who can work a ticket from the inbox.
Access follows the same permissions as everywhere else in TicketCord: nobody sees a ticket in the dashboard who could not already see it in Discord or the server's staff channels.
Staff you add
Everyone with dashboard access can work tickets for the bots they own or manage. The bot owner adds staff on the Staff tab; a handful of actions, including permanently purging a deleted ticket, stay owner-only.
Included on every plan
The dashboard ticket queue is part of every plan, for every bot you own or manage. Other dashboard areas are plan-gated separately, such as AI drafting on Pro and Enterprise.
Filters and saved views
Filter by status, priority, assignment, access, bot, or tags, then save the combination as a view. Keep up to 25 saved views and mark one as your default so the page opens on it.
Internal notes stay internal
Notes on the Notes tab are visible only to dashboard users with access to the ticket. They are never shown to the ticket creator, in Discord or the dashboard.
A support shift, start to finish.
None of this needs a second tool. The same ticket, roles, and history you already have in Discord show up in the dashboard, just arranged for someone working through a queue instead of a single channel.
- 01
Start from a saved view
Open Mine or Unassigned to see only what needs you, or build a filter combination once and save it as your own view.
- 02
Work the ticket
Read the timeline and internal notes, reply from the dashboard or claim it and continue in Discord, and set a priority so the queue sorts itself.
- 03
Close, export, and move on
Close from the toolbar and export a transcript in HTML, JSON, CSV, or PDF when you need a copy. The ticket drops out of your open queues on its own.
Made for triaging at scale.
Turn on Select mode, then tick the checkbox in the list header to select every ticket on the current page, then close, claim, or tag them together. Choose Done selecting to leave selection mode. Ticket actions are point-and-click today.