Telegram is the best place to receive a trading alert — it is fast, it is on your phone, and it renders images inline. It is also where most alert setups quietly fail, for one reason nobody explains up front.
The rule that breaks every first attempt
A Telegram bot cannot start a conversation with you. This is a platform restriction, not a limitation of any particular product. The bot may only send messages to a chat that has already messaged it first.
So the sequence is always: you open the bot, you send it something, and only then can it reach you. Configure an alert destination without having done that and it will fail every single time — usually with no visible symptom beyond alerts that never arrive.
Why your @username will never work
The second trap. It is natural to enter @yourname as the destination, and it looks like it should work. It
cannot. A bot has no way to resolve a personal @username to a chat it is allowed to message. Telegram deliberately does
not expose that.
What a bot needs is a numeric chat ID — something like 123456789. That is the only thing
that addresses a chat. chartTrigger now rejects a non-numeric Telegram destination at the point you add it, rather than
accepting it and failing forever afterwards.
Getting your chat ID, in one message
Historically this was the worst part of the process: people were sent to third-party ID-lookup bots, or told to paste a URL containing their bot token into a browser and read raw JSON.
chartTrigger handles it directly:
- Open the alert destinations screen and choose Telegram. It gives you a
t.melink to the actual bot — resolved live from the bot itself, not assumed. - Tap the link and send the bot any message. "hi" is fine.
- It replies with your numeric chat ID.
- Paste that number back as the destination.
- Confirm the verification code it sends.
The replying part is a real piece of the system: an inbound long-poll that answers any private message with that chat's ID. Without it the bot simply never responds to anything, which reads exactly like a dead bot rather than a missing feature.
When alerts stop: read the recorded error
A destination that fails should say why. Every send that targets a destination — success or failure, including the verification code itself — writes its real result back to that destination. So a Telegram address that has failed every time since you added it shows the actual error, not a dash.
The usual causes, in order of frequency:
- You never messaged the bot. Overwhelmingly the most common.
- An @username was entered instead of a numeric ID.
- The bot was blocked at some point and never unblocked.
- Group chat, bot not added, or added without permission to post.
Getting the chart into the alert
Text alerts make you do the work. "EURUSD crossed 1.1570" tells you a number and leaves you opening a platform to see what it meant.
chartTrigger renders a chart image from the candles the engine actually evaluated — not a generic screenshot — draws your level on it, and marks the bar that fired. Telegram receives it as a photo with the alert text as the caption. If Telegram refuses the photo for any reason, the text still arrives; a missing piece means no picture rather than a wrong one. Email inlines the same image.
The alert also reports the engine's own share of the delay, measured from the tick's timestamp to the recorded fire, so latency is a number you can read rather than a feeling.
Groups and multiple destinations
A Telegram group works the same way — add the bot to the group and use the group's numeric ID, which is negative. And a rule is not limited to one destination: Telegram for the ones you act on, email for the record, a webhook for anything else you run.
No broker account needed
Telegram alerts run on the free public market feed, so you can have chart-carrying alerts on Bitcoin, EUR/USD, gold or an index without connecting a broker at all. See price alerts without a broker.
Common questions
Why does the Telegram bot not respond to me?
If it responds to nothing at all, it has no inbound handler. chartTrigger's bot replies to any private message with that chat's numeric ID.
Can I use my @username as the destination?
No. A bot cannot resolve a personal @username to a chat. Use the numeric chat ID.
Why did alerts stop arriving?
Check the destination's recorded error — the real result of the last send is written there, including failures.
Get alerts that carry the chart
Telegram, email and webhooks — with the candles the engine evaluated, your level drawn on them, and the firing bar marked.
Create a free accountRead next
Risk note. This article is educational material about how chartTrigger works. It is not investment advice, not a recommendation to trade any instrument, and nothing here forecasts results. Trading leveraged products carries a high risk of loss. Any historical simulation referred to is exactly that — a run over past bars under stated spread and slippage assumptions, not an indication of future performance.