> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/sipgate-ai-agents/welche-statistiken-kann-ich-fuer-sipgate-ai-agents-auswerten.md).

# Which statistics can I evaluate for sipgate sona?

View statistics and analyses for sipgate sona – call volume, call duration, and success rates.

This article explains how to use analytics in the logged-in area of sipgate sona. You will learn how to retrieve key figures for a period in the dashboard and analyze individual data for specific calls. Relevance: This helps you see the number of incoming calls, duration of use, and topics of your calls and can specifically evaluate the front desk setup.

If you use sipgate sona, you can **as admin** in the logged-in area under **Products** ➔ **Analytics** apply several statistics to evaluate the usage of your sipgate AI Agent. This gives you an overview of incoming calls and the usage duration of your sipgate AI Agent.

In **call volume** you can see for the selected period:

* the answered calls per day
* the forwarded calls per day
* the forwarding rate
* the total talk time per day
* the average talk time per day

In the **call data** you can view each call in detail and thus have the opportunity to analyze the topics of the respective calls here:

If you have created different playbooks for your AI agents, you can under **Content** see the statistical distribution of the playbooks used as well as a ranking of the most frequently used playbooks.

Admins can also view the transcriptions of individual calls in order to evaluate further details of the respective conversations.


---

# 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://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/sipgate-ai-agents/welche-statistiken-kann-ich-fuer-sipgate-ai-agents-auswerten.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.
