User commands

Available to all members (subject to per-command permission checks).

/ping · Any member · 2s cooldown

Returns the bot's current WebSocket latency.

/uptime · Any member · 1s cooldown

Returns a formatted embed showing how long the bot has been running.

/ticket-close [status] · Staff or ticket creator · 5s cooldown

Opens the close modal for the current ticket thread. An optional status can be passed to pre-select the closing status. Only usable inside a ticket thread.

/ticket-status <status> · Staff · 3s cooldown

Updates the status of the current ticket. Accepted values: open, in_progress, resolved, cancelled, closed, pending, awaiting, referred.

/add-user <user> · Staff

Adds a Discord member to the current ticket thread so they can read and reply. Requires the invoker to be authorized on the ticket.

/remove-user <user> · Staff

Removes a Discord member from the current ticket thread. Requires the invoker to be authorized on the ticket.

Admin commands

Server configuration and ticket management commands. Most require the Discord Administrator permission or an authorized staff role.

Tip: The /ticket-config and /ticket-type commands use subcommands. Type the command name in Discord and the subcommand list will appear automatically.

/ticket-type create · Admin

Opens a creation modal to name and describe a new ticket type. After submission, the bot prompts you to select a staff role and then one or more channels where the panel will be posted.

/ticket-type list · Admin

Lists all ticket types configured for this server.

/ticket-type delete <name> · Admin

Permanently deletes a ticket type by name. Existing tickets are unaffected but no new tickets can use that type.

/ticket-config set-format <format> · Admin

Sets the guild-level default ticket number format (e.g. NOY-{number:04d}). Individual ticket types can override this.

/ticket-config view-format · Admin

Shows the current guild number format with rendered examples.

/ticket-config set-notification-channel <channel> · Admin

Configures which channel receives a ping embed when a new ticket is created.

/ticket-config view-notification-channel · Admin

Shows the currently configured notification channel.

/ticket-config clear-notification-channel · Admin

Disables ticket creation notifications.

/ticket-setup · Admin

Posts a Create Ticket button panel to the channel of your choice. Members click the button to open a new ticket without needing to know any slash commands.

/bot-profile · Admin

Sets a guild-scoped nickname, avatar, or banner for the bot in this server without affecting other servers.

/send-feedback <user> · Admin

Manually sends a feedback request DM to the specified user. Requires feedback collection to be enabled for this server.

Permission model

Ticket management operations check whether the invoking member can manage the ticket before executing. A member is authorized if they meet either condition:

  • Administrator — the member has Discord's Administrator permission
  • Staff role — the member holds the staff role assigned to the ticket's type

This applies to: Join Ticket, Add User, Remove User, Update Status, and Close.

Tip: If a ticket type has no staff role set, only members with the Administrator permission can manage those tickets.

Button interactions

In addition to slash commands, members interact with tickets through buttons posted in ticket threads:

  • Create Ticket — on the panel posted by /ticket-setup; triggers the ticket type select menu
  • Join Ticket — adds the clicking staff member to the private thread
  • Update Status — opens a status select menu inside the thread
  • Close Ticket — opens a reason modal; archives the thread and generates a transcript on submit

Tip: The panel button is the recommended way for members to open tickets. See the Ticket panel page for setup instructions.

Still need a hand?

Open a ticket in our Discord, and our team will help you out.

Open a ticket