> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/user-hub/administration/contact-support.md).

# Contact Support

Send a support request.

Use **Contact support** when something is not working or you need help from the Ninox support team.

Fill in all form fields before you submit your request. To help the team understand the issue faster, include what you tried, what happened, and a screenshot or file if it helps.

{% stepper %}
{% step %}
**Open Help & support**

In the left sidebar, go to the bottom section.\
Click <i class="fa-circle-question">:circle-question:</i> **Help & support**.
{% endstep %}

{% step %}
**Select Contact support**

In the menu that opens, click **Contact support**.
{% endstep %}

{% step %}
**Fill in the form**

Fill in all fields in the form.\
Check your email address, first name, and last name.\
Select a topic, then add a subject and your message.
{% endstep %}

{% step %}
**Add an attachment if needed**

Click **Choose Files** to attach a file.\
This is useful for screenshots or other supporting material.
{% endstep %}

{% step %}
**Submit your request**

Click **Submit**.\
Your support request is then sent to the Ninox support team.
{% endstep %}
{% endstepper %}


---

# 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.ninox.com/user-hub/administration/contact-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.