> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pd-ag/providing-feedback.md).

# Feedback and Support

If you would like us to improve or add a specific feature to the Parallels Management Portal, you can use our feedback form by clicking on the user icon in the top-right corner and selecting the **Provide Feedback** option. Just type in your request and hit **Send**, and our Product Management team will receive your idea via email.

<figure><img src="https://content.gitbook.com/content/KtRUprxh035S97pZeygw/blobs/mLeyypp8djGmT8JmFutv/PMP_Feedback.png" alt="" width="336"><figcaption></figcaption></figure>

### Service availability

Before contacting our support, you can check the Parallels Desktop Services section of our [status page](https://status.parallels.com/) for service availability.

### Support

To contact support, navigate to [this section](https://my.parallels.com/support/pde) of your Parallels My Account customer area. Your ongoing and previous support requests can be tracked using [this page](https://my.parallels.com/support/tickets).


---

# 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.parallels.com/landing/pd-ag/providing-feedback.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.
