> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/settings/messages.md).

# Ticket messages

There is no server-wide "messages" group on the Settings page. The text shown when a ticket opens is set per panel option in the panel editor. The only message text on the Settings page is the **Default Ticket Close Reason**.

## Per-option messages (panel editor)

Open a panel in the dashboard, click a button or select-menu option, and go to the **Messages** tab. Both fields here are free.

| Field                                                              | What it does                                                                        | Limit           |
| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | --------------- |
| **Custom Embed Content**                                           | The embed shown inside the ticket when it opens.                                    | 2048 characters |
| **Custom Ticket Message**                                          | A message sent into the ticket when it opens.                                       | 1024 characters |
| **Admin Thread Message** (<i class="fa-crown">:crown:</i> Premium) | A message posted in the staff thread. The custom text only takes effect on premium. | 1024 characters |

A panel can also set defaults that every option inherits (for example **Default Ticket Embed Message** and **Default Ticket Message Content**) in the panel-wide defaults editor.

→ [Per-option settings in the panel editor](/docs/panels/per-option-settings.md)

<figure><img src="/files/qoHoj7ERgNKB2YhU9nO6" alt="The Messages tab of a panel option"><figcaption></figcaption></figure>

## Default Ticket Close Reason (Settings)

In the **Ticket Close & Transcript Settings** group, **Default Ticket Close Reason** sets the reason that is recorded when a ticket is closed without one being given. When it is blank, Ticket King uses its own built-in default reason.

## Related

{% content-ref url="/pages/9dB72vzFglsTzKnh6Q2Z" %}
[Closing a ticket](/docs/tickets/closing-a-ticket.md)
{% endcontent-ref %}

{% content-ref url="/pages/bMLvaN6SRnkJa0CP1UBr" %}
[Settings overview](/docs/settings/overview.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ticketking.xyz/docs/settings/messages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.