# Set Up UpScalp Telegram Alerts Safely

**Last reviewed:** 2026-05-23.

Set up Telegram from official UpScalp links only. A working alert setup is not just joining a chat; the chat must be genuine, visible, unmuted, and tied to the right product path.

Use this page when you are setting up Telegram for the first time, alerts are not arriving, notifications look muted, or you are unsure whether a bot or channel is official.

## Use only these official destinations

1. Announcements: `https://t.me/upscalpannouncements`
2. Lite bot: `https://t.me/UpScalpLite_bot`
3. Premium access bot: `https://t.me/upscalp_access_bot`

Check links against [UpScalp Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links) before trusting a search result, forwarded message, or DM.

UpScalp support will not ask for seed phrases, private keys, exchange passwords, or API secrets in Telegram DMs.

## Verify the message before acting

Before following a Telegram instruction, check the message against this table.

| Check    | Continue only when                                                                                                                  |
| -------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Source   | The message is from an official bot, official channel, or official support route.                                                   |
| Username | The username matches the official link exactly, including capitalization and spelling.                                              |
| Request  | The message does not ask for seed phrases, private keys, exchange passwords, API secrets, recovery codes, or withdrawal permission. |
| Link     | The link matches an official UpScalp destination or an official announcement.                                                       |
| Urgency  | The message does not pressure you to move funds, reveal credentials, or bypass the normal flow.                                     |

If any check fails, stop setup and verify through the Official Links page before continuing.

## Choose the correct path

| Path             | Start here                           | What to expect                                     |
| ---------------- | ------------------------------------ | -------------------------------------------------- |
| Lite             | `https://t.me/UpScalpLite_bot`       | A simpler signal flow after Telegram setup.        |
| Premium          | `https://t.me/upscalp_access_bot`    | Verification before Premium delivery.              |
| Private Beta API | Access Bot after Premium eligibility | Approval required before relying on beta behavior. |

If you are not sure which path fits, use the Lite vs Premium guide before starting setup.

## Make the alert visible

After opening the correct UpScalp destination:

1. Send `/start` if the bot requests it.
2. Complete the bot prompts without switching Telegram accounts.
3. Pin the UpScalp chat.
4. Turn on notifications for the chat.
5. Confirm Telegram notifications are allowed at device level.
6. Confirm Focus mode, Do Not Disturb, battery saver, or app restrictions are not suppressing Telegram.
7. Keep the chat unarchived and unmuted.

## Test the setup before judging signals

Before trading from alerts:

1. Confirm the next UpScalp message appears in the expected chat.
2. Confirm the message came from an official destination.
3. Confirm notifications reach the device you actually monitor.
4. Read one full signal without placing a trade.

Do not place the first trade just to test alerts.

## If messages do not arrive

Check in this order:

1. Correct official bot or channel.
2. Correct Telegram account.
3. Chat not muted or archived.
4. Device and app notifications allowed.
5. Current UpScalp status or incident updates.
6. Premium verification status if you expect Premium delivery.

Then use the no-signals troubleshooting page or contact support with the exact chat, timestamp, and product path.

## Stop setup if the path changes

Stop and verify before continuing if:

1. A bot sends you to a different username than the official list.
2. A support account asks to continue in a private DM without clear reason.
3. You are asked to connect an exchange, wallet, or API key as part of ordinary Lite or Premium Telegram setup.
4. You are told to enable withdrawals or send credentials.
5. You are unsure whether the chat belongs to UpScalp.

## Related

1. [UpScalp Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links)
2. [UpScalp Lite vs Premium](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-plans-and-access)
3. [How to Complete UpScalp Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification)
4. [Why UpScalp Signals May Not Arrive](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals)


---

# 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/setup/upscalp-telegram-setup.md?ask=<question>
```

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.