> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/live-agent/dashboard.md).
# Dashboard
Comprehensive analytics interface for monitoring performance metrics.
## Feature Overview
* Real-time Statistics: View current agent status and active conversation counts
* Performance Metrics: Track key indicators like response time and resolution rates
* Agent Performance: Individual and team performance visualization
* Time-based Analysis: Filter metrics by different time periods (hour, day, week, month)
* Data Export: Extract reports for further analysis
* Customer Satisfaction: Monitor user ratings and feedback
## Key Metrics
In this first version, the key metrics available are:
* Total Chats
* Active Chats
* Abandoned chats
* Avg. Chat time
* Avg. Response Time
* Avg. Satisfaction Score
If you're a supervisor, you can check the overview or see the details for each Team, such as how many chats were handled, how many are active, the satisfaction score, and average response time.
Use the time filter dropdown to refine your data visualization for this week or this month and get more accurate insights.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs-conversational-ai.syntphony.com/live-agent/dashboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
