> For the complete documentation index, see [llms.txt](https://docs.opencityitalia.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencityitalia.it/stanza-del-cittadino/i-servizi-di-help-desk/dashboard-e-reportistica.md).
# Dashboard e reportistica
La piattaforma include una funzione di reportistica ed estrazione dei dati, progettata per fornire all’Ente una visione chiara delle performance dei servizi di segnalazione e richiesta di assistenza.
## Una dashboard di analisi dedicata
Il cuore della reportistica è una [**Dashboard di analisi**](https://docs.google.com/spreadsheets/d/11IKqD3cSSpmr06GrvbzkzgSfmDnFVcl4Xtuc1VeerFI/edit?gid=1657471859#gid=1657471859), che fornisce una data visualization immediata dei principali indicatori (KPI). In particolare, i funzionari possono monitorare metriche come:
* numero di ticket **aperti/chiusi;**
* distribuzione delle richieste per **categoria** o **sotto-categoria;**
## Dati e privacy
Oltre agli strumenti di visualizzazione integrati, la funzione assicura l’accessibilità ai dati aggregati in forma **anonimizzata**, nel rispetto della normativa privacy.
---
# 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.opencityitalia.it/stanza-del-cittadino/i-servizi-di-help-desk/dashboard-e-reportistica.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.
