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

# Política de soporte de Velogic

Política de soporte de Velogic centrada en el correo electrónico y cómo obtener ayuda

## La política de soporte de Velogic es "el correo electrónico primero"

* Todas las consultas de soporte deben iniciarse por correo electrónico: <support@velogicfit.com>
* Nuestro objetivo es responder a todos los correos de soporte en el plazo de un día hábil, y a menudo mucho antes
* Si se trata de un problema de hardware o de un problema que requiera que veamos tu pantalla, puedes [reservar una sesión de soporte remoto aquí](https://calendly.com/velogic-darren/remote-support-30).

> **¿Por qué primero el correo electrónico?**
>
> El correo electrónico nos permite **priorizar**, para trabajar a través de **diferentes zonas horarias**, para mantener **registros** de nuestra conversación, para involucrar **colegas** cuando sea necesario, y para asegurarnos de que **¡no se nos pase nada!**
>
> No obtendrás una respuesta más rápida contactándonos por chat o redes sociales, así que por favor usa el correo electrónico.


---

# 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.velogicfit.com/es/general/support-policy.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.