# Tickets

<figure><img src="/files/i1pSEsw7Zogd1wEMXtKh" alt=""><figcaption></figcaption></figure>

The Tickets section provides comprehensive details in one place. It includes numerical data on the total tickets, closed tickets, open tickets, pending tickets, and received tickets. This is followed by a tabular list of all received tickets, showing the ticket number, subject, requester name, date of request, and additional details.

The list can be easily filtered using the filter feature or the tabs in the upper row, which indicate different categories.

<figure><img src="/files/wAegm28Ztoa5f2d90xae" alt=""><figcaption></figcaption></figure>

To add a new received ticket to the existing list, fill out the "Create Ticket" form with the following details:

1. **Requester**: Indicate if the ticket is raised by a client or an employee using a checkbox.
2. **Requester Name**: Enter the name of the person raising the ticket.
3. **Ticket Subject**: Briefly state the purpose of the ticket.
4. **Description**: Provide detailed information about the issue or concern, ensuring thorough understanding to prevent miscommunication.
5. **Upload File**: Attach any relevant images, documents, or files provided by the requester for reference.

<figure><img src="/files/SaXrDr6ZBsHk3qWWIEti" alt=""><figcaption></figcaption></figure>

To add a new received ticket to the existing list, fill out the "Create Ticket" form with the following details:

1. **Requester**: Indicate if the ticket is raised by a client or an employee using a checkbox.
2. **Requester Name**: Enter the name of the person raising the ticket.
3. **Ticket Subject**: Briefly state the purpose of the ticket.
4. **Description**: Provide detailed information about the issue or concern to ensure thorough understanding and prevent miscommunication.
5. **Upload File**: Attach any relevant images, documents, or files provided by the requester for reference.
6. **Agent**: Enter the name of the agent who will handle the specific ticket.
7. **Priority**: Set the importance level of the ticket based on the issues it addresses.
8. **Type**: Specify the category of the ticket, such as complaint, question, problem, or incident.
9. **Channel Name**: Indicate the source through which the ticket was received, such as Facebook, email, calls, or texts.
10. **Tags**: Add relevant tags based on the ticket's content.

Once the required details are updated, click the "Save" button to save the data.

<figure><img src="/files/Pb9Un4ht7jQtRoItg2Qn" alt=""><figcaption></figcaption></figure>

The "Create Ticket" form is used to add newly received tickets to the list and can be created or edited using the "Ticket Form" option. This allows for the addition or removal of fields based on organizational requirements. After making selections, a preview form is available to finalize and proceed with the decision.

<figure><img src="/files/WbYFtfro8JAWyX1jKA31" alt=""><figcaption></figcaption></figure>

The tickets section is crucial as it addresses key issues and concerns raised by both employees and clients. Resolving these tickets can lead to significant improvements in the organization.


---

# 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://wheel-erp.gitbook.io/wheel-erp-user-guide/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.