Bot Commands
Complete reference for all Ticky bot commands.
Ticket Commands
/close [reason]
Closes the current ticket.
Options:
reason(optional): Reason for closing the ticket
Example:
/close reason: Issue resolved
Permissions: Ticket creator, server admins, or configured admin roles
/reopen
Reopens a closed ticket.
Example:
/reopen
Permissions: Server admins or configured admin roles
/delete
Deletes the current ticket. This action cannot be undone.
Example:
/delete
Permissions: Server admins or configured admin roles
/add <user>
Adds a user to the current ticket.
Options:
user(required): The user to add
Example:
/add @username
Permissions: Ticket creator, server admins, or configured admin roles
/remove <user>
Removes a user from the current ticket.
Options:
user(required): The user to remove
Example:
/remove @username
Permissions: Ticket creator, server admins, or configured admin roles
/claim
Claims the current ticket, restricting access to only you and the ticket creator.
Example:
/claim
Permissions: Server admins or configured admin roles
/rename <name>
Renames the ticket channel.
Options:
name(required): New channel name
Example:
/rename support-ticket-123
Permissions: Ticket creator, server admins, or configured admin roles
/transcript
Generates an HTML transcript of the ticket conversation.
Example:
/transcript
Permissions: Ticket creator, server admins, or configured admin roles
Configuration Commands
/config
Opens the configuration menu for the bot. Most configuration is done through the dashboard.
Example:
/config
Permissions: Server admins only
Utility Commands
/ping
Checks the bot’s latency.
Example:
/ping
Permissions: Everyone
/help
Displays help information and available commands.
Example:
/help
Permissions: Everyone
Command Permissions
Commands respect the following permission hierarchy:
- Server Administrators: Full access to all commands
- Configured Admin Roles: Access based on role configuration
- Ticket Creator: Access to their own tickets
- Everyone: Access to public commands like
/pingand/help
Command Usage Tips
- All commands work in ticket channels
- Some commands require specific permissions
- Use
/helpto see available commands in context - Commands are case-insensitive