Get Help — Support & Community
A short map of every channel that exists, in the order you should try them.
Self-serve first
Most questions are answered faster by the docs than by a human. Before you reach out:
- Trade not executing as expected → Debug a Failed Alert or Trade Command gotchas
- API error codes → error codes reference
- Anything else → use the search bar in the top-right of these docs (
Ctrl+K)
If you found the answer in the docs but it took you longer than it should have, tell us — that is a documentation bug.
Community channels
Best for: quick questions, sharing setups, talking to other traders.
| Channel | Link | Best for |
|---|---|---|
| Telegram Community | t.me/tv_hub_org | Real-time chat, announcements, fellow users |
| Discord Server | discord.gg/3xqyXRm | Threaded discussions, channel-per-exchange |
| Twitter / X | @tvhub_org | Release news, short tips |
Community help is best-effort — fellow users answer when they have time.
Direct support
Best for: account-specific issues, bug reports, anything you cannot share publicly.
- Email: info@tv-hub.org
- Contact form: tv-hub.org/Home/Contact
- Telegram: post your question in the Telegram community.
Response times
| Channel | Typical first reply |
|---|---|
| Community (Telegram / Discord) | Best-effort, fellow users |
| Email / contact form — free tier | 1–3 business days |
| Email / contact form — paying users | Same business day |
Reporting bugs
The faster we can reproduce a bug, the faster it gets fixed. Use this template:
Subject: [BUG] <one-line summary>
Body:
User Token (last 4 chars only): ...XXXX
Exchange: e.g. Binance USDⓈ-M
Pair: e.g. BTCUSDT
Time (UTC): 2026-05-22 14:32
What I expected: <one sentence>
What actually happened: <one sentence>
Steps to reproduce: <numbered list>
Attach as much context as you can — the more we can see, the faster we reproduce it:
- Activity Log export filtered to the failed trade (export button on the Activity Log page).
- The exact Trade Command JSON you sent (the payload from your TradingView alert or script).
- Screenshots of the failure — the Activity Log entry, any error message, and the relevant part of your setup.
- Your TradingView setup — the alert configuration (Condition, Webhook URL, Message field) and, if relevant, the strategy/indicator you fired from.
- Your TVH setup — which exchange/API key, sizing mode, and any special options (DCA, hedge mode, trailing, etc.).
Send to info@tv-hub.org. Do not paste your full User Token — last 4 characters are enough for us to find your account.
Feature requests
We read every request, even when we cannot ship every one.
Subject: [REQUEST] <feature>
Body: describe the trading workflow you want to run and why the current setup blocks you. Concrete scenarios beat abstract wish lists.
Send to info@tv-hub.org.
Status page
TVH does not run a public status page yet. Live status — exchange outages, queue lag, planned maintenance — is posted in the Telegram community or Discord. If a trade should have executed and did not, check there first.
Security disclosure
Found a vulnerability? Please report it privately.
- Email: security@tv-hub.org (or info@tv-hub.org)
- What to include: affected endpoint or feature, reproduction steps, impact assessment, your contact for follow-up.
- Disclosure window: we ask for 90 days between report and public disclosure so we can patch and notify users.
- No formal bug bounty program at the moment — but we review every report we receive and will reward valid findings appropriately. We also credit researchers in this changelog on request.
Do not file security issues on Telegram, Discord, or Twitter.