> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/reporting-and-analytics/dashboards.md).

# Read your dashboards

Read the Request, AI and SLA dashboards in Siit: weekly request volume, satisfaction, channel filters, AI efficiency, and First Response and Time to Resolve achievement rates

Requests metrics allow you to monitor your employee support performance.

### Request Dashboard:

We’ve improved the existing dashboard to display weekly request metrics, providing insights to analyze the volume of requests you’ve been managing. It also includes reports on the satisfaction of employee support. And we have added new Filters: You can now filter data by “Submitted from” and “Channel” for more granular insights.

### AI Dashboard:

This new dashboard allows you to monitor the efficiency of the AI model, along with insights to continuously improve it by feeding the right content.

### SLA Dashboard:

This dashboard focuses on the SLA feature, and will help you keep track of team performance. For the two targets, “First Time Response” and “Time to Resolve,” you will be able to evaluate your achievement rate.\
​

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-0ebfc31a48fff961a85ab96057d2a57baabbf10f%2FNew-Analytics-1-.gif?alt=media" alt=""><figcaption></figcaption></figure>

**Available filters :** Date, Priority, Requested by, Channel, Assigned to Inbox Assigned to, Associated to, Tags, Requester Location, Requester Department, Requester Team

### Evolution of requests

* **Repartition by status** Repartition of requests per status (”New”, “In progress”, “Waiting”, “Resolved”).
* **Requests over time** Evolution of new and resolved requests during the last 12 months.

### Performance and SLA

* **Avg. Solving time** (days) Average of total requests solving time *(time when status is “Resolved” - time of creation)*.
* **Avg. Solving time over time** (days) Evolution of average solving time during the last 12 months.
* **Completed requests per admin** List of Siit admins with their total of solved requests and their average solving time.
* **Distribution by Day of the week** Repartition of requests per day of the week (based on “creation date”).
* **Distribution by Hour of the day**
* Repartition of requests per hour of the day (based on “creation time”).

**Avg. Solving time** (days) Average of total requests solving time *(time when status is “Resolved” - time of creation)*.

**Avg. Solving time over time** (days) Evolution of average solving time during the last 12 months.

**Completed requests per admin** List of Siit admins with their total of solved requests and their average solving time.

**Distribution by Day of the week** Repartition of requests per day of the week (based on “creation date”).

**Distribution by Hour of the day**

Repartition of requests per hour of the day (based on “creation time”).

### Associated applications / services

* **Top associated applications / services** Repartition of requests per application / service (including a repartition per status).
* **Details** \[List] List of applications / services associated to the requests (”name”, “type”, “requests number”, “avg. solving time (h)”, “last request date”).


---

# 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.siit.io/guides/reporting-and-analytics/dashboards.md?ask=<question>&goal=<user_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.