> 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/contact-center/en/the-coaching-area.md).

# The coaching area

This is a new area in the Contact Center with its own navigation item. This area is currently still in beta. Here, you can view the performance of an individual agent per channel. At the moment, admins can see the performance for inbound telephony there with the following scope:

* Top filters: Channel, Agent, Call direction (inbound telephony), Time period (Today, Yesterday, Last 7 days, Last 30 days, Last 12 weeks, Custom)
* KPIs:
  * Availability and utilization (section)
    * Logged-in time (%)
    * Agent activities (%)
    * Logged-in time (hrs.)
    * Availability rate
    * Productive time rate
  * Call volume (section)
    * Answered calls
  * Handling times (section)
    * Avg. handling time (AHT) (min)
    * Avg. after-call work time (min)
    * Avg. talk time (min)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.de/contact-center/en/the-coaching-area.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
