Appearance
Are you an LLM? You can read better optimized documentation at /billing-and-account/notifications.md for this page in Markdown format
Notifications
TTMT runs 24/7 in the cloud, so you don't have to watch the dashboard — it can push real-time alerts straight to your Telegram. A dedicated notification bot messages you when signals come in, trades open or close, take-profits and stop-losses hit, and errors occur. This page covers connecting the bot and choosing exactly which events you want to hear about.
Connecting the notification bot
Go to Settings → Notifications, then:
- Click Connect Telegram.
- TTMT shows a connection code (displayed large, with a copy button) and a button to open @ttmt_notifications_bot.
- Send the code to the bot in Telegram.
- The dashboard confirms automatically — "Telegram connected successfully".
INFO
Your connection code is valid for 5 minutes. If it expires before you send it, click New Code to generate a fresh one.
Example: You generated a code but it stopped working — it expired after 5 minutes. Click New Code and resend the new one to the bot.
Separate from channel monitoring
Separate from channel monitoring
The notification bot only sends you alerts; it never reads your channels. It is a different connection from the channel-reading link on your profile, and disconnecting one does not affect the other.
Notification types
Once connected, ten independent toggles control which events send you a message. All toggles default to on.
| Toggle | When it fires |
|---|---|
| Signal Received | When a new trading signal is detected |
| Signal Modifications | When a signal modifies your trades (SL, TP, BE) |
| Trade Opened | When a trade is executed |
| Trade Closed | When a trade is fully closed |
| Take Profit Hit | When a TP level is reached |
| Stop Loss Hit | When stop loss is triggered |
| Broker Errors | Connection or execution errors |
| Warnings | System warnings and alerts |
| Manual Actions | When you make changes in MT4/MT5 |
| Signal Failures | When a signal fails to execute |
Trade Closed is a single toggle — it covers both winning and losing closes rather than splitting them.
Oracle notifications (limited preview)
If your account is in the Oracle limited preview, you may see additional notification options for Oracle verdicts alongside the toggles above. Oracle is enabled per account on request and is rolling out gradually, so these options only appear if it is active on your account — and their exact labels and behavior may change before general release.
Testing and disconnecting
Once connected, a Test button sends a sample notification so you can confirm delivery. A Disconnect button unlinks the bot after a confirmation dialog — you can reconnect anytime with a fresh code.
Commands you can send the bot
The notification bot is not just one-way — you can type a few simple commands straight into the chat with @ttmt_notifications_bot and it replies. These commands manage the notification connection itself; they do not touch your trades, your channels, or your settings. Think of them as a shortcut for the same connect/disconnect actions you'd otherwise do on the dashboard.
| Command | What it does |
|---|---|
| /start or /help | Shows the welcome message and how to connect — handy if you've lost the linking instructions. |
| /status | Reports whether the bot is currently connected and which notification types are switched on. |
| /stop | Disconnects the bot — exactly the same as pressing Disconnect on the Notifications page. Alerts stop until you reconnect. |
If you send anything the bot doesn't recognize, it replies with a short list of the commands above, so you can always rediscover them from inside the chat. (Sending your 6-digit code is what connects the bot in the first place — see Connecting the notification bot above.)
Example. You changed phones and aren't sure your alerts are still wired up. Send /status to the bot — it replies with your connection state and the toggles that are on, without you opening the dashboard at all.
/stop does not stop trading
/stop only unlinks the notification bot — it silences alerts and nothing more. Your channels keep monitoring and TTMT keeps opening and managing trades exactly as before. To actually pause or halt your trading, use the in-dashboard controls instead — the one-click kill switch and the daily-loss halt on Emergency Controls, or pause a single channel or account from its settings.
Recommended setups
- Stay fully informed: all ten toggles on.
- Hands-off: Trade Closed, Stop Loss Hit, Broker Errors, and Warnings — outcomes and problems only, less noise.
- Debugging a channel: turn on Signal Received, Signal Modifications, and Signal Failures to see exactly what a channel sends and how TTMT handles each message.
Example: A channel sends signals but nothing executes. Turn on Signal Received and Signal Failures to see whether the signal arrived and why it didn't fill. Or you closed a position manually in MT5 — Manual Actions tells you TTMT noticed your change.
Troubleshooting
Not receiving alerts. Check the bot shows Connected on the Notifications page. Confirm at least one toggle is on, and make sure you haven't blocked the bot in Telegram. If needed, disconnect and reconnect using the flow above.
Code expired. Connection codes last 5 minutes. Click New Code and resend.
Delayed alerts. Telegram's bot delivery can lag at peak times.
TIP
Notification delays never affect your trades. Trade execution runs independently of alert delivery, so a late message does not mean a late trade.
After a Telegram session reset. If you reset your Telegram sessions or changed your phone number, disconnect and reconnect the bot.
Related pages
- Profile Settings — the channel-reading connection
- Emergency Controls — how to actually pause or halt trading (not /stop)
- Connection Issues — fixing a bot that won't connect or stopped delivering