Commands in the channel

A signal can be managed right from the channel, without opening the bot. A command is published as a reply to the signal post — that is how the bot knows which signal it refers to. The changes are applied to all subscriber trades of that signal.

How it works

Commands work for anyone who can publish posts in the channel: Telegram does not tell the bot which of the admins wrote the message. The only signal management command that does not need a reply to a post is /close_all_signals.

Command	Action	The bot's reply in the channel
/close — or simply the word close, cancel, exit as a reply to the post	Close the signal: subscriber trades are cancelled, open positions are closed at market	“⛔ Signal closed by the channel admin. Closing subscriber trades: 12. Open positions are closed at market.”
/change_sl_to_83500	New stop-loss price	“✏️ Stop-loss: new price 83500. Applying to subscriber trades: 10, skipped: 2 (target already filled or violates rules for a specific trade).”
/change_tp1_to_87500	New price of take-profit #1 (tp2, tp3 … for the rest)	“✏️ Take-profit #1: new price 87500. Applying to subscriber trades: …”
/change_entry1_to_85200	New price of entry #1 (entry2 …)	“✏️ Entry #1: new price 85200. Applying to subscriber trades: …”
/close_all_signals (no reply to a post)	Close all active signals of the channel	“⛔ All channel signals closed by the admin: 3 signals, 25 subscriber trades.”

The numbers of targets and entries follow the order in the signal text: the first target is tp1, the second is tp2.

Rules and fine points

• The price in a command is a number with a dot or a comma: /change_tp1_to_0.545, /change_entry2_to_56,4. Case does not matter. The command text is exactly as in the table: without @botname and without any text after the number.
• “Skipped” are the trades where the change does not apply: the target is already filled, or the new price breaks the rule SL < entry < TP (the other way round for a short) for that subscriber's particular entry price. Such trades stay as they were.
• A stop exactly at a subscriber's entry price also ends up in “skipped” — the rule is strict. To move a stop to breakeven, set it slightly below the entry for LONG or slightly above it for SHORT.
• Changing the levels also changes the tracked signal: channel notifications and statistics are counted by the new prices from then on.
• /close closes subscriber trades at market — this is irreversible. If your idea ended before the targets (you exited manually, or by time), close the signal with /close, otherwise subscribers' positions will keep hanging until a take-profit or the stop.
• Service posts (commands and the bot's replies) do not interfere with parsing the next signals — they start with / and are not parsed.
• /activate and /deactivate are also commands in the channel and need no reply to a post; they turn the processing of new posts on and off and do not touch open signals (Connecting a channel).

Example

A signal: entry 85000, targets 87000 and 88500, stop 82900. The price reached 87000 and the first target filled for some subscribers. You move the stop to breakeven: /change_sl_to_84990 as a reply to the post. The bot answers: “✏️ Stop-loss: new price 84990. Applying to subscriber trades: 10, skipped: 2…”. Two trades were skipped where the subscriber's entry filled at 84990 or lower — for them the new stop would break the rule.

Common mistakes and what the bot says

• “Signal management commands must be sent as a REPLY to the signal post. Available commands: /close — close the signal… /change_sl_to_56780… /change_tp1_to_56780… /change_entry1_to_56780… /close_all_signals…” — the command was sent as an ordinary post, not as a reply.
• “There is no active signal or subscriber trades for this post. Commands only apply to active signals.” — the reply was not to a signal post, or the signal is already finished or closed.
• “Could not parse the command. Examples: /change_sl_to_56780 /change_tp1_to_0.545 /change_entry2_to_56,4” — a typo in the command or extra text after the number.
• “⛔ Signal closed by the channel admin. There were no active subscriber trades for it.” — the signal was closed and no subscriber had a trade on it.
• “No active signals in this channel — nothing to close.” — /close_all_signals with an empty list.

All the same actions are available as buttons in the admin cabinet — the result is identical.