> 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/create-support-panel.md).
# Create Support Panel
### Create support panel (only required fields)
1. Click on the side menu, specifically on the "support panels" option (1), an interface will be displayed where you can see the "create" button (2)\
\
2. A screen will be displayed with the settings to create a new support ticket message.\
\
3. To create this configuration there are three fields that will be required, among them:\
\
\- Identifier\
\- Category\
\- Channel for Message\
\
4. "Identifier" drop-down list:\
Used to help you identify support tickets on the dashboard.\
\
5. "Category" drop-down list:
This is the category on the server that is used when creating a new ticket. All input channels will appear in the category you choose here (3).\
\
Important: You must have previously created your category in Discord (1) (2), E.g:\
\
6. "Channel for Message" drop-down list:\
This channel is designated for hosting the message with the ticket container. By clicking the button linked to this message, users can initiate a ticket creation process.\
\
7. Click on the "save" button and you will automatically see the message in discord\
\
\
\
8. Clicking the "create a support ticket" button will open a new thread for you\
\
### Create support panel (other settings)
#### 1. **Transcript:** Once the toggle is enabled, a summary will be creator to the ticket initiator after the ticket is resolved or the /ticket transcript command is used. For transcriptions you will have two options which are: a) Transcriptions in DM:
* To do this you must go to the betsy dashboard and when you are creating your support ticket click on the toggle "Dm transcribed on close?" and enable it.\
\
It will be displayed as follows (discord):
* Create a ticket\
\
\
\
* If the ticket creator does not write any message then no transcript will be sent, but if the ticket creator writes at least one message then the transcript will be sent to the DM\
\
\
\
* Clicking on the link in the transcript will take you to another page where you can see the information:\
\
b) Public transcripts:
* Once the option is enabled, a public summary will be created in a ticket channel after it is resolved or the /ticket transcribed command is used.\
\
* Create a ticket\
\
\
\
* Write a message on the ticket and close it.\
\
* An embed will be sent to the channel where you can view a link with the transcription\
\
* Clicking on the link in the transcript will take you to another page where you can see the information:\
\
2. **Auto increment number:**\
Once the option is enabled, an increment will be added to the ticket title (discord).\
\
\
\
3. **Hide name:**\
Once the option is enabled, the user's name will not be displayed in the ticket they open\
\
\
\
4. **Allow claiming:** \
Once the option is enabled, when creating a ticket the button to claim will be displayed\
\
\
\
---
# 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/create-support-panel.md?ask=&goal=
```
`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.