Notifications

TTMT runs in the cloud 24/7, so you do not need to watch the dashboard constantly. To keep you informed, TTMT sends real-time notifications directly to your Telegram account via a dedicated bot.

Setting Up Notifications

Connection Flow

1. Go to Settings > Notifications.
2. Click the Connect Bot button. This opens a link to the TTMT Notification Bot in Telegram.
3. Start a conversation with the bot by clicking Start in Telegram.
4. The bot sends you a verification code.
5. Enter the verification code back in the TTMT dashboard.
6. Once confirmed, your notification connection is active.

Separate from Channel Monitoring

The notification bot is a separate connection from your Telegram channel monitoring. Your channel monitoring uses the Telegram API to read signals from channels. The notification bot uses the Telegram Bot API to send you personal alerts. Both connections operate independently.

Notification Toggles

Once connected, you can independently enable or disable each of the 10 notification types. Go to Settings > Notifications to configure which events trigger a message.

#	Notification	What It Tells You
1	Trade Opened	A new trade was successfully executed on your account, including the symbol, direction, and lot size.
2	Trade Closed (Profit)	A trade closed in profit, with the P&L amount and close reason (TP hit, manual, signal close).
3	Trade Closed (Loss)	A trade closed at a loss, with the P&L amount and close reason (SL hit, manual, signal close).
4	Signal Received	A new signal was detected from one of your monitored channels, showing the parsed symbol and direction.
5	Signal Rejected/Skipped	A signal was received but not executed, with the reason (duplicate, validation failure, channel paused).
6	Breakeven Triggered	The stop loss was moved to breakeven (entry price + buffer) after a TP was hit.
7	TP Hit	A take profit level was reached and the corresponding positions were closed at profit.
8	SL Hit	The stop loss was triggered, closing remaining positions at the defined loss level.
9	Connection Issues	Your MetaTrader or Telegram connection dropped or is experiencing problems.
10	System Alerts	Important system-level events such as service restarts, maintenance windows, or critical errors.

Recommended Configuration

• Active traders: Enable all notifications to stay fully informed.
• Hands-off traders: Enable Trade Closed (Profit), Trade Closed (Loss), Connection Issues, and System Alerts. This gives you the outcomes without the noise.
• Debugging a channel: Temporarily enable Signal Received and Signal Rejected/Skipped to see exactly what the channel is sending and how TTMT handles each message.

Notification Format

Each notification message includes:

• Event type: Clearly labeled (e.g., "Trade Opened", "TP Hit").
• Symbol and direction: The instrument and whether it was a BUY or SELL.
• Key details: Relevant data such as lot size, P&L amount, TP level hit, or error reason.
• Timestamp: When the event occurred.
• Channel name: Which signal channel triggered the event (for trade and signal notifications).

Notifications are delivered in real-time, typically within seconds of the event occurring.

Troubleshooting Notifications

Not receiving notifications

Cause: The bot connection may have been interrupted.

Fix:

1. Go to Settings > Notifications and check if the bot status shows as connected.
2. If disconnected, click Reconnect and follow the verification flow again.
3. Make sure you have not blocked the TTMT Notification Bot in Telegram.
4. Check that at least one notification toggle is enabled.

Delayed notifications

Cause: Telegram's Bot API occasionally has delivery delays during peak usage.

Fix: This is a Telegram infrastructure issue and typically resolves on its own. Notification delivery does not affect trade execution -- trades are executed independently of notification delivery.

Notifications stopped after Telegram session reset

Cause: If you terminated all Telegram sessions or changed your phone number, the bot connection may need to be re-established.

Fix: Go to Settings > Notifications, disconnect the bot, and set it up again with the connection flow described above.