These commands control the core ticket lifecycle and are available on all plans.
/close
Close the current ticket channel.
| Option | Type | Required | Description |
|---|
reason | Text | No | Reason for closing the ticket |
silent | Boolean | No | Close without sending a notification message |
Permission: Ticket creator or staff
What happens:
- Channel is renamed from
ticket-XXXX to closed-XXXX
- Ticket is moved to the closed tickets category
- Creator loses access to send messages
- Ticket messages are compressed for storage
- Transcript is generated (if auto-transcript is enabled)
If Skip Close Confirmation is enabled in your dashboard settings, the ticket closes immediately. Otherwise, you’ll see a confirmation dialog.
Example:
/close reason:Issue resolved
/close silent:True
/reopen
Reopen a closed ticket.
Permission: Ticket creator or staff
What happens:
- Channel is renamed from
closed-XXXX back to ticket-XXXX
- Ticket is moved back to the open tickets category
- Creator regains full access
- Status changes from “closed” to “open”
Reopening preserves the full conversation history - nothing is lost.
/claim
Claim ownership of a ticket.
Permission: Staff only
What happens:
- Your name is displayed as the ticket handler
- Other staff can see who’s working on it
- Prevents duplicate effort on the same ticket
- Claim information shows in the ticket channel
Only one staff member can claim a ticket at a time. Use /unclaim to release it.
/unclaim
Release your claim on a ticket.
Permission: The claimer or any staff member
What happens:
- Removes the claim from the ticket
- Other staff can now claim it
- Claim message is deleted from channel
Staff members can unclaim tickets claimed by others to help redistribute workload.
/add
Add a user or role to the current ticket.
| Option | Type | Required | Description |
|---|
user_or_role | User/Role | Yes | The user or role to add |
Permission: Ticket creator or staff
What happens:
- User/role gains access to view and send messages in the ticket
- A notification is sent to the channel
- Added users can participate in the conversation
Example:
/add @JohnDoe
/add @Support Team
/remove
Remove a user or role from the current ticket.
| Option | Type | Required | Description |
|---|
user_or_role | User/Role | Yes | The user or role to remove |
Permission: Ticket creator or staff
What happens:
- User/role loses access to the ticket channel
- They can no longer view or send messages
- A notification is sent to the channel
You cannot remove the ticket creator or staff roles from a ticket.
/rename
Rename the current ticket channel.
| Option | Type | Required | Description |
|---|
name | Text | Yes | New name for the ticket |
Permission: Ticket creator or staff
What happens:
- Channel name changes to
ticket-XXXX-newname
- Original ticket number is preserved
- Helps identify tickets by topic
Example:
/rename billing-issue
/rename vip-support
Channel names follow Discord’s naming rules - lowercase, no spaces, max 100 characters.
/closerequest
Request that the ticket creator close their ticket.
| Option | Type | Required | Description |
|---|
reason | Text | No | Reason for requesting closure |
Permission: Staff only
What happens:
- Creator receives a message asking if their issue is resolved
- They can choose to close the ticket or keep it open
- Useful when staff believe the issue is resolved
Example:
/closerequest reason:Your issue appears to be resolved. Please confirm!
This is more polite than closing directly - it gives the user a chance to ask follow-up questions.
Staff Tools
Learn about notes, tags, and transcripts