> 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/zielwerte-einrichten.md).

# Zielwerte einrichten

Zielwerte für den Servicelevel festlegen, die das Contact Center kontinuierlich mit Echtzeit-Kennzahlen vergleicht.

Zielwerte definieren die Messlatte für den Servicelevel. Das Contact Center vergleicht Echtzeit-Kennzahlen kontinuierlich mit den konfigurierten Zielwerten.

Konfigurierbare Zielwerte:

| Kennzahl                              | Beispielwert                              |
| ------------------------------------- | ----------------------------------------- |
| Erreichbarkeitsquote                  | Mind. 90 % aller Anrufe werden angenommen |
| Anrufe in unter X Sekunden angenommen | Mind. 80 % in unter 20 Sekunden           |
| Team AHT (Ø Bearbeitungszeit)         | Max. 6 Minuten                            |

Vorgehensweise:

1. Unter Contact Center Channels im gewünschten Channel zu den Einstellungen navigieren.
2. Gewünschte Zielwerte eintragen.
3. Speichern.

Die Zielwerte gelten sowohl für das Live Monitoring als auch für die historische Analyse.


---

# 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/contact-center/zielwerte-einrichten.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.
