> 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/account-management/gruppen-und-user/welche-anrufstatistiken-stehen-fuer-gruppen-zur-verfuegung.md).

# What call statistics are available for groups?

Overview of sipgate group statistics - availability rate, waiting times, call duration, and CSV export for admins.

{% hint style="info" %}
The function *Groups* is **is available only to customers on sipgate classic** available. On sipgate neo, it is integrated in a different form.
{% endhint %}

With the group call statistics, admins get the most important key figures about your incoming telephony in real time. This gives you the option on the group detail page to evaluate various key figures for incoming calls to your groups individually for each month.

With an **enabled queue** admins can also use the call statistics to capture the current number of people waiting as well as the average wait time in the queue over the last 30 days. All recorded data can also be filtered by month, retroactively for up to one year.

For a better overview, reachability is additionally displayed visually as a **graph** . This allows you to evaluate reachability on individual days. In addition, the data can also be downloaded in CSV format, with an hourly breakdown provided. This makes it possible, for example, to record times of increased call volume in order to plan employees' working hours accordingly. The function can be activated as a **free** option in the logged-in area via the tile **Contracts and products** for one or more groups.

{% hint style="warning" %}
Important: If a group is deleted, the call statistics for this group are automatically deleted as well.
{% endhint %}

Explanations of the key figures:

* **Incoming calls**: Number of calls that came in on the group number during the selected period.
* **Answered calls**: Number of calls answered by group members during the selected period. If the queue is enabled, this also includes the number of calls that were answered after waiting in the queue.
* **Missed calls**: Number of calls that were not answered. This also includes forwarded calls, both to other phone numbers and to voicemail. If the queue is enabled, this also includes calls where callers hung up while waiting.

{% hint style="info" %}
In the call statistics, forwarded calls are counted as follows: If the forwarded call is answered, it is considered "**answered**" in the event list and the group statistics. If it is not answered, it is considered "**missed**" -- both in the event list and in the group statistics.
{% endhint %}

* **Reachability rate**: Ratio of successfully answered calls to the total number of incoming calls.
* **Voicemail messages**: Number of messages callers left on voicemail, if this is enabled as a forwarding option.
* **Average call duration**: Average duration of calls (including forwarded calls that were answered) during the selected period.


---

# 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/account-management/gruppen-und-user/welche-anrufstatistiken-stehen-fuer-gruppen-zur-verfuegung.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.