Why Telegram
Setting it up
Open the alerts section in your account settings
Link your Telegram account
Send a test message
Choose which events you want
Check it still works after a week
Alerts worth having
| Event | Why |
|---|---|
| Broker session expired | The single most common cause of a missed morning |
| Order rejected | Something needs fixing today, not next week |
| Strategy stopped unexpectedly | Silent stops are the expensive kind |
| Stop loss hit | Not actionable, but you should know |
| Daily summary after close | One message that confirms the day behaved |
Alerts that become noise
- Every order placement. A strategy entering four legs produces four messages before 9:21.
- Every price update. You are not going to act on these and they bury the ones you would.
- Paper trading activity, beyond a daily summary. Nothing here is urgent.
Reading an alert correctly
- Read what the alert actually says. "Order rejected" and "session expired" need different responses and are easy to skim past.
- Open the logs. The strategy's decision and the broker's reply are what tell you the cause.
- Check whether a position is open. A failed exit is more urgent than a failed entry.
- Fix one thing, then re-check. Changing three things at once tells you nothing about which was wrong.
What alerts do not replace
- Reading the logs when something looks wrong — an alert says what, logs say why
- Your morning broker login, where the broker requires it
- Knowing where the force stop is
- Checking positions directly in your broker account
- A weekly look at performance rather than daily reaction
A reasonable default configuration
- Session expiry — on, this is the important one
- Order rejection — on
- Strategy stopped unexpectedly — on
- Stop loss hit — on
- Daily summary — on
- Individual order placements — off
- Paper trading activity — off except the summary
The short version
- Alerts exist so you learn about problems the same day
- Session expiry is the alert that pays for the whole setup
- Switch off per-order and price alerts — noise buries the signal
- Test the channel periodically; silent failure is its failure mode
- An alert says what happened; the logs say why
Frequently asked questions
Email gets filtered and in-app notifications need you to be in the app. A Telegram message reaches your phone whether or not you were thinking about trading.
Broker session expired, order rejected, strategy stopped unexpectedly, stop loss hit, and a daily summary after close.
Individual order placements and price updates. A four-leg strategy produces four messages before 9:21, and that noise makes you stop reading the channel entirely.
Broker session expiry. A morning message gives you time to log in before your entry window, which is the most common cause of a missed trading day.
No. An alert tells you what happened; the logs tell you why. You need both when something looks wrong.
Test them periodically. The failure mode is silent — you stop receiving messages and read the silence as everything being fine.
Treat it as a problem rather than as a quiet period. Send a test message, confirm the link is still active, and check your logs directly for the days you received nothing.
You can, and a daily summary is usually enough. Per-trade paper alerts are noise, because nothing in paper mode needs acting on urgently.
Start with a free 3-day trial
Build a strategy, backtest it and run it on paper — no broker, no IP and no money needed to try it.
