# 2. Basic Ticket Configuration

#### Step 1: Set Up Admin Roles

Assign admin roles so staff can manage tickets: /add admin-role

Who can use this: Server administrators only\
What it does: Grants admin permissions to the selected role

Admin permissions include:

* Managing ticket panels
* Configuring AI settings
* Adding knowledge base documents
* Viewing ticket logs

#### Step 2: Set Up Ping Roles

Configure roles to ping when new tickets are created: /add pingrole

What it does:

* When a user creates a ticket, the bot will ping these roles to notify your support team.
* If the ticket is still unresolved after 2 AI responses, the bot will ping the roles added through the command
* If a query is used with "continue response" added to it, it will ping these roles alongwith the "continue response"

#### Step 3: Deploy Ticket Panel

Create a ticket panel in your support channel (if you don't want to use the channel that the bot automatically created): /add support channel \<channel\_name>

What it does: Creates a ticket panel with an "Open Ticket" button that users can click to create tickets.

#### Step 4: Customize Ticket Panel (If you want to change the information of the support panel)

Edit the ticket panel appearance: /edit

This opens a modal where you can customize:

* Title - Panel title (e.g., "Create a Support Ticket")
* Description - Instructions for users
* Footer - Footer text
* Color - Embed color (hex code)
* Button Label - Text on the "Open Ticket" button
* Button Emoji - Emoji for the button (e.g., 🎫)

#### Step 5: Add Custom Buttons (If you another button on your ticket panel)

Add custom buttons to your ticket panel: /add button

Example buttons:

* FAQ button
* Rules button
* Application button
* Report button

#### Step 6: Customize panel that is inside the ticket

customize the welcome message that appears inside ticket channels when users create tickets: /edit-inside-panel

What Can Be Customized?

The `/edit-inside-panel` command lets you customize:

1. Title - The embed title (supports `{ticket_number}` placeholder)
2. Description - The main message text (supports `{user_mention}` placeholder)
3. Embed Color - The color of the embed (hex code format)
4. Commands Field Name - The name of the field showing ticket commands
5. Commands Field Value - The instructions text for closing tickets


---

# 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://ansari-labs.gitbook.io/ansari-labs/products/ai-powered-ticket-tool/setup-guide/2.-basic-ticket-configuration.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.