> For the complete documentation index, see [llms.txt](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/6.-reports/6.2-real-time-monitoring/6.2.2-chat-monitoring.md).

# 6.2.2 Chat monitoring

## Chat monitoring interface

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

### (1) Information filter

* **Queue:** filter real-time chats by queue name. The user can either unselect a queue (to see all) or select multiple queues (to view chats in that queue).

### (2) Real-time chat fields

* **ID:** chat code on StringeeX&#x20;
* **Customer:** customer name entered at the beginning of the conversation (for Zalo, customers who have not clicked interest will display Zalo's Visitor ID)&#x20;
* **Email:** the email entered by the customer at the start of the conversation&#x20;
* **Queue:** conversation reception queue&#x20;
* **Status:** the status of the chat, including ringing (pending to the agent but the agent has not received) and answering (the agent is chatting with the customer)&#x20;
* **Status duration:** duration in the current status of the chat&#x20;
* **Agent:** the agent is chatting with the customer or the agent to which the system is pouring the conversation&#x20;
* **Start time:** chat start time&#x20;
* **Action:** management interventions. *Note: supervisor/admin can only perform interventions on a chat that has been received by the agent (the status is answering).*&#x20;
  * **View:** watch live chat&#x20;
  * **Join:** join the conversation&#x20;
  * **Transfer:** move the conversation from the current agent to another agent&#x20;
  * **End:** end the conversation


---

# 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://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/6.-reports/6.2-real-time-monitoring/6.2.2-chat-monitoring.md?ask=<question>&goal=<endgoal>
```

`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.