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

# Customer Support

Need help? We've got your back. If you're stuck, experiencing a bug, or just have a question — here's how to reach us and get help fast.

***

### How to Contact Gremsy Support

**Email:** <support@gremsy.com>\
**Live Chat:** Monday–Friday, 8:00–17:00 (GMT+7)

***

### Need Help With?

Whether you're looking for **technical support**, need help using your product, or have questions about **repairs or warranty**, we're here to assist.

***

### Before You Reach Out

To help us support you faster, please include:

* A clear description of the issue
* Steps to reproduce (if applicable)
* Screenshots, logs, or error messages
* Serial number and product model
* Firmware/app version, software, and SoM version

***

### What to Expect

* We aim to respond within **24 hours on weekdays**
* More complex issues may take longer—we’ll keep you updated
* **Urgent bugs or hardware failures** are prioritized
* For warranty or service requests, we may ask for purchase details and photos/videos

***

**Thank you for choosing Gremsy.**\
Your feedback helps us improve every step of the way.

— **Gremsy Support Team**

***


---

# 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.gremsy.com/help-center/customer-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.
