> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/it/servizi-business/zoom-contact-center/zoom-customer-experience/supervisor-experience/zoom-contact-center-reporting-and-real-time-analytics.md).

# Reporting e analisi in tempo reale del centro di contatto Zoom

{% hint style="info" %}
**Nota**

Consulta le [Analisi e Reporting](/technical-library/it/servizi-business/zoom-contact-center/zoom-customer-experience/analytics-and-reporting.md) sezione per ulteriori informazioni.
{% endhint %}

### Nota speciale sui wallboards

I wallboards sono display digitali che forniscono aggiornamenti in tempo reale sulle principali metriche di prestazione del centro di contatto, come il volume di chiamare, i tempi di attesa e la disponibilità degli agenti. I wallboards possono offrire sia ai supervisori sia agli agenti una visione chiara dello stato del centro e delle prestazioni complessive, e sono spesso esposti pubblicamente per un facile monitoraggio da parte dell’intero team.

Dato il Ruolo significativo che i wallboards svolgono nel supportare la consapevolezza operativa, questa sezione è dedicata a mettere in evidenza [i wallboards in tempo reale](/technical-library/it/servizi-business/zoom-contact-center/zoom-customer-experience/analytics-and-reporting/real-time-reports.md#wallboards) come una Funzionalità importante all’interno della sezione Reporting e analisi in tempo reale.

Fare riferimento al Centro assistenza di Zoom per ulteriori informazioni su [personalizzazione dei wallboards](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0059227).

{% hint style="info" %}
**Nota**\
I wallboards richiedono autenticazione per l’Access e l’utilizzo di collegamenti dinamici, con conseguenti cambiamenti periodici dell’URL.
{% endhint %}

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd4_iiO65H63JU9W0wpkdQM58peUOEpjAkZbQLAKHS7N71r6IhK-eYT50KEx5w-kwkseFcJooSOP4dfHuYGnRyAkbj6uuFVVS3FzYWQpSpagpJ4aEvC7hPF2X7PQ7nIyUp2INSo?key=KRgQ_4ail54dHZXUquLpIw" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdDD3l2a8B92k5XSfwY76aMUOnUQOHrhzyu2iMe5zBCCxWtoelrpWZ4pC2PzVkLFqEojTjN796_2OnEbdIy4_GtF1ymovDVjR25N1Kd3XJdxfK2buGEWFV-AZwEr1K8d74wXHw2yA?key=KRgQ_4ail54dHZXUquLpIw" alt=""><figcaption></figcaption></figure>


---

# 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://library.zoom.com/technical-library/it/servizi-business/zoom-contact-center/zoom-customer-experience/supervisor-experience/zoom-contact-center-reporting-and-real-time-analytics.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.