> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/platform/english/appendix/consulting-and-support.md).

# Consulting and Support

On this page, you will find the right contacts for your platform solution and learn how to reach our support team for user inquiries and technical issues.

On this page, you can find the contact persons responsible for your platform solution and learn how to reach our support team for application-related questions and technical issues.

If you are interested in Payrexx platform solutions or have questions about your existing platform, our [advisory team](#advisory-team) looks forward to hearing from you.

For application-specific questions or technical issues, please use our [support platform](#support-team).

## Platform Advisory Team

Our advisory team is happy to support you with any questions regarding our platform solution. Please contact us via the following page:

{% embed url="<https://payrexx.com/en/company/sales>" %}

## Support Team

For any questions regarding the use of Payrexx, managing your Payrexx account, or technical issues, you can contact our support team at any time via the following link:

{% embed url="<https://support.payrexx.com/en/support/home>" %}


---

# 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.payrexx.com/platform/english/appendix/consulting-and-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.
