# 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. Use this page when you need to contact support, report a problem, prepare a support ticket, or verify whether a support/admin message is safe to follow. ## 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, product path, market quietness, and official status updates. | | Premium access failed | Confirm you used the official Access Bot and did not switch Telegram accounts mid-flow. | | 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 product evidence. | If the issue still remains after the relevant check, send one complete report. ## Send one complete report Use this format: | Field | What to send | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | | Product path | 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 and cannot help with | Support can help with | Support cannot do | | ------------------------------------------- | ------------------------------------------------------------------------------------- | | Official link verification. | Tell you whether to enter, hold, or exit a trade. | | Telegram setup and delivery checks. | Guarantee signal outcomes, price movement, liquidity, or profit. | | Premium verification issues. | Recover losses from a trade decision. | | Approved beta access questions. | Make API access self-serve without approval. | | Documentation gaps or unclear instructions. | Accept seed phrases, private keys, 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 | [Complete UpScalp Premium Verification Without Breaking the Flow](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 support cannot verify from a vague report Support usually cannot diagnose an issue from only: 1. "It does not work." 2. A screenshot without a timestamp or product path. 3. A copied message from an unofficial group. 4. A report sent from a different Telegram account than the one used for setup. 5. Missing details about whether the issue is 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) --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.