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

# Discord & Support

This page explains how to get help from the Bullpen team and create a support ticket safely.

Join our Discord: [discord.gg/bullpen](https://discord.gg/bullpen)

> ⚠️ **Scam Warning:** Scammers often impersonate support staff or offer unsolicited help to gain your trust. Always disregard direct messages from individuals claiming to be support. Seek assistance only through private tickets.

## 1. Join Our Discord

To join our Discord server, click the link above. If you don't have a Discord account yet, create one by following the sign-up prompts, then return to join the server.

## 2. Verify Your Account

We require everyone to complete verification to prove they aren't a bot before accessing the server. This helps keep the community safe by limiting automated bot accounts from joining and spamming channels.

After joining, click the verification button and complete the captcha. This ensures only real users gain access, creating a secure and organized environment for everyone.

## 3. Ignore Direct Messages

**Never respond to unsolicited DMs** from anyone claiming to be from Bullpen support. Our team will never:

* DM you first
* Ask for your private keys or seed phrase
* Ask you to send funds to "verify" your wallet
* Share links to "claim" rewards or airdrops

If someone DMs you claiming to be support, block and report them immediately.

## 4. Create a Ticket

To get help from our official support team:

1. Create a ticket on our [ticketing website, Freshdesk](https://bullpen-help.freshdesk.com/support/tickets/new)
2. Select the category that best matches your issue:
   * Affiliate / Partnership
   * Question
   * Problem
   * Feature Requests
   * Other
3. Describe your issue in detail
4. A support team member will respond in your private ticket

## 5. Provide Information

When creating a ticket, include:

* Your Bullpen username or wallet address
* Description of the issue
* Screenshots if applicable
* Transaction IDs for deposit/withdrawal issues
* Steps to reproduce (for bugs)

The more detail you provide, the faster we can help.

## 6. Wait for Response

Our team typically responds within a few hours during business hours. For urgent issues (stuck funds, security concerns), mention "URGENT" in your ticket.

## Other Support Channels

* **Telegram**: [@BullpenSupportBot](https://t.me/BullpenSupportBot) for automated support and ticket creation
* **Email**: <support@bullpen.fi> for sensitive issues or if you can't access Discord
* **Twitter/X**: [@bullpen\_fi](https://twitter.com/bullpen_fi) for general questions (not account-specific issues)

## Community

Beyond support, our Discord has channels for:

* Trading discussion
* Feature requests
* Alpha and market chat
* Announcements

We'd love to have you in the community!


---

# 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.bullpen.fi/support/discord.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.