> For the complete documentation index, see [llms.txt](https://reference-guide.gitbook.io/crm-back-office-user-guide-full/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reference-guide.gitbook.io/crm-back-office-user-guide-full/crm-back-office-user-guide-full-cn/16.-tickets/ticket-management/view-tickets.md).

# View Tickets

Brokers will be able to do the following: 

<details>

<summary>View Ticket Details</summary>

To access the detailed information of a ticket, simply click on it.&#x20;

You will have visibility into the following components:

1. Ticket Content: This includes the content submitted by the client as well as any responses provided by you or your team.
2. Handler: This indicates the specific person assigned and responsible for handling the ticket.&#x20;
3. Ticket Status: The status of the ticket will be indicated. The available ticket statuses are as follows:
   * Pending: The ticket is awaiting resolution.
   * Reopen: The ticket has been reopened, which may occur if the issue resurfaces or if the previous resolution was unsatisfactory.
   * Processing: The ticket is currently being processed, indicating that the team is actively working towards resolving the issue or fulfilling the client's request.
   * Resolved: The issue reported in the ticket has been resolved, and it is pending verification from the client.
   * Closed: The ticket has been resolved and verified by the client, indicating that the issue has been successfully addressed and closed.
4. Owner: This refers to the salesperson or team member responsible for managing the client associated with the ticket.
5. Log: The activity log for the ticket provides a record of all actions, updates, and changes related to the ticket.<br>

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

</details>

<details>

<summary>Search Bar</summary>

You have the ability to search for a specific ticket via the search bar via the following:&#x20;

1. Client Name
2. Ticket ID&#x20;
3. Subject <br>

   <figure><img src="/files/1fqJEZC98b3SOykJJ8jt" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>Date Range</summary>

1. This allows brokers to filter tickets based on a specific time frame.&#x20;
2. Brokers can filter the date range by the following methods:&#x20;
   1. Manually select the time frame.&#x20;

      <figure><img src="/files/Stc78dr1Di0tUQF6F9cQ" alt=""><figcaption></figcaption></figure>
   2. Select the timeframe based on the pre-set periods.<br>

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

</details>

<details>

<summary>Filter</summary>

You can also filter tickets via the following options:&#x20;

1. Ticket Status
2. Reply Status<br>

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

</details>


---

# 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://reference-guide.gitbook.io/crm-back-office-user-guide-full/crm-back-office-user-guide-full-cn/16.-tickets/ticket-management/view-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.