Tickets
Key features
Panel-based ticket forms
Publish one or more ticket panels, each with its own form, category prefix, intro message, visibility, and staff routing. Members open tickets from the panel and Nox collects the configured answers before creating the thread.
Private or public ticket threads
Tickets can open as private support threads or public threads, depending on the form configuration. Nox records the created thread, runs the configured on-open actions, adds the right people, and keeps the dashboard linked to the conversation.
On-open and on-close actions
Run an ordered action list when a ticket opens and when it closes — reply to the member in the thread, send a channel message, or assign a role. The on-open list must include at least one reply, which replaces the old separate intro message and mention-role fields.
Staff claim, priority, close, and reopen controls
Staff can claim open tickets, set priority, close resolved requests, and reopen previous threads with the ticket command. Priority changes are limited to the current claimant so ownership stays clear.
Auto-close for stale queues
Auto-close rules can close tickets after inactivity or after a member has waited too long for a staff response. Nox recalculates deadlines when people post in the ticket thread.
Best for
Support queues where staff need a private, accountable place to handle member requests.
Applications, appeals, reports, or onboarding flows that need different forms and prefixes.
Communities that want ticket cleanup without manually watching every inactive thread.
How it works
Create a ticket form
In the dashboard, staff configure the panel channel, form fields, visibility, prefix, on-open and on-close actions, and optional auto-close behaviour. Saving the form sends or updates the Discord panel message.
A member opens a ticket
The member clicks the panel, fills out the modal, and submits it. Nox checks that the form still exists, claims the interaction to prevent duplicates, creates the thread, stores the ticket, and replies with the result.
Staff work the thread
Staff use the ticket command to claim, close, reopen, or set priority. Nox records ticket state, updates activity, and applies thread changes such as archive, lock, or reopen.
Nox keeps deadlines current
Messages inside an open ticket update the last staff or member response time. When an auto-close deadline is due, Nox closes the ticket and archives the thread, retrying temporary Discord failures.
Setup checklist
Choose the channel where the ticket panel should be published.
Decide whether each form should open private or public threads.
Write form fields that collect enough context before staff enter the conversation.
Set the on-open actions (including the required reply) and any on-close actions members and staff should see.
Configure auto-close only after deciding how long members and staff should have to respond.
Give staff the ticket feature role or Discord permissions required to manage ticket threads.
Ticket actions
Each ticket form runs two ordered action lists — one when a ticket opens and one when it closes.
| Trigger | Runs |
|---|---|
| On open | When a member opens a ticket (must include a reply) |
| On close | When a ticket is closed (optional) |
| Action | What it does |
|---|---|
| Reply | Post a message in the ticket thread |
| Send message | Post a message to a chosen channel |
| Assign or remove role | Grant or take a role from the member |
Up to eight actions across both lists. The on-open list must include at least one reply, which becomes the member's first message in the thread.
Important notes
Ticket setup in the dashboard is separate from live Discord permissions. A form can save successfully but still fail later if Nox loses thread or message permissions in the panel channel.
Ticket opening is protected against duplicate modal submissions. If Discord retries the same interaction, Nox reuses the existing ticket when it can.
If thread creation fails before the ticket is stored, the member can retry. If a later setup step fails, the ticket may remain open and Nox records an Errors page entry for staff to review.
Auto-close deadlines are scheduled. If Nox is offline, due closes are handled when it runs again.
Priority is a staff coordination signal, not a Discord permission. Only the current claimant can change it from the ticket command.
Troubleshooting
The panel button does not open a ticket
Check that the form still exists, the panel message is current, and Nox can see the panel channel. Re-publishing or repairing the form from the dashboard refreshes the Discord panel message.
Tickets are not creating private threads
Verify that Nox can create private threads, send messages in threads, and add members to the target channel. Missing thread permissions usually appear as a ticket error or a member-facing open failure.
Auto-close did not happen when expected
Check whether the ticket received a staff or member message that moved the deadline. If the deadline is still due, review unresolved ticket errors and confirm Nox can archive and lock the thread.
Commands
The live slash-command reference from Discord, including options and default permissions.
/tickets claim
Claim the current ticket thread.
/tickets close
Close the current ticket thread.
/tickets note
Add an internal staff note to the current ticket.
/tickets priority
Set the priority for the current ticket thread.
/tickets reopen
Reopen a previously closed ticket.
/tickets unclaimed
List unclaimed open ticket threads.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
