Quick overview — what the ticket system provides

The /ticket command family lets you:

• Create and manage ticket panels (interactive button messages users click to open tickets).

• Open, close and administratively manage ticket channels (add/remove members, rename, claim/unclaim).

• Produce transcripts and list open tickets.

• Initialize the entire ticket system (roles, categories and permissions) with /ticket setup.

Ticket panels and ticket metadata persist across restarts so you can safely stage and deploy panels and still keep data intact.

Command reference

Below each command you’ll find: Purpose, Syntax / options, Examples, Who can run it, and Notes / tips.

/ticket panel

Purpose — Create or manage a dashboard-style ticket panel (open-ticket button). Use the panel builder to post a button-styled embed that members press to open tickets.

Syntax / options — use the dashboard UI or the ticketpanel subcommands (see below). The panel flows let you specify: channel, title, description, button-label, button-emoji, mention role, ticket category, SLA / auto-close and transcript wiring.
Examples

/ticket ticketpanel create channel:#support title:"Need help?" description:"Tell us what you need" button-label:"Open ticket" button-emoji:"🎫"

Who can run it — Staff/managers (as configured in Command Permissions) or server owners.
Notes / tips — Panels can be drafted, copied and pushed from the dashboard. You can append buttons or delete panels using ticketpanel subcommands. Panel messages and button metadata are persisted so panels survive bot restarts.

/ticket close

Purpose — Close the current ticket channel and lock it for further posting.

Syntax

/ticket close

Examples

/ticket close

Who can run it — The ticket claimer, ticket staff, or users with the required role/permission. Specific behaviors (who may close) are controlled by your ticket settings.
Notes / tips — Closing typically locks the channel and archives it (depending on your server’s configuration). Use /ticket transcript first if you need a saved log.

/ticket add <user>

Purpose — Add a user (friend or staff) into the current ticket so they can read/post.

Syntax / options

/ticket add user:@username

Examples

/ticket add user:@Helper
/ticket add user:123456789012345678 # user ID

Who can run it — Ticket handlers / staff (as configured).
Notes / tips — Adds the user to ticket channel permissions. Use when a ticket needs escalation or a subject-matter expert.

/ticket remove <user>

Purpose — Remove a participant from the ticket conversation.

Syntax / options

/ticket remove user:@username

Examples

/ticket remove user:@Helper

Who can run it — Ticket handlers / staff.
Notes / tips — Use to remove guests or mistakenly added members; permissions are updated on the channel.

/ticket rename <name>

Purpose — Rename the ticket channel to a clear, searchable name (for example billing-support).

Syntax / options

/ticket rename name:"billing-support"

Examples

/ticket rename name:"billing-support-42"

Who can run it — Staff/ticket handlers.
Notes / tips — Use short, informative names. The rename helps future auditing and support handoffs.

/ticket claim

Purpose — Mark the ticket as being handled by you; helpful to show ownership in busy queues.

Syntax

/ticket claim

Examples

/ticket claim

Who can run it — Staff members.
Notes / tips — The dashboard will reflect claims (so other staff know who’s handling the ticket). Use claims to avoid duplicate handling. The dashboard’s “Claim on first reply” option can automate claiming in some setups.

/ticket unclaim

Purpose — Release your claim so another staff member can take the ticket.

Syntax

/ticket unclaim

Examples

/ticket unclaim

Who can run it — The claimer or staff.
Notes / tips — Useful when handing off a ticket to a different shift or team.

/ticket transcript

Purpose — Generate and send a log (text or file) of the ticket conversation for records/escallation.

Syntax

/ticket transcript

Examples

/ticket transcript

Who can run it — Staff / handlers.
Notes / tips — Transcript generation may send a text file to a staff log channel, DM the requester, or upload to your logging store depending on server wiring. Always produce a transcript before closing if you need an audit trail.

/ticket list

Purpose — List all open tickets for staff.

Syntax

/ticket list

Examples

/ticket list

Who can run it — Staff only (command returns open ticket channels with links).
Notes / tips — Useful during shift changes or when triaging a backlog.

