> For the complete documentation index, see [llms.txt](https://mythicalbot.gitbook.io/arklynn-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mythicalbot.gitbook.io/arklynn-docs/miscellaneous/tickets.md).

# Tickets

### 1. Initial Configuration

After the bot joins, you need to set up the core ticketing system.\
Use the slash command:

text

```
/setup_ticket
```

This opens an interactive configuration with three dropdown menus.

### 2. Core Configuration (`/setup_ticket`)

***

The `/setup_ticket` command defines the basic infrastructure:

* **Ticket Category** – where new ticket channels are created.
* **Support Roles** – who can access all tickets.
* **Transcript Channel** – where closed ticket logs are sent.

#### How to use `/setup_ticket`

1. Type `/setup_ticket` in any channel.
2. Arklynn replies with a message containing three dropdowns.
3. Click each dropdown and select:
   * **Ticket Category** – choose an existing channel category.
   * **Support Roles** – select one or more roles (staff, admin, etc.).
   * **Transcript Channel** – pick a text channel (keep it private to staff).

The configuration is saved immediately. You can run `/setup_ticket` again anytime to change it.

#### View Current Settings

To see your current configuration, use:

text

```
/ticket_config
```

or click the **⬇ Show Current Config** button in the `/setup_ticket` response.\
You'll see the category, support roles (with member counts), and transcript channel.

### 3. Creating the Ticket Panel (`/setup_panal`)

***

The ticket panel is the message users see with a big button to open a ticket.\
Use the slash command:

text

```
/setup_panal
```

This opens the **Advanced Panel Configuration** with a live preview.

#### Panel Customization Options

| Section                  | What You Can Set                                                 |
| ------------------------ | ---------------------------------------------------------------- |
| **Channel Selection**    | Where the panel will be sent.                                    |
| **Title & Emoji**        | Panel title (e.g., "Support Ticket") and optional emoji.         |
| **Description**          | Explanatory text (e.g., "Click below to create a ticket.").      |
| **Colors**               | Embed color and button color (Blurple, Green, Red, Grey).        |
| **Button Customization** | Button text, emoji, and color.                                   |
| **Display Options**      | Show/hide system info (support roles, category) below the panel. |

As you change settings, the **Preview Panel** updates in real time.

#### Publish the Panel

When you're happy, click **Create Panel**. The bot sends the panel to your chosen channel.\
Users can now open tickets by clicking the button.

### 4. Inside a Ticket – The Button Interface

***

When a user clicks the **Open Ticket** button, Arklynn creates a private channel (e.g., `ticket-username`) in your configured category.\
The ticket contains a special message with several **buttons** – no commands needed.

#### Ticket Header Message

The header shows:

* Ticket number (e.g., `Ticket #2 from @Anaseueid`)
* Creation time
* Status: `> Waiting for support`
* Staff assignment: `> None` (if not claimed)
* A note: "Please wait while our team responds."

#### Available Buttons

| Button             | Description                                                       |
| ------------------ | ----------------------------------------------------------------- |
| **Claim Ticket**   | Assign the ticket to yourself. Other staff see you've claimed it. |
| **Close Ticket**   | Close the ticket and save a transcript.                           |
| **Add User**       | Add another user (by mention or ID) to the ticket.                |
| **Remove User**    | Remove a user from the ticket.                                    |
| **Transfer Claim** | Pass the claim to another support member.                         |
| **Rename Ticket**  | Change the ticket channel's name (useful for custom reference).   |

All buttons work immediately – just click them.

* **Claiming** shows who is handling the ticket.
* **Adding/Removing users** lets you bring in extra people (e.g., a second support agent).
* **Closing** triggers a transcript and archives/deletes the channel.

#### For Users

The ticket opener can only see and use the channel; they do **not** see the management buttons (only support roles do).\
They can type freely, upload files, etc.

### 5. Closing Tickets & Transcripts

***

#### How to Close

Any support member can click **Close Ticket**. Arklynn will:

* Save the entire message history as a `.html` file.
* Send that file to the **transcript channel and user DM**'**s**.
* Delete the ticket channel (or archive it, depending on settings).

#### Viewing Transcripts

Go to your transcript channel. Each closed ticket appears as a message with an attached transcript file, including:

* Ticket number and creator
* Opening and closing time
* All messages in order

###

### 6. Permissions & Administration

***

* **Who can use `/setup_ticket` and `/setup_panal`?**

{% hint style="warning" %}
Only members with the `Administrator` permission (or a configured admin role, if supported).
{% endhint %}

* **Who sees tickets?**
  * The ticket creator always has access.
  * All members with any **support role** (set in `/setup_ticket`) have access to **all** tickets.
  * Regular members cannot see ticket channels.
* **Who sees the management buttons?**\
  Only support roles. The ticket opener only sees the chat area.

### 7. Frequently Asked Questions

***

<details>

<summary><strong>The panel button doesn't create a ticket.</strong></summary>

Check if the bot has `Manage Channels` in the server and in the selected category. Also ensure the category isn't full.

</details>

<details>

<summary><strong>How do I add more support roles later?</strong></summary>

Run `/setup_ticket` again and select the additional roles. Future tickets will include them.

</details>

<details>

<summary><strong>Can I edit an already posted panel?</strong></summary>

Run `/setup_panal` and create a new panel in the same channel, or delete the old one manually. Some versions support editing via a button on the panel itself.

</details>

<details>

<summary><strong>What happens if I delete a ticket channel manually?</strong></summary>

No transcript is saved. Always use the **Close Ticket** button.

</details>

<details>

<summary><strong>Can users open multiple tickets at once?</strong></summary>

No, by default.

</details>

<details>

<summary><strong>The transcript channel receives nothing.</strong></summary>

Verify the bot can send messages and attach files there. Also check that the transcript channel is correctly selected in `/setup_ticket`.

</details>

###

### 8. Command Summary (Slash Commands)

***

| Command         | Description                                            |
| --------------- | ------------------------------------------------------ |
| `/setup_ticket` | Configure category, support roles, transcript channel. |
| `/setup_panal`  | Create or customize a ticket panel.                    |

{% hint style="info" %}
All other actions are done via buttons inside tickets.
{% endhint %}


---

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

```
GET https://mythicalbot.gitbook.io/arklynn-docs/miscellaneous/tickets.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.