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] [role]

Adds a user or role to the current ticket.

Options:

  • user (optional): The user to add
  • role (optional): The role to add

Example:

/add user: @username
/add role: @Support Team

Select either user or role, not both. Adding a role gives everyone with that role access to the ticket channel.

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

Transcripts are stored on the website and can be viewed from the dashboard. When a ticket is closed, Ticky automatically generates a transcript and DMs the website transcript link to the ticket creator when possible.


AI stop by mention

This is not a slash command. In a ticket channel, mention the bot and say stop to disable AI replies in that channel.

Example:

@Ticky stop

After this, the AI assistant will stop responding in that ticket channel until the AI configuration is changed by staff.


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:

  1. Server Administrators: Full access to all commands
  2. Configured Admin Roles: Access based on role configuration
  3. Ticket Creator: Access to their own tickets
  4. Everyone: Access to public commands like /ping and /help

Command Usage Tips

  • All commands work in ticket channels
  • Some commands require specific permissions
  • Use /help to see available commands in context
  • Commands are case-insensitive
  • Use /add role: when an entire support team needs access to one ticket
  • Use /transcript or close the ticket to create a website-hosted transcript

Need Help?