/ticket setup

Purpose — Initialize the ticket system: create required roles, create a ticket category and default permissions, and prepare the server to host tickets.

Syntax / options

/ticket setup

Examples

/ticket setup

Who can run it — Server owner or admins (or staff with Dashboard controls).
Notes / tips — /ticket setup automates creating the roles, categories and default channel permissions so the panel/experience works without manual channel permission fiddling. Use it first when you’re configuring the system for a server.

/ticket settings

Purpose — Display and configure the ticket system options, such as who can create tickets, auto-assign behavior, claim options, transcript wiring, and per-user ticket limits.

Syntax

/ticket settings

Examples

/ticket settings

Who can run it — Staff / managers.
Notes / tips — Use this to adjust limits (max open tickets per user), whether tickets auto-assign on open, and who the mention role should be.

Panel management (ticketpanel group)

The ticketpanel group contains helper actions for the interactive panel messages:

• /ticket ticketpanel create channel:<#> title:"..." description:"..." button-label:"..." — Post a dedicated ticket panel embed with button.

• /ticket ticketpanel addbutton message-id:<id> label:"... — Append another button to an existing ticket panel message.

• /ticket ticketpanel delete message-id:<id> — Remove an existing panel message entirely.

• /ticket ticketpanel list — List all ticket panels saved to disk.

Example (create):

/ticket ticketpanel create channel:#support title:"Need help?" description:"Click to open a ticket" button-label:"Open ticket"

These panel management commands let staff compose panels without using the dashboard UI and mirror the dashboard’s push/draft workflow.

Permissions & who can run ticket commands

• The ticket commands are staff-oriented and should be limited to managers/moderators as configured in your Command Permissions settings. The dashboard exposes Command Permissions so you can assign Manager or Custom roles to staff. Use the dashboard to make granular decisions about who may run ticketing commands.

• The bot itself must have appropriate Discord permissions to create/rename channels, manage channel permissions, and manage roles (for setup, adding/removing users, and assigning roles). If the bot cannot create channels or manage roles, /ticket setup and panel actions will fail — verify Manage Channels, Manage Roles, and Send Messages for the bot.

Persistence & data

Ticket metadata (ticket channel mappings, panel messages, roles) is persisted to disk so panels and ticket state survive restarts. This is highlighted in the project docs and means your ticket panels are durable across bot restarts.

Best practices & workflows

• Run /ticket setup first. This avoids manual permission errors and ensures the ticket category and roles are created with correct defaults.

• Use panels + mention role. Have a light-weight mention role (e.g., @Support) included in the panel so staff are alerted when a ticket opens. Don’t ping very large roles for every ticket.

• Claim and unclaim liberally. Claims reduce duplication and make ownership explicit; unclaim when handing off.

• Generate transcripts before closing. Transcripts provide an audit trail for billing, disputes and escalations.

• Use /ticket list for triage. Pull a quick list of open tickets at shift changes to ensure everything has coverage.

Troubleshooting

• “Bot failed” or panel doesn’t post: ensure the bot has Manage Channels, Manage Roles, Send Messages and Embed Links. Try /ticket setup again and check the bot’s role position (it must be above any role it needs to assign).

• “Cannot add/remove user” errors: confirm the user ID or mention is valid and that the ticket handler has rights to run the command (some servers restrict add/remove to managers).

• Transcript generation fails: ensure the bot can read message history and upload files to the staff log channel. Also confirm transcript destination is configured in ticket settings.

• Panel button not creating a ticket: check the panel message ID and that the ticketpanel is correctly associated with a ticket category that the bot can create channels under.

Quick cheatsheet

/ticket ticketpanel create channel:#support title:"Need help?" description:"..." button-label:"Open ticket"
/ticket close
/ticket add user:@User
/ticket remove user:@User
/ticket rename name:"billing-support"
/ticket claim
/ticket unclaim
/ticket transcript
/ticket list
/ticket setup
/ticket settings

(Panel helpers: /ticket ticketpanel addbutton, /ticket ticketpanel delete, /ticket ticketpanel list)