> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/de/customer-support.md).

# Kundensupport

Erhalten Sie die Kontaktdaten des Devolutions-Kundensupports, einschließlich Telefon-, Chat- und E-Mail-Zeiten, sowie einen Vergleich der kostenpflichtigen Supportpläne.

Telefon- und Chat-Zeiten: Montag bis Freitag, 7:30 bis 18:00 Uhr EDT

Sprachen: English, Français, Deutsch

E-Mail: <service@devolutions.net>

Forum: [https://forum.devolutions.net](https://forum.devolutions.net/)

Telefon: +1 844 463.0419

#### Supportpläne

Abonnenten eines kostenpflichtigen Supportplans erhalten eine E-Mail-Adresse und eine Plan-ID. Sie sollten Ihre Supportanfragen an die entsprechende E-Mail-Adresse senden und Ihre Plan-ID in der Betreffzeile angeben.

Der Umfang des bereitgestellten Supports sowie die Priorität, die den Supportanfragen des Kunden zugewiesen wird, hängen von dem ausgewählten oder gekauften Supportplan und vom Schweregrad des gemeldeten Problems ab.

Die folgende Tabelle zeigt die verschiedenen von Devolutions angebotenen Supportpläne, wobei jeder Plan einen eigenen Umfang an Kundensupport und technischer Unterstützung festlegt:

<table data-search="false"><thead><tr><th width="357"></th><th align="center">Standard-Plan</th><th align="center">Extended-Plan</th><th align="center">Premium-Plan</th></tr></thead><tbody><tr><td><strong>Priorität der Supportstufe</strong></td><td align="center">Normal</td><td align="center">Hoch</td><td align="center">Höchste</td></tr><tr><td><strong>24/7-Zugriff auf unser Community-Forum, unsere Dokumentation und die Devolutions Academy</strong></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td><strong>Support im Online-Community-Forum</strong></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td><strong>E-Mail-Support</strong></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td><strong>Live-Chat-Support</strong></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td><strong>Telefonsupport</strong></td><td align="center"></td><td align="center">X</td><td align="center">X</td></tr><tr><td><strong>24/7-Support im Online-Community-Forum und per E-Mail</strong></td><td align="center"></td><td align="center"></td><td align="center">X</td></tr><tr><td><strong>Dedizierter Customer Success Manager</strong></td><td align="center"></td><td align="center"></td><td align="center">X</td></tr><tr><td><strong>Beratung, Sicherheitsempfehlungen und Schulungen (6 Stunden pro Jahr)</strong></td><td align="center"></td><td align="center"></td><td align="center">X</td></tr></tbody></table>


---

# 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://docs.devolutions.net/resources/de/customer-support.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.