> For the complete documentation index, see [llms.txt](https://docs.betsybot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betsybot.xyz/features/support-panels-tickets/custom-implementations.md).

# Custom Implementations

### Open Tickets with Menu Components

{% embed url="<https://t.gyazo.com/teams/chicksgold/9bb93f9fc1c5617bb71f7fbca6c6b48c.mp4>" %}
How it looks when creating a ticket with a menu select
{% endembed %}

#### How to Configure

{% hint style="info" %}
You MUST have more than 1 support panel created and configured before you can use this feature. The way this works is you are opening up different panels, which are your different types. This gives you full control over what happens when each of these types are opened
{% endhint %}

{% hint style="info" %}
You must have a support ticket panel for each change in "functionality" you want with the different "types" of message you want to open. For example if you want to open a ticket the same exact way but have a different starting message you need to clone your support panel and change the Initial Message. This gives you FULL control over the differences in which "type" of ticket you are opening.
{% endhint %}

For this example we will use the Tracked Message Feature to house the message with the Menu Select.

First and foremost you must have the Custom Id for the menu select be "MenuCreateTicket". This will tell Betsy's API to create a ticket when something with this menu select happens.

For the options the "Item Value" for the option MUST match the Identifier of the the Support Ticket Panel you would like to open.

<figure><img src="https://t.gyazo.com/teams/chicksgold/058e97adbff6dd9ff0e4e41627a7885a.png" alt=""><figcaption><p>Showing the options matching the Identify of the Support Ticket Container</p></figcaption></figure>

<figure><img src="https://t.gyazo.com/teams/chicksgold/2d7f099d4aa8e5ca7fe197fa611356a8.png" alt=""><figcaption><p>Showing the matching identifiers for the support ticket container</p></figcaption></figure>

### Open Tickets with Button Components

#### How to Configure

For this example we will use the Tracked Message Feature to house the message with the Buttons.

The way that you can use buttons is by utilizing the Custom ID Action "ButtonCreateTicket". Because buttons don't come from a single source, unlike menus, you will need to use the ":" delimiter in the custom ID and append the identifier to the Button's Custom ID. For example if you have a ticket container with the identifier of "test" your custom ID for the button would look like "ButtonCreateTicket:test"

<figure><img src="https://i.gyazo.com/64a7b99e1d75d884a23e942c6f9b85d6.png" alt=""><figcaption><p>The components section for a Tracked Message used to create tickets through buttons</p></figcaption></figure>

You do not need to have the ticket container active in order to create a ticket through this method.


---

# 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://docs.betsybot.xyz/features/support-panels-tickets/custom-implementations.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.