Fastest channel
Open the Telegram bot and use /feedback with a short, specific note.
Support
Use Telegram feedback as the official support route or Discord for public community discussion. Send clear details, commands used, token mint, expected behavior, and what looked wrong.
Plain-English beta notice
For token-output issues, include the exact mint and a short note about what seemed off. Do not send seed phrases, wallet credentials, or sensitive account details.
Direct answer
Use /feedback bug ..., /feedback privacy request ..., or /feedback feature_request ... in Telegram. Discord is for public community discussion; do not post sensitive account data there.
Standalone page
Current public-beta support routes and response expectations.
Open the Telegram bot and use /feedback with a short, specific note.
Join Discord for public bug-report discussion, feature ideas, safety examples, and case studies. Do not post private identifiers, credentials, seed phrases, or sensitive account details.
Include command used, token mint or link, what happened, and what you expected.
Use /feedback privacy request ... from the relevant Telegram account or chat and include enough context to identify the records.
If a score looks wrong, include source links or evidence so the scoring logic can be reviewed.
If watchlist alerts stop, mention the watched token and whether you changed chats, blocked the bot, or moved groups.
Help build the product by telling us what would make the bot more useful for research-only token review.
Use /feedback feature_request with the command, explanation, alert, or risk check you would like to see next.
This is beta support. Critical reliability issues get priority over feature requests.
Research-only / NO_TRADE