> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/es/resources/contact.md).

# Contacto

Escribe a alberto\@lid.pro o envía un mensaje a @albertofdez20 en X. Qué incluir para que un problema se resuelva en la primera respuesta.

## Correo

<alberto@lid.pro>

Cada mensaje llega al fundador. Te responde una persona, no un número de ticket.

## X

[@albertofdez20](https://x.com/albertofdez20)

Los mensajes directos están abiertos.

## Reportar un problema

Incluye estas cinco cosas y casi siempre lo arreglamos en la primera respuesta:

1. El correo con el que entras
2. El nombre o enlace del producto en cuestión
3. Qué esperabas que pasara
4. Qué pasó en realidad
5. Una captura de pantalla, si la tienes

Cualquier cosa de dinero que parezca perdida o un pago que se vea mal va al frente de la fila. Pon "problema de pago" en el asunto.


---

# 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://docs.lid.pro/es/resources/contact.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.