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

# Contact & support

We're here to help.

## Email

* **Support:** <support@genvibe.pro>
* **Billing:** <billing@genvibe.pro>

When emailing about a problem, include:

* What you were trying to do.
* What happened (and any error message).
* A link to your project if possible.

## Before you reach out

Many questions are answered in:

* [FAQ](/help/faq.md)
* [Troubleshooting](/help/troubleshooting.md)

## Community & social

* **Discord:** [Join the community](https://discord.gg/HStFjHzWbH) — the fastest way to get help and share what you build.
* **Twitter / X:** [@genvibepro](https://twitter.com/genvibepro)

## Feature requests & feedback

We build GenVibe based on what users need. Send ideas and feedback to <support@genvibe.pro> — we read everything.


---

# 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.genvibe.pro/help/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.
