> 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-service.md).

# Customer Service

The most common questions and answers

<details>

<summary>What are the warranty conditions?</summary>

* **Warranty Period:** All Gremsy products are covered by a **12-month warranty** from the date of purchase.
* **Product Condition:** The product must have the **original warranty seal intact** and show no signs of tampering or user-inflicted damage.
* **Purchased from a Distributor:** If you purchased the product through an official distributor, please **provide the purchase invoice** to verify the warranty period.

</details>

<details>

<summary>How to Request a Repair?</summary>

1. **Contact**: Email us at **<support@gremsy.com>**
2. **Provide**:
   * The product **serial number**
   * A **clear description of the issue** or malfunction
3. After reviewing your request, the **Gremsy Support Team will issue an RMA number** (Return Merchandise Authorization) and guide you through the next steps.

</details>

<details>

<summary>How long is the repair time?</summary>

The average repair time is **10 business days**, **excluding shipping time**.

</details>


---

# 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-service.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.
