> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/support/admin-support/escalating-to-daxium-support.md).

# Escalating to Daxium Support

How to contact Daxium support and what to include in your request.

When you encounter an issue that cannot be resolved through the documentation, the Daxium support team is available to help.

## Contact

**Daxium Support — Dubai office**\
Email: <dubai.support@daxium.com>\
Hours: Monday to Friday, 9 am – 6 pm (Gulf Standard Time, UTC+4)

## What to include in your request

The form below will guide you through the information expected. Please fill it in as completely as possible.

**General description of the issue**\
Describe what you were trying to do, what you expected to happen, and what actually happened.

**When the issue appeared**\
When did you first notice the problem?\
Has it occurred again since, or was it a one-off?

**Steps to reproduce**\
Do you know how to reproduce the problem?\
If possible, list the steps that led up to the issue.

**Environment**\
On which environment are you experiencing the problem?

* Back Office (web)
* Android v2
* iOS

**Mobile app version**\
If the issue concerns a mobile environment (Android or iOS), which version is installed?\
This information is available in Settings, accessible from the app's main menu.

**Affected user account(s)**\
Indicate only the account(s) concerned.

{% hint style="warning" %}
Do not include the passwords of these accounts.
{% endhint %}

**URLs of the affected elements (Daxium back-office)**\
Fill in only what applies to your case:

* Form:
* Example submission:
* List:
* Report:

**Additional information**\
Provide any information you consider relevant to resolving the issue, for example:

* Screenshots
* Screen recording of the action on mobile ([Android](https://support.google.com/android/answer/9075928?hl=en) / [iOS](https://support.apple.com/en-us/102653))
* If the issue concerns a report: an example of a generated file

{% hint style="info" %}
The more detail you provide upfront, the faster the team can diagnose the issue without needing to ask for clarification.
{% endhint %}


---

# 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://www.center.daxium-air.com/user-documentation/support/admin-support/escalating-to-daxium-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.