# Support

Something not working as expected? Here's how to reach us, fast.

## Telegram support

Primary channel: [@ayebot\_support](https://t.me/ayebot_support)

* **Account or wallet issues** — DM the support handle with your Telegram username and a short description.
* **Stuck transactions** — include the chain (SOL or BSC), the operation ID if you have it, and the approximate time of the transaction.
* **Bug reports** — screenshot + repro steps help us fix things in hours instead of days.

We try to answer within a few hours during the day, and within 24 hours overnight.

## What to include in a bug report

|                            |                                               |
| -------------------------- | --------------------------------------------- |
| **Your Telegram username** | so we can find your account                   |
| **What you tried to do**   | one sentence is fine                          |
| **What actually happened** | including any error message                   |
| **When**                   | rough timestamp (with timezone if it matters) |
| **Chain involved**         | Solana, BSC, or both                          |
| **Screenshot**             | optional but helpful                          |

## Feature requests

Got an idea? Drop it in [@ayebot\_support](https://t.me/ayebot_support) with `feature:` at the start of the message so it routes to the product backlog. Real user requests are the main source of our roadmap.

## What support won't do

We can't recover funds from external mistakes — sending to the wrong address, falling for a phishing scam, sharing your seed phrase. Crypto's most painful lesson is that **chain transactions are final**. Double-check addresses; never share your seed.

We also can't move funds for you or override your wallet's signing — that's the whole point of self-custody. If you need to send from your wallet, you do it from your wallet.

## What to read next

* [Self-custody](/wallet-and-security/self-custody.md) — what we can and can't see, and what to do if you suspect compromise
* [Bot commands](/reference/bot-commands.md) — many "issues" are actually just an unknown command — check first
* [Getting started](/getting-started.md) — if you're brand new, the onboarding may answer your question


---

# Agent Instructions: 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:

```
GET https://docs.ayebot.io/reference/support.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.