Feature

Telegram, e-mail and SMS alerts

A useful alert arrives during the incident. A useless alert arrives all the time, and you end up not reading it.

Ten monitored conditions

Drawdown decline from the high-water mark
Daily loss from the opening equity
Losing streak consecutive losing trades
Backtest drift real versus expected expectancy
Grade drop drop between two recalculations
Abnormal lot position outside the median lot
News blackout position during an announcement
Account offline bridge silent for too long
Target reached daily gain above the threshold
Low margin before broker liquidation

The cooldown

Every rule has its own delay, adjustable from five minutes to twenty-four hours. Once triggered, it stays silent for that delay even if the condition remains true.

This is a minor technical constraint and a major design decision. Without it, a 16% drawdown against a 15% threshold would produce one notification a minute for hours. By the third, you would mute notifications — and miss the next one, the one that mattered.

Choosing the right channel

Telegram

The fastest. Immediate notification with the numbers. Best reserved for conditions that call for a decision: drawdown, drift, abnormal lot.

E-mail

Good for tracking and archiving, poor for urgency. Suits informational alerts: target reached, account offline, grade drop.

SMS

Works without mobile data, arrives even with poor coverage. Keep it for what is genuinely critical — otherwise it loses exactly what makes it valuable.

Three severity levels

Every alert carries a level: information, warning, critical. The level is not decorative — it depends on how far the threshold was exceeded. A 16% drawdown against a 15% threshold is a warning; the same at 23% becomes critical. That lets you route channels according to what genuinely deserves to wake you.