> 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/resources/contact.md).

# Contact

Email hello\@lid.pro or DM @albertofdez20 on X. What to include so a problem gets fixed on the first reply.

## Email

<hello@lid.pro>

You will get a reply from a person, not a ticket number.

## X

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

DMs are open.

## Reporting a problem

Include these five things and we can usually fix it on the first reply:

1. The email you use to log in
2. The product name or link involved
3. What you expected to happen
4. What actually happened
5. A screenshot, if you have one

Anything involving money that seems missing or a payout that looks wrong goes to the front of the line. Put "payment issue" in the subject line.


---

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