> 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/channels/wie-kann-ich-meine-statistiken-fuer-channels-exportieren.md).

# How can I export my statistics for Channels?

This is how you export Channel statistics in sipgate as CSV - call analysis of the last 60 days including waiting times and call status.

As **an admin** you can analyze the availability of all channels created in the last 60 days separately using statistics. An automatic report is generated for this purpose, recording all **incoming calls** To download the current statistics, go to the relevant channel routing and click **Data export**. For newer contracts, simply use the download button. You will then receive the requested file in CSV format.

![](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-db97291ae31bf653e02885d4bbb63cfa2df1abd4%2Fmceclip0.png?alt=media\&token=522781c5-6689-4396-857f-1d34f4a39af0)

To export data, you first need admin permissions.\
The export contains the following information:

**Channel name, called number, caller number, call status, date + time, waiting time, duration of answered call, after-call work, reason for missed call**

The following data can be analyzed using the statistics:

* Which phone number called, and when?
* How many calls were answered?
* How many calls were missed? When were calls missed?
* How many calls were forwarded?
* How many calls exceeded the maximum waiting time?
* During which periods was call volume highest?
* If agent statistics are enabled: who answered how many calls?


---

# 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/channels/wie-kann-ich-meine-statistiken-fuer-channels-exportieren.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.
