Contact UpScalp Support
Contact UpScalp support with the account, setup, signal, and troubleshooting details needed for faster help.
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:
Announcements:
https://t.me/upscalpannouncementsOfficial links page: UpScalp Official Links and Channels
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.
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:
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:
Official link verification.
Telegram setup and delivery checks.
Premium verification issues.
Approved beta access questions.
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:
Telegram messages are missing
Telegram setup is unclear
Premium verification failed
A link, bot, or support contact looks suspicious
You suspect account compromise
What a useful report looks like
The fastest reports include:
A clear description of what was expected and what happened instead.
A screenshot that shows the timestamp and relevant error or missing state.
The official chat or bot where the issue happened, not a copied message from an unofficial group.
A report sent from the same Telegram account used for setup.
Whether the issue is on Lite, Premium, or approved beta.
One complete report is better than several partial messages.
After you send a report
Keep the original report in one thread where possible.
Do not send secrets or extra screenshots unless support asks for a safe, non-secret detail.
Do not retry verification or setup repeatedly while waiting unless the official guide tells you to do so.
If an official incident is active, wait for the next official update before repeating the same report.
If you suspect compromise, prioritize account protection before ordinary troubleshooting.
Related
Last updated