> For the complete documentation index, see [llms.txt](https://help.sipgate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.com/documentation/en/statistics-and-analytics/statistiken-and-analysen.md).

# Statistics & analytics

In the area **Analysis** you evaluate the usage and conversation content of your agent. This helps you see where you can adjust content, workflows, or capacity.

### Where can I find the statistics?

You can find the analyses in the logged-in area under **Agents → Analysis.**

#### What is evaluated?

In the analysis, you can see, among other things:

* call volume and conversation duration over different periods
* which days and times calls come in
* which topics and questions arise in the conversations
* how often your agent answers calls itself and how often it forwards them

### Set period and filters

You can filter the statistics by time periods and narrow them down specifically: by individual agents or across all of them, by specific time windows, or by thematic focuses.

<figure><img src="https://1551117702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgAkjs11I2pdU4JZqXDl%2Fuploads%2FielaXUJ1DLZ0UMpvRvVe%2Fanalys1.gif?alt=media&amp;token=a65fb7ff-0d5a-4624-837c-818ffc4534f5" alt=""><figcaption></figcaption></figure>

#### **Call volume**

Here you can see at a glance when and how many calls were received, how long they lasted, and how the conversation time is distributed over the selected period. The breakdown by individual days shows patterns and helps with capacity planning.

<figure><img src="https://1551117702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgAkjs11I2pdU4JZqXDl%2Fuploads%2FcOeB4ACANOGeQ1S02eFJ%2Ffeatures.gif?alt=media&amp;token=47560bfb-a981-4923-a3fc-b2eaa20f8d3f" alt=""><figcaption></figcaption></figure>

#### **Content**

This is about the conversation content: Which topics were discussed, which questions were asked, how often were calls forwarded? This helps you identify thematic priorities and assess how well your agent is performing.

In addition, you can evaluate calls by customer concerns, forwarding destinations, and playbooks. This lets you see which topics are on callers' minds and where there is room for optimization.

<figure><img src="https://1551117702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgAkjs11I2pdU4JZqXDl%2Fuploads%2FPqVkTySZg5Mae7qAfCrL%2Finhalt.gif?alt=media&amp;token=9fef264b-4190-4cee-9c77-79fdb213c161" alt=""><figcaption></figcaption></figure>

<br>


---

# 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.com/documentation/en/statistics-and-analytics/statistiken-and-analysen.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.
