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

# Ticket commands and permissions

> Prefix command reference with the actual actor checks, action access rules, aliases, and bot permission requirements.

Tickets uses prefix commands. Examples use `.` (the default prefix); replace the dot if your server has configured a different prefix. The `.ticket` group also accepts `.tickets`; Tickets has no slash commands.

## Permissions

Configuration commands require `Manage Channels` from the person running them; Headless's permission layer may also accept a matching Fake Permission. Claiming requires a configured support role or `Manage Channels`.

> [!NOTE]
>
> `.ticket close` and `.ticket transcript`, including their corresponding controls, do not perform an additional staff check. Any member who can access the private channel can use them. Channel overwrites are the effective access boundary. Fake Permissions never grants native Discord permissions to the bot.

Headless needs its own native permissions to create channels, configure channel permissions, read messages, and send files to the log channel.

## Configuration commands

> **Panel, staff, and logs**
>
> These commands enable Tickets and define who manages ticket channels and where records are stored.
>
> * **`.ticket`** — **Aliases:** `.tickets` · **Requirement:** Server · **Behavior:** Shows status; in an active ticket, redisplays its controls.
> * **`.ticket setup #panel [#category]`** — **Aliases:** `set`, `config` · **Requirement:** `Manage Channels` · **Behavior:** Enables Tickets, requests an initial reason, saves destinations, publishes the panel, and displays diagnostics.
> * **`.ticket panel`** — **Aliases:** `send`, `publicar` · **Requirement:** `Manage Channels` · **Behavior:** Publishes or updates the saved panel.
> * **`.ticket role @support`** — **Aliases:** `rol` · **Requirement:** `Manage Channels` · **Behavior:** Adds a support role; up to 25 per server.
> * **`.ticket log #channel`** — **Aliases:** `logs` · **Requirement:** `Manage Channels` · **Behavior:** Sets the explicit destination for logs and transcripts.

> **Panel appearance**
>
> Each command requires `Manage Channels` and updates the saved panel.
>
> * **`.ticket thumbnail URL`** — **Aliases:** `thumb`, `miniatura` · **Behavior:** Sets or clears (`off`) the thumbnail.
> * **`.ticket image URL`** — **Aliases:** `imagen` · **Behavior:** Sets or clears the image.
> * **`.ticket gif URL`** — **Aliases:** `animacion` · **Behavior:** Sets or clears the GIF.
> * **`.ticket button label | HTTPS_URL`** — **Aliases:** `btn`, `link`, `boton` · **Behavior:** Adds or replaces a labeled link; `remove label` removes one and `clear` removes all. Maximum 4 HTTPS links.
> * **`.ticket accent #RRGGBB`** — **Aliases:** `color` · **Behavior:** Changes the panel and control accent color.

> **Messages and closing**
>
> Each command requires `Manage Channels`.
>
> * **`.ticket mention user on|off`** — **Aliases:** `mencionar` · **Behavior:** Toggles requester mentions when a ticket opens. Use `staff` to toggle support-role mentions.
> * **`.ticket open-message text`** — **Aliases:** `mensaje` · **Behavior:** Sets the message or template inside the private channel.
> * **`.ticket close-delay [seconds=10]`** — **Aliases:** `autodelete` · **Behavior:** Schedules deletion after closing, from 0 to 86,400 seconds; defaults to 10 when omitted.

## Actions in a ticket channel

> **Claiming**
>
> A configured support role or a member with `Manage Channels` can claim a ticket. The ticket must be active. Claiming assigns the current handler; there is no separate `.ticket claim` command.
>
> * **Claim from the ticket control** — **Access:** Configured support role or `Manage Channels` · **Result:** Records the current ticket handler.

> **Transcript**
>
> Any member with access to the channel can run the command. Transcripts require the feature to be enabled for the ticket and an explicit log channel; Headless attaches a `.txt` file.
>
> * **`.ticket transcript`** — **Access:** Member with channel access · **Result:** Generates a transcript and sends it to the configured log channel.

> **Closing**
>
> Any member with channel access can close a ticket. Headless retains the record and schedules channel deletion. Transcript and close-DM delivery are best-effort.
>
> * **`.ticket close [reason]`** — **Access:** Member with channel access · **Result:** Closes the ticket and records the supplied reason or the default text.

There is no command to open a ticket outside the panel. Headless also has no blacklist, manual allow/deny, extra participants, reopen, move, or ticket-statistics commands.

## Syntax and example

#### `.ticket setup`

```headless-command Syntax theme={null}
.ticket setup <panel_channel> [category]
```

```headless-command Example theme={null}
.ticket setup #help #tickets
```

#### `.ticket role`

```headless-command Syntax theme={null}
.ticket role <role>
```

```headless-command Example theme={null}
.ticket role @Support
```

#### `.ticket log`

```headless-command Syntax theme={null}
.ticket log <channel>
```

```headless-command Example theme={null}
.ticket log #ticket-records
```

#### `.ticket button`

```headless-command Syntax theme={null}
.ticket button [definition]
```

```headless-command Example theme={null}
.ticket button Rules | https://example.com/rules
```

#### `.ticket close-delay`

```headless-command Syntax theme={null}
.ticket close-delay [seconds=10]
```

```headless-command Example theme={null}
.ticket close-delay 3600
```

> [!WARNING]
>
> Use `0` only when you intend to request immediate deletion of the channel after closing the ticket.

#### `.ticket transcript`

```headless-command Syntax theme={null}
.ticket transcript
```

```headless-command Example theme={null}
.ticket transcript
```

#### `.ticket close`

```headless-command Syntax theme={null}
.ticket close [reason]
```

```headless-command Example theme={null}
.ticket close Resolved
```

> [!WARNING]
>
> A transcript may contain messages, identifiers, and attachment links from the private channel. Restrict the log channel; command access does not replace ticket-channel overwrites.

## Related pages

* [Tickets overview](/docs/en/server/tickets/overview.md)
* [Panels](/docs/en/server/tickets/panels.md)
* [Access and privacy](/docs/en/server/tickets/access.md)
* [Lifecycle](/docs/en/server/tickets/lifecycle.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.