Administration
Commands for server setup, posting ticket panels, in-Discord configuration, diagnostics, auto-close, approvals, and bulk deletion
These commands change how the ticket system works for the whole server. Most require Discord permissions such as Administrator, Manage Channels, or Manage Messages rather than a staff role; each command lists who can run it.
/setup
Create the Discord categories, channels, and roles the ticket system needs. Has no options and asks no questions unless it finds existing resources. The setup form on your server creates the same set, or only the parts you have not picked, with Create them for me (see Configuration).
/setupWho can run it: members with Administrator, or with both Manage Channels and Manage Roles. The command is hidden from everyone else in Discord's command list.
What the bot needs: Manage Channels and Manage Roles at the server level (or Administrator). Without them the command stops with TC002 before creating anything.
What it creates
| Resource | Type | Purpose |
|---|---|---|
| 🎫 Tickets | Category | New ticket channels are created here |
| 📁 Closed Tickets | Category | Closed tickets are moved here |
| 📝 Ticket Logs | Category | Holds the two channels below |
#ticket-logs | Text channel | Ticket events, feedback, and staff actions |
#ticket-transcripts | Text channel | Transcripts posted when tickets close |
| Ticket Admin | Role | Full ticket management access. Named TicketCord Admin on the Free plan |
| Ticket Support | Role | Basic ticket access. Named TicketCord Support on the Free plan |
The categories and channels are created with permission overwrites so that the two roles and the bot can see them and @everyone cannot. If Discord will not let the bot place the new roles below its own role, the confirmation shows a Role Position Warning; move the bot's role above the new roles in Server Settings → Roles.
The confirmation lists what was created and the next steps, with a Finish setup button that opens your server in the dashboard.
If resources already exist
When /setup finds categories, channels, or roles that look like an earlier ticket setup (for example a category with "ticket" in its name, a #logs or #transcripts channel, or a role named like Ticket Support), it shows Existing Setup Detected with three buttons:
| Button | Result |
|---|---|
| Create Anyway (New Names) | Creates a second set named 🎫 TicketCord Tickets, 📁 TicketCord Closed, 📝 TicketCord Logs, #ticketcord-logs, and #ticketcord-transcripts |
| Use Existing (Recommended) | Creates nothing; select your existing resources in the dashboard (the reply has a Finish setup button) |
| Cancel | Makes no changes |
/setup only creates Discord resources. The bot does not handle tickets until you select those resources and save the configuration in the dashboard. See Configuration.
Errors: TC002 (you lack the permissions, or the bot lacks Manage Channels and Manage Roles), TC008 (the bot could not read the server's roles or channels; try again), TC019 (the server is at Discord's limit of 500 channels; delete unused channels and run it again), TC000 (creation failed part-way; the message lists any leftover resources to delete before retrying).
/embed
Post a saved embed (a ticket panel or any other designed message) into a channel.
/embed <name> [channel]| Option | Type | Required | Allowed values | Default |
|---|---|---|---|---|
name | Text (autocomplete) | Yes | The name of an embed saved in the dashboard | none |
channel | Channel | No | Any text or announcement channel that is not a ticket | The current channel |
Who can run it: members with Manage Messages. Autocomplete only lists embeds to people with that permission.
What happens: the embed is sent to the channel with its buttons or dropdown. Ticket buttons on it are live immediately. The reply, shown only to you, has a Jump to message button. If the message was posted but its button settings could not be saved, the reply says so: send the embed again so its buttons work.
Example
/embed name:support-panel channel:#get-helpDesign embeds under Panels → Ticket panels in the dashboard. Set an embed's description there and it appears next to the name in autocomplete.
Errors
| Code | When |
|---|---|
| TC002 | You lack Manage Messages, or the bot lacks View Channel, Send Messages, or Embed Links in the target channel |
| TC004 | No embed with that name, or the channel no longer exists or the bot cannot access it |
| TC011 | The server is not configured, or no embeds have been created yet |
| TC012 | The embed uses an emoji the bot cannot use (deleted, or from a server the bot is not in) |
| TC017 | The target channel is a ticket channel |
/config
Open an interactive settings panel for the server inside Discord.
/configWho can run it: server administrators and staff. Only the bot owner or the Discord server owner can change staff roles there; anyone else who tries gets TC002 ("Only the bot owner or the server owner can change staff roles.").
What it shows
| Section | Control |
|---|---|
| Staff roles | Change button; select up to 10 roles. Bot owner or Discord server owner only |
| Transcript channel | Change button. Without one, transcripts go to the logs channel (Same as logs in the dashboard) |
| Logs channel | Change button, or remove the channel |
| Auto-close | On/Off toggle and the current time. Turning it on sets 1 day (1,440 minutes); change the time with /auto-close or in the dashboard. Basic plan or higher |
| DM on close | On/Off toggle. The same setting as Message the member in Closing tickets → Closing rules |
| Auto-delete | On/Off toggle. The same setting as After closing set to Delete the channel in the dashboard |
| Ticket categories | Dropdown that starts with the current categories selected. What you select replaces the list, so keep the ones you want |
| Refresh | Reloads the panel with the saved values |
| Open dashboard | Opens your server in the dashboard, where every other setting is |
Some settings are managed from the dashboard only; the panel says so when you press a control that is not available in Discord (TC018).
Each change saves only that one setting, so the rest of the server's settings stay as they are.
Errors: TC002 (not an administrator or staff, or changing staff roles without being the bot owner or the Discord server owner), TC012 (more than 10 staff roles selected), TC014 (turning on auto-close on the Free plan), TC017 (run in a DM), TC000 (the server's settings could not be loaded; try again).
/diagnose
Check the bot's permissions and the server configuration, and list what is wrong.
/diagnoseWho can run it: staff, or the server owner.
What it checks
| Category | Check |
|---|---|
| Logs channel | Exists, and the bot can view it and send messages |
| Transcript channel | Exists, and the bot can view it, send messages, and attach files |
| Ticket category | Each configured open-ticket category exists and the bot has View Channel, Send Messages, and Manage Channels in it, plus Manage Roles (shown as Manage Permissions in a category's settings) when tickets open as channels or ModMail is on |
| Closed category | Each configured closed-ticket category exists and the bot has View Channel, Send Messages, and Manage Channels in it |
| Thread channel | With thread tickets on: the server's thread channel is selected and exists, can hold the thread type (a text channel; public threads can also use an announcement channel), and the bot has View Channel, Send Messages in Threads, and Create Private Threads or Create Public Threads (matching the thread type) in it |
| Thread management | With thread tickets on: the bot has Manage Threads in the thread channel. Missing it is a warning, because tickets still open without it, but the bot then cannot delete thread tickets, rename archived ones, or purge them |
| ModMail category | With ModMail on and a ModMail category selected: it exists and the bot has View Channel, Send Messages, Manage Channels, and Manage Roles (shown as Manage Permissions in a category's settings) in it |
| ModMail waiting on staff, ModMail waiting on member | With ModMail on and its tickets sorted by who needs to reply: each selected category exists and the bot has View Channel, Send Messages, and Manage Channels in it |
| ModMail ping roles | With ModMail on: every role pinged for a new ModMail ticket still exists |
| Staff roles | Every configured staff role still exists |
| Bot permissions | The bot has Manage Channels, Manage Roles, Send Messages, View Channel, Manage Messages, Embed Links, Attach Files, and Read Message History at the server level (or Administrator). Without Manage Roles the bot cannot close channel tickets. Missing only Manage Roles is a warning when every ticket is a public thread and ModMail is off |
The result, shown only to you, lists Errors and then Warnings, each with what is wrong and how to fix it, and then counts the checks that passed. Open dashboard opens your server in the dashboard. If the checks run out of time, the result says some were skipped; run the command again. Run it first whenever tickets stop being created. A thread channel picked for a single panel button is not checked; only the server's thread channel is.
Errors: TC002 (not staff or the server owner), TC008 (your staff role could not be checked; try again), TC011 (the server is not configured yet), TC000 (the result could not be shown; try again).
/auto-close
Set how long a ticket may stay inactive before it is closed automatically.
/auto-close <time>| Option | Type | Required | Allowed values |
|---|---|---|---|
time | Text | Yes | A duration such as 30M, 2H, or 1D, or off (any case) to disable. Minimum 15 minutes, maximum 30 days |
Who can run it: server administrators.
Plan: Basic or higher.
What happens: open tickets with no messages for the configured time are closed automatically. Closed tickets are not affected. The private confirmation, Auto-close is on, shows the new time, or Auto-close is off when you pass off. The same setting is the Auto-close card under Closing tickets → Auto-close and reminders in the dashboard, where you can also enable reminders before the close (Basic and higher). A reminder is a message too, so it restarts the timer: the ticket closes one full auto-close time after the last reminder.
Examples
/auto-close time:2D
/auto-close time:offErrors: TC012 (unrecognised format, under 15 minutes, or over 30 days), TC014 (Free plan), TC017 (run in a DM), TC002 (not an administrator).
/approval
Request, decide, and check approvals for sensitive actions such as refunds. Run inside the ticket the request belongs to.
/approval request <type> [reason] [urgency] [amount] [custom_type]
/approval approve [reason]
/approval reject <reason>
/approval statusPlan: Enterprise only. The approval process must also be enabled and configured in the dashboard under Staff → Approvals (Approver role, Actions that need approval, Time limit, and optionally Logging).
request options
| Option | Type | Required | Allowed values |
|---|---|---|---|
type | Choice | Yes | refund, ban, policy_exception, escalation, custom |
reason | Text | No | Free text, up to 1,000 characters. Required when the server requires a reason for requests |
urgency | Choice | No | low, medium, high |
amount | Number | No | Any number; meant for refunds and other financial requests |
custom_type | Text | No | Up to 100 characters. Required when type is custom, and must be one of the server's custom approval types |
approve takes an optional reason. reject requires a reason. Both allow up to 1,000 characters. status has no options; it shows the request's ID, type, requester, reason, and when a pending request times out.
Who can run it: staff can request and view status; the ticket's member cannot see the status. Only members holding the configured approval role can approve or reject. Every reply is shown only to you.
What happens
Staff submit a request
A card with the request ID, type, urgency, amount, and reason is posted in the ticket, and the customer sees a note that their request is under review.
Approvers are notified
The approval role is pinged with the request details. If a timeout is configured, the request expires after that many hours.
An approver decides
/approval approve or /approval reject records the decision, names the approver, and notifies the customer of the outcome.
The decision is logged
When Logging is on, the decision, approver, and response time are posted in the Approval decisions channel chosen under General → Where the bot posts, or in the logs channel while that is Same as logs.
Errors
| Code | When |
|---|---|
| TC014 | The bot owner is not on Enterprise |
| TC018 | The approval process is not enabled, or the request type is not enabled for this server |
| TC011 | Approvals are not configured for this server |
| TC002 | Non-staff tried to request or view the status, or someone without the approval role tried to approve or reject |
| TC012 | reject without a reason, a request without a reason when the server requires one, or custom without custom_type |
| TC015 | The ticket already has a pending, approved, or rejected request; or there is no pending request to decide; or another approver already decided |
/purge
Delete ticket channels in bulk. This cannot be undone.
/purge [type]| Option | Type | Required | Allowed values | Default |
|---|---|---|---|---|
type | Choice | No | all, open, closed | all |
Who can run it: the server owner only. Nobody else can run the command or press its confirmation button.
What happens
- The bot counts the matching tickets and shows a warning with the number of channels to delete, the scope, and a reminder that transcripts not already exported are lost.
- Press Confirm Purge to continue or Cancel to stop.
- Every matching ticket channel is deleted and each ticket is marked deleted, so it no longer counts toward open ticket limits. Ticket records stay in the dashboard for analytics.
- A results card lists how many tickets and channels were deleted and how many channel deletions failed. Channels that were already gone count as deleted. A ticket whose channel could not be deleted is kept, so check the bot's permissions on it and run
/purgeagain. Thread tickets the bot could not delete because it lacks Manage Threads in their thread channel are counted separately; their threads stay and the tickets are not marked deleted.
Example
/purge type:closedFor routine cleanup, set After closing to Delete the channel in the dashboard (Closing tickets → Closing rules) so closed tickets remove themselves, instead of purging by hand.
Errors: TC002 (not the server owner), TC012 (an outdated confirmation button).
Common questions
I ran /setup but the bot still says the server is not set up.
/setup only creates Discord resources. Open your server in the dashboard, pick the categories, roles, and channels it created in the setup form, and click Finish setup. Tickets work only after the configuration is saved.
Can I run /setup again?
Yes. It detects the existing resources and offers to create a second set with TicketCord-prefixed names, use the existing ones, or cancel. Nothing is deleted.
Why is /setup not in my command list?
Discord hides it unless you have Administrator, or Manage Channels and Manage Roles.
/embed says the embed contains an invalid emoji.
The embed uses a custom emoji that was deleted or belongs to a server the bot is not in. Edit the embed under Panels → Ticket panels, replace the emoji, and post it again.
Can /auto-close warn people before closing?
The command only sets the time. Reminders before the close are configured in the dashboard, in the Reminders card under Closing tickets → Auto-close and reminders (Basic and higher), and their wording on Messages.
Who can approve an approval request? Only members with the Approver role selected under Staff → Approvals in the dashboard. Staff without that role can request and check status but cannot decide.
Does /purge delete transcripts?
It deletes the ticket channels. Transcripts already posted to the transcript channel (or the logs channel) stay there; anything not yet exported is lost.
Join the support Discord and ask the team
Was this page helpful?
Last updated on