Admin checklist
Everything important from this section as a list you can go through in a minute. Details are behind the links.
Before connecting
- [ ] I connect the channel from the account that will manage it — it becomes the owner, and afterwards ownership can only be transferred through support (Three bots and the channel owner).
- [ ]
/startwas pressed in @sync_trading_bot. - [ ] Spot or futures is decided: the audience knows which exchange bot to create.
- [ ] Exchange API keys are not needed for the channel — subscribers connect their own.
Connecting
- [ ] The main bot is an administrator with the Post messages and Edit messages permissions.
- [ ] The service bot from the prompt is an administrator without extra permissions.
- [ ]
/activatein the channel → “🚀 SYNC channel activated!”. - [ ] The 📢 Channel administration button appeared in the main menu, with the channel in the status “🟢 active” (Connecting a channel in three steps).
- [ ] A test signal on a liquid pair: the buttons appeared under the post; the test was closed with
/close(Checking after connection). - [ ] The test was done while subscribers have auto-trade off — otherwise real trades open.
Every signal
- [ ] A text post, not a photo caption; one signal per post.
- [ ] The only hashtag is the pair, a full ticker with the quote currency (
#BTCUSDT), and the pair exists on Bybit. - [ ] Leverage is specified (futures) or there is no leverage line at all (spot).
- [ ] Every entry and every target on its own line; numbering only with a separator after the number (
TP1: 87000, notTP1 87000). - [ ] Decimals with a dot (a comma is read too); no thousands separator like
85,000. - [ ] Exactly one stop — as a price or as a whole percentage.
- [ ] No lines with numbers inside the blocks (
TF: 5m,RR 1:2) and no lines starting withLevels,Slippage,Buy,Sell. - [ ] After a few seconds the buttons appeared under the post (Signal format).
Managing
- [ ] Level corrections go through commands as a reply to the post (
/change_sl_to_…,/change_tp1_to_…,/change_entry1_to_…) or from the cabinet, not by editing the post. - [ ] Closing goes through
/closeas a reply to the post or ⛔ Close signal in the cabinet; I remember that subscribers' positions will be closed at market. - [ ] The idea ended before the targets (I exited manually or by time) — the signal was closed with
/close, otherwise subscribers' positions hang until a take-profit or the stop. - [ ] Moving to breakeven — the stop slightly below the entry for LONG (slightly above for SHORT), not exactly at the entry (Commands in the channel).
- [ ] A new signal on the same pair in the same direction — the previous one is closed.
Regularly
- [ ] Once a week — a look at 📈 Statistics and 📥 Export history (CSV) (Channel statistics).
- [ ] Unclosed signals in 📈 Open signals are closed — otherwise in 30 days they go to ⌛ Expired with no notification.
- [ ] The private messages from the bot are read: “was not accepted as a signal” and “no trades were opened” come to the owner only.
- [ ] The bots' permissions are in place: if someone removed a bot from the administrators, processing stopped — put the bot back and send
/activate.
If something went wrong
| Symptom | Where to look |
|---|---|
| No buttons under the post and nothing in private messages | The post has no text, or the channel is not activated |
| No buttons, but subscribers are trading | No Edit messages permission |
| The bot does not post in the channel | No Post messages permission |
| “signal … was recognized as SPOT…” | Leverage was forgotten |
| Take-profit 187000 instead of 87000 | A number without a separator stuck to the price |
| Only one target out of three was taken | The targets were on one line separated by / |
| “There is no active signal or subscriber trades for this post…” | The reply was not to a signal post, or the signal is finished |
| No 📢 Channel administration button | You are not the owner — changing it goes through support |
| “No service bot is available right now” | Write to support |
