> ## Documentation Index
> Fetch the complete documentation index at: https://fyre.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Tickets

> Learn about Fyre's ticket module commands and how to customise ticket categories.

export const scope_0 = "Ticket transcripts"

<Warning>
  **{scope_0}** require the [Message Content intent](https://docs.discord.com/developers/events/gateway#message-content-intent) to function.
  Without [privileged intent proxying](/docs/guides/proxy) enabled, {scope_0} will be disabled.
</Warning>

## Create, Updating, and Deleting

To learn about creating, updating, or deleting ticket categories,
visit [Managing Ticket Categories](/modules/tickets/managing).

## Staff Commands

Below is a list of Fyre's staff commands for tickets. All of these commands are text and slash commands.

<Info>In brackets is the default usability of the command. This can be changed on a per category basis.</Info>

* `/add` - Add a member to the current ticket (ticket owner or staff).

* `/remove` - Remove a member from the current ticket (ticket owner or staff).

* `/claim` - Claim a ticket as your own (ticket staff).

* `/release` - Release (un-claim) the ticket and allow other staff to claim it (ticket staff).

* `/move` - Move the ticket to a different ticket category (ticket staff).

* `/transfer` - Transfer the ticket to a different owner (ticket owner or staff).

* `/ticket-vc` - Create a temporary private VC for ticket members (ticket staff).

## Category Roles (Ping, Staff, Required)

With Fyre you can have up to 10 roles in each related field per category.
To manage category roles, use `/categories roles add` and `/categories roles remove`.

Ping roles are the roles that Fyre will ping when a ticket is opened, or when a ticket close request is made.

Staff roles are the roles that will be able to see all newly-created tickets, and manage them.

Required roles are roles that a member must have before opening a ticket in a specific category.
With Fyre, a member must only have **one** of the required roles to open a ticket in a locked category.

## Greeting Message

You can customise Fyre's ticket greeting message quite extensively.
To update a category's greeting message, use `/categories greeting`.

<img src="https://mintcdn.com/fyre/5Do-Ft2cBSBPPoFk/public/screenshots/tickets/greeting-message.png?fit=max&auto=format&n=5Do-Ft2cBSBPPoFk&q=85&s=dbcbbf105169eb9a8ff9ca14a88e8d89" alt="Ticket Greeting Message Example" width="1030" height="294" data-path="public/screenshots/tickets/greeting-message.png" />

After using this command, a modal will popup allowing you to enter a custom template for the greeting.
This template supports most of Fyre's [variables](/templating/variables).

<img src="https://mintcdn.com/fyre/5Do-Ft2cBSBPPoFk/public/screenshots/tickets/admin-greeting-message-modal.png?fit=max&auto=format&n=5Do-Ft2cBSBPPoFk&q=85&s=79fa9779dec1f85df92a2bb8a391aaba" alt="Admin Ticket Greeting Modal Example" width="960" height="926" data-path="public/screenshots/tickets/admin-greeting-message-modal.png" />

## Confirmation Prompt

All ticket categories have an optional confirmation prompt that is disabled by default.
You can use this prompt to make sure users have required evidence, are ready to open a ticket, etc.

Users will be shown this confirmation prompt whenever they attempt
to open a ticket via a ticket panel or the `/open` command.

<img src="https://mintcdn.com/fyre/5Do-Ft2cBSBPPoFk/public/screenshots/tickets/confirmation-prompt.png?fit=max&auto=format&n=5Do-Ft2cBSBPPoFk&q=85&s=0bb736f98d6a0a02ed6e0c51d0b216f2" alt="Ticket Confirmation Prompt Example" width="1040" height="346" data-path="public/screenshots/tickets/confirmation-prompt.png" />

You can customize this confirmation prompt to say whatever you prefer easily using `/categories confirmation`.
This command support the following options:

* `category` - The category ID to update (autocomplete).
* `enabled` - Whether the confirmation prompt is enabled for this form (Yes or No).
* `delay` - The delay in seconds a user must wait before starting the form (default: none, min: 5, max: 30).
* `mode` - The mode for displaying the confirmation prompt (Plain or Container, default: Plain).

After using this command, a modal will popup allowing you to enter content for the confirmation prompt.
Confirmation prompts support [guild template variables](/templating/variables#guild%2Fserver-variables).

<img src="https://mintcdn.com/fyre/5Do-Ft2cBSBPPoFk/public/screenshots/tickets/admin-confirmation-prompt-modal.png?fit=max&auto=format&n=5Do-Ft2cBSBPPoFk&q=85&s=5811d0023f94c0537dba98b44321d965" alt="Ticket Admin Confirmation Prompt Modal Example" width="964" height="756" data-path="public/screenshots/tickets/admin-confirmation-prompt-modal.png" />

## Creating Ticket Panels

Ticket panels allow your users to easily open tickets without using `/open`.
These panels can have buttons or a select menu for members to easily start form submissions.

To create a ticket panel, use `/ticket-panel`. This command supports the following options:

* `type` - The type of panel to create (Buttons or Select Menu).
* `channel` - The channel to send the panel in (text channels only).
* `message-template` - A pre-existing message template to use as the ticket panel (autocomplete).
* `button-name` - The name of the button if you're making a one button panel.
* `select-menu-placeholder` - The placeholder text in the select menu if you're making a select menu panel.

After using this command, a modal will popup allowing you to enter a template for the ticket panel.
Ticket panels support [guild template variables](/templating/variables#guild%2Fserver-variables).
You can select up to 5 ticket categories per panel in the select menu.
Each category will get it's own button or select menu option.

<img src="https://mintcdn.com/fyre/5Do-Ft2cBSBPPoFk/public/screenshots/tickets/admin-panel-template-modal.png?fit=max&auto=format&n=5Do-Ft2cBSBPPoFk&q=85&s=eff4b6c05cfa20df200ada0a943582ca" alt="Ticket Admin Create Panel Template Example" width="483" height="718" data-path="public/screenshots/tickets/admin-panel-template-modal.png" />
