> For the complete documentation index, see [llms.txt](https://ask.simplehw.eu/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.simplehw.eu/kb/technical-support/contact-support.md).

# Contact Support

## [**SUBMIT YOUR TICKET HERE!**](https://simplehw.eu/helpdesk/)&#x20;

## Instructions

In order to support you, we request you to provide the following info:

1. Product Name as written on the device you have a problem with&#x20;
2. Firmware version of the device
3. Device ID
4. Number of Messages sent by the device? Attach the CSV file if possible.
5. Were any downlinks used? If so, please share it with us.
6. **Issue description in detail:**
   * What do you want to achieve?
   * Which instructions are you following?
   * What steps have you taken?
   * What were the expected results?
   * What were the real results? &#x20;

If you can, attach a screenshot, an image, or a short video of your issue to the new ticket. This is often the easiest way for both of us.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ask.simplehw.eu/kb/technical-support/contact-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
