Reply anywhere. One ticket, both surfaces.
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.
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.
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.