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

# Support and feedback

Use **Support & Feedback** to report a problem or suggest an improvement.

## Open Support & Feedback

While signed in:

1. Open the account menu.
2. Select **Support & Feedback**.
3. Choose **Support** or **Feedback**.

On mobile, open the navigation menu and select **Support & Feedback**.

If you cannot sign in or open the form, email <support@duels.trade>.

## Discord community

Join the official [duels.trade Discord](https://discord.com/invite/B2rrt5FvbH) for community help, product discussion, and general questions.

For account, wallet, transaction, or other sensitive issues, use the private **Support & Feedback** form or email <support@duels.trade>. Do not post private account information in Discord.

## Support request

Choose **Support** when something is not working as expected. Enter at least one contact method—email, Telegram handle, or Discord handle—so support can follow up, then describe the issue. The optional **Duels platform wallet** field is specifically for your wallet on Duels and is not used as a contact method. Include any other relevant wallet addresses in the issue description.

Include:

* What happened
* What you expected
* Steps to reproduce
* Mainnet or Testnet
* Screenshot when useful

Depending on the issue, also include:

| Issue                              | Useful details                                            |
| ---------------------------------- | --------------------------------------------------------- |
| Duel entry, scoring, or settlement | Duel name, invite code, game mode, and approximate time   |
| Deposit, send, or transfer         | Transaction hash, network, asset, and wallet address      |
| Trading or orders                  | Market, order type, approximate time, and any error shown |
| Account or sign-in                 | Sign-in method and the exact message shown                |
| Referral                           | Referral code and the affected action                     |

{% hint style="warning" %}
Never send a private key, recovery phrase, password, one-time code, or full payment-card details. duels.trade support does not need them.
{% endhint %}

## Product feedback

Choose **Feedback** to share:

* **What do you like?**
* **What don't you like?**
* **Suggestion**

Add enough context to explain where the change would apply and what outcome you want.

The optional **Duels platform wallet** field is specifically for your wallet on Duels. Include any other relevant wallet addresses in the feedback text.

## Screenshots

The form accepts PNG, JPEG, WEBP, and GIF images smaller than 5 MB. Review the image before sending it and remove any information you do not want included in the private support ticket.

## After submission

A successful submission displays:

> Request submitted. We’ll follow up using the contact details provided.

If the form cannot send the request, retry once and then email <support@duels.trade>.


---

# 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.duels.trade/help/support.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.