> For the complete documentation index, see [llms.txt](https://polyhelper.gitbook.io/polyhelper-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polyhelper.gitbook.io/polyhelper-docs/community-and-team/social-links.md).

# Social Media & Links

PolyHelper has an active and growing community across multiple platforms. Join us to stay updated on new features, earn bonus points, and connect with other Polymarket traders.

***

## Official Channels

### Twitter / X

[**@Poly\_Helper**](https://x.com/Poly_Helper)

Our main channel for:

* Product announcements and feature releases
* New market coverage additions
* Social tasks and bonus point opportunities
* Polymarket alpha and trading insights
* Community highlights and trader spotlights

Follow and turn on notifications to never miss a feature drop.

***

### Telegram Channel

[**t.me/polyhelper**](https://t.me/polyhelper)

Official PolyHelper channel — announcements, feature releases, and updates.

### Telegram Community

[**t.me/polyhelpercommunity**](https://t.me/polyhelpercommunity)

The most active discussion hub for PolyHelper users:

* Real-time Polymarket market discussion
* Community alpha sharing
* Feature feedback and requests
* Support from the team and other users

### Telegram Support

[**t.me/polyhelpers**](https://t.me/polyhelpers)

Direct technical support — reach out here if you have issues with the extension.

***

### Discord

[**discord.gg/2RfMcye8fG**](https://discord.gg/2RfMcye8fG)

Discord is the home for structured community channels:

**PolyHelper**

* `#announcements` — official product updates
* `#updates` — feature and changelog updates
* `#official-links` — links to all PolyHelper resources

**Community**

* `#general` — open discussion
* `#trading` — market discussion and alpha
* `#lp-farming` — liquidity providing strategies
* `#profits` — share your wins
* `#your-tweets` — share your X posts

**Support**

* `#support-ticket` — technical help with the extension
* `#feedback-suggestions` — feature requests
* `#bug-report` — report issues

***

### Website

[**polyhelper.io**](https://polyhelper.io)

The main landing page with:

* Extension download link
* Feature overview
* Rewards program details
* Blog and updates

***

## Team Members on X

| Name      | Role            | X Profile                                     |
| --------- | --------------- | --------------------------------------------- |
| Valeriy   | CMO, Co-Founder | [@0xd1namit](https://x.com/0xd1namit)         |
| Andrey    | CTO, Co-Founder | —                                             |
| Stanislav | Growth Lead     | [@AdzProsperous](https://x.com/AdzProsperous) |
| Alex      | CBDO            | —                                             |

***

## Stay in the Loop

The best way to stay updated:

1. **Follow** [**@Poly\_Helper**](https://x.com/Poly_Helper) on X with notifications on
2. **Join** [**Telegram Community**](https://t.me/polyhelpercommunity) for real-time market discussion
3. **Subscribe to** [**Telegram Channel**](https://t.me/polyhelper) for announcements
4. **Join the** [**Discord**](https://discord.gg/2RfMcye8fG) for structured community channels and support

New features, social tasks with bonus points, and Polymarket market coverage additions are announced across all channels simultaneously.

***

## Contact & Support

For technical support or bug reports:

* Post in `#support-ticket` or `#bug-report` on [Discord](https://discord.gg/2RfMcye8fG)
* Message on [Telegram Support](https://t.me/polyhelpers)
* DM [@Poly\_Helper on X](https://x.com/Poly_Helper)

For business inquiries and partnerships:

* Contact Alex (CBDO) via [LinkedIn](https://www.linkedin.com/in/alex-onishenko/)
* Email: <polymarkethelper@gmail.com>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://polyhelper.gitbook.io/polyhelper-docs/community-and-team/social-links.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 `build a script that syncs our docs to a CMS` 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.