> ## 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 options

> Per-server Ticket defaults, supported limits, Dashboard controls, and the options that Headless does not implement.

Ticket settings are stored per server. Most values are changed in the authenticated Dashboard; the deletion delay also has a prefix command. Setup is the main exception to defaults: it enables Tickets and sets require\_reason to true.

## Defaults and bounds

> **Reference details**
>
> * **enabled** — **Initial value:** Off until setup · **Effective bound or behavior:** .ticket setup enables the feature.
> * **max\_open\_per\_user** — **Initial value:** 2 · **Effective bound or behavior:** 1–10 concurrent tickets per member.
> * **require\_reason** — **Initial value:** False before setup; enabled by setup · **Effective bound or behavior:** The Dashboard may turn the reason modal requirement off.
> * **transcript\_enabled** — **Initial value:** On · **Effective bound or behavior:** Off prevents on-demand and close-time transcript generation.
> * **transcript\_limit** — **Initial value:** 500 messages · **Effective bound or behavior:** 25–5,000 recent messages in a transcript.
> * **close\_delete\_seconds** — **Initial value:** 10 seconds · **Effective bound or behavior:** 0–86,400 seconds; 0 requests immediate channel deletion after close.
> * **dm\_user\_on\_close** — **Initial value:** On · **Effective bound or behavior:** Optional closing DM; delivery is best-effort.
> * **mention\_user, mention\_staff** — **Initial value:** Both on · **Effective bound or behavior:** Separate controls for requester and support-role mentions.
> * **Support roles** — **Initial value:** None · **Effective bound or behavior:** Up to 25 per server.
> * **Additional panel links** — **Initial value:** None · **Effective bound or behavior:** Up to four HTTPS links.

> [!NOTE]
>
> The current Dashboard number control advertises 50–10,000 for `transcript_limit`, but the runtime normalizes the effective value to 25–5,000. Use the effective range; saving an out-of-range number does not enlarge the transcript.

## Change and verify settings

Use the Dashboard's Tickets settings to change the per-server limits, modal requirement, transcript controls, DM and mention behavior, panel text, labels, media, and accent color. `.ticket close-delay [seconds=10]` sets the closed-channel deletion delay. `.ticket log #channel` is a separate required destination for transcript delivery; a panel channel is not used as a fallback.

**1. Set capacity**

Choose max\_open\_per\_user between 1 and 10 based on your team's workload.

**2. Choose modal behavior**

Keep require\_reason enabled for structured intake, or disable it if opening should skip the fixed modal.

**3. Protect transcript data**

Enable transcripts only if you have a restricted log channel, set a reasonable history limit, and test access to the resulting file.

**4. Choose close behavior**

Set the delay with `.ticket close-delay [seconds=10]` and verify that deletion timing suits your retention needs.

## Transcript delivery

`.ticket transcript` creates a text file with up to `transcript_limit` recent messages. Tickets and transcripts must be enabled, and a valid log channel must be configured. On close, Headless attempts to create and send the file before finishing; the ticket record remains closed if generation, the log channel, or delivery fails.

### Configure the log destination

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

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

### Request a transcript

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

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

## Set the deletion delay

The default delay is 10 seconds; the accepted range is 0–86,400 seconds. `0` requests immediate deletion of the closed channel. The ticket record remains in per-server storage after the Discord channel is deleted.

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

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

> [!WARNING]
>
> A zero-second delay requests immediate deletion. The stored ticket record does not preserve the deleted Discord channel or its messages.

## Unsupported reference options

Headless does not implement inactivity reminders, inactivity auto-close, automatic deletion on a separate timer, per-option settings, overflow categories, multiple panels, or reusable form limits. Do not configure these as if they were hidden Dashboard toggles.

## Related pages

* [Ticket forms](/docs/en/server/tickets/forms.md)
* [Ticket lifecycle](/docs/en/server/tickets/lifecycle.md)
* [Ticket messages](/docs/en/server/tickets/messages.md)


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