# Public Presets

Public Presets are panel designs curated by the developer. They cover common ticket workflows such as general support, bug reports, staff applications, and partnerships.

Unlike your private [Templates](/docs/panels/templates.md), Public Presets are **available to every server** and are kept up to date by the developer.

<figure><img src="/files/cOM5FGlBevkZQq8x94nT" alt="The Public Panel Presets page with a grid of preset cards, each showing a live panel preview and a Use Preset button"><figcaption></figcaption></figure>

## Browsing the catalog

1. Open the **Templates** page from the sidebar.
2. Click the **Public Presets** button at the top of the page.

This opens the **Public Panel Presets** page, where each preset is shown as a card with a live preview. You can search the catalog by name.

## Using a preset

On the preset card, click **Use Preset**. This starts a new panel pre-filled with the preset's design. The full creation wizard is skipped. You are only asked to pick the channel to send the panel to before you land in the editor.

You can edit anything before saving.

## What presets are not

* **Not a contract.** Every preset is fully customizable after you start a panel from it.
* **Not your support team.** A preset gives you the design only. Your panel still uses your server's support roles, your channels, and your settings.

## Related

{% content-ref url="/pages/R8NFg7M0JfMv91zYkHQI" %}
[Templates](/docs/panels/templates.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://ticketking.xyz/docs/panels/public-presets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.