> For the complete documentation index, see [llms.txt](https://upscalp.gitbook.io/upscalp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support.md). # Contact UpScalp Support Contact support after you have checked the relevant setup or troubleshooting page. A complete first message usually gets a faster answer. **Last reviewed:** 2026-05-23. Prepare one complete support report when you need help with setup, access, missing signals, or suspicious messages. ## Use official routing only Start from official UpScalp destinations: 1. Announcements: `https://t.me/upscalpannouncements` 2. Official links page: [UpScalp Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links) 3. Email escalation: `upscalpbot@gmail.com` Do not send account details to unsolicited DMs. ## Check the right page first Many support issues can be narrowed down before you send a report. | Before reporting | Check | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | No signal arrived | Confirm Telegram notifications, your plan, market quietness, and official status updates. | | Premium access failed | Confirm you used the official Access Bot and did not switch Telegram accounts during verification. | | A route looks suspicious | Compare it against the official links page before clicking again. | | API or automation seems unavailable | Confirm you have explicit Private Beta approval before troubleshooting API behavior. | | A trade result was poor | Review signal reading, risk management, and skip criteria; support cannot turn a trading outcome into a setup fault without evidence of a product issue. | If the issue still remains after the relevant check, send one complete report. ## Send one complete report Use this format: | Field | What to send | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | | Your plan | Lite, Premium, Premium verification, or approved Private Beta. | | Telegram username | The username or account used for UpScalp setup. | | UTC timestamp | When the issue happened or when the last verification attempt was made. | | What you expected | The signal, access confirmation, bot response, or status update you expected to receive. | | What happened instead | Exact error text, missing message, failed instruction, or different outcome. | | Checks already completed | The setup, status, Telegram, or verification checks you already tried. | | Screenshot | A screenshot of the error or missing state if it does not expose private keys, API secrets, passwords, or personal recovery material. | Do not send seed phrases, private keys, exchange passwords, API secrets, one-time codes, or withdrawal-related credentials. ## What support can help with Support can help with: 1. Official link verification. 2. Telegram setup and delivery checks. 3. Premium verification issues. 4. Approved beta access questions. 5. Documentation gaps or unclear instructions. Support does not make trading decisions for you, guarantee outcomes, or recover losses from a trade. Support will never ask for seed phrases, private keys, exchange passwords, API secrets, or withdrawal credentials. ## Choose the right starting page Use the most relevant guide before sending a support report: | Issue | Start here | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Telegram messages are missing | [Why UpScalp Signals May Not Arrive](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals) | | Telegram setup is unclear | [Set Up UpScalp Telegram Alerts Safely](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup) | | Premium verification failed | [How to Complete UpScalp Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification) | | A link, bot, or support contact looks suspicious | [UpScalp Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links) | | You suspect account compromise | [Protect Your UpScalp and Exchange Accounts](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-security-and-account-protection) | ## What a useful report looks like The fastest reports include: 1. A clear description of what was expected and what happened instead. 2. A screenshot that shows the timestamp and relevant error or missing state. 3. The official chat or bot where the issue happened, not a copied message from an unofficial group. 4. A report sent from the same Telegram account used for setup. 5. Whether the issue is on Lite, Premium, or approved beta. One complete report is better than several partial messages. ## After you send a report 1. Keep the original report in one thread where possible. 2. Do not send secrets or extra screenshots unless support asks for a safe, non-secret detail. 3. Do not retry verification or setup repeatedly while waiting unless the official guide tells you to do so. 4. If an official incident is active, wait for the next official update before repeating the same report. 5. If you suspect compromise, prioritize account protection before ordinary troubleshooting. ## Related 1. [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links) 2. [Why UpScalp Signals May Not Arrive](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals) 3. [UpScalp Status and Service Updates](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-status-and-service-updates)