> For the complete documentation index, see [llms.txt](https://www.aevo.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aevo.xyz/docs/help-and-support/tickets.md).

# Support Tickets

Please read this page before you open a ticket. Tickets may take up to 48 hours for a response, with longer wait times on weekends.

#### Recommendations

1. Search the Docs to better understand concepts you have questions about.
2. If you cannot find an answer, you can open a ticket via Discord or email:
   1. For email: use [this form](https://aevoxyz.zendesk.com/hc/en-us/requests/new).
   2. For Discord: go to the [Discord server](https://discord.com/invite/aevo), find the *questions* channel and ask our community and staff. Support only takes place inside the official Aevo Discord. Do not respond to any DMs; they are from impersonator accounts.

#### Important reminders

1. Never share your wallet, seed phrase, password, or private key with anyone or any website. If someone reaches out to you directly, assume they are a scammer.
2. Always check the full URL of any website you interact with. Scammers use look-alike domains (e.g., "aevo-xyz.com", "aev0.xyz") to prompt users to sign malicious transactions.
   1. The official Aevo website is <https://www.aevo.xyz/>
   2. You can trade on <https://app.aevo.xyz/>
   3. The official documentation is <https://docs.aevo.xyz/>
   4. The official X account is <https://x.com/aevoxyz>
   5. The official Telegram updates channel is <https://t.me/aevoupdates>


---

# 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://www.aevo.xyz/docs/help-and-support/tickets.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.
