Tickets

Private support channels with configurable panels, AI summaries on close and a built-in CRM history per user.

NoxBot’s ticket system works like the ones you know - members open a private channel, your team helps, the ticket closes - but with a twist: every ticket is remembered. Close a ticket and NoxBot can summarise it with AI, then keep a per-user history so the next time someone opens a ticket your team instantly sees their past context. It is less of a queue and more of a lightweight CRM.

Panels (entry points)

A panel is the message members click to open a ticket. You can create several, each in its own channel:

Channel, title, description and button label - the embed NoxBot posts.
Topics - optional categories. With two or more topics the panel shows a dropdown so members pick what their ticket is about; with none it is a single button.
Ticket category - new ticket channels are created under this Discord category.
Support roles - the roles that can see and reply in tickets opened from this panel.
Ping role and a welcome message posted inside each new ticket.

Hit Deploy to post (or update) the panel in Discord. Buttons keep working across bot restarts, so a deployed panel never goes stale.

Opening and handling a ticket

A click creates a private channel that only the opener and your support roles can see. NoxBot posts the welcome message plus Claim and Close buttons. If the member has a history, a staff-only context card is added showing their previous tickets. Use /ticket add and /ticket remove to pull other people in or out.

Closing, transcripts and AI summaries

Closing asks for an optional reason, then:

The full message transcript is saved (if enabled).
With AI summaries on, OpenAI produces a structured summary - issue, resolution, open points, sentiment and the next best action.
A log embed is posted to your ticket log channel.
The channel is deleted - history lives in the dashboard, not in a wall of stale channels.

AI is optional

AI summaries need an OpenAI key. Add it once under Server Settings → API Keys; it is encrypted at rest and powers both ticket summaries and NSFW image moderation. Without a key, tickets still work - you just skip the summary.

The CRM view

Every ticket is stored against the user who opened it. The dashboard’s Tickets tab lists all tickets with a user filter; open one to read its transcript and summary. Each user also has a profile page with their ticket count, recent topics, first/last seen and a private staff notes field - so recurring issues and context are never lost between tickets.

Commands

/ticket add - add a user to the current ticket.
/ticket remove - remove a user from the current ticket.

Claiming and closing are handled by the buttons inside each ticket.

Previous Moderation Next Giveaways