> 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/customer-support.md). # Customer support Get Devolutions customer support contact details, including phone, chat, and email hours, plus a comparison of paid support plans. Phone and chat hours: Monday to Friday 7:30 a.m. to 6:00 p.m. EDT Languages: English, Français, Deutsch Email: Forum: [https://forum.devolutions.net](https://forum.devolutions.net/) Phone: +1 844 463.0419 #### Support plans Subscribers of a paid support plan receive an email address and a plan ID. You should send your support requests to the appropriate email address and provide your plan ID in the subject line. The level of support provided, as well as the priority assigned to customer's support requests, will depend on the specific support plan selected or purchased, and on the severity level of the issue reported. The table below outlines the various support plans offered by Devolutions, each plan defining a distinct scope of customer support and technical assistance:

	Standard plan	Extended plan	Premium plan
Support level priority	Normal	High	Highest
24/7 access to our community forum, documentation, and Devolutions Academy	X	X	X
Online community forum support	X	X	X
Email support	X	X	X
Live chat support	X	X	X
Phone support		X	X
24/7 online community forum and email support			X
Dedicated customer success manager			X
Consulting, security guidance, and training (6 hours per year)			X

--- # 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/customer-support.md?ask=&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.