Connecting Telegram

There is nothing to install. You open a chat with one of our bots, send it a message, and your account exists from that moment. Linking it to a risbot.io account comes later, and only trading needs it.

The only step that needs care is the first one, and it is the one that has nothing to do with this bot: making sure the chat you have opened is ours.

Check the bot before you type anything into it

Anyone can create a Telegram bot, and nothing on Telegram reserves our name. A convincing copy can carry our wording, our panels and a link that says "verified" - and it will ask you for the same API key the real one does.

risbot.io/verify lists every bot we run. It is the only list we publish, and it is complete: a bot that is not on it is not ours. Type risbot.io into your browser yourself rather than following a link from the chat you are checking - that is the whole point of the list living on the website.

Checking a Bot Is Ours has the full procedure, including what a retired bot looks like and what we will never ask you for.

What our bots are called

Usernames are a star name and risbot - @rigel_risbot, @mizar_risbot. Telegram requires a bot username to end in bot, and risbot already does, so there is no second bot on the end and there are no numbered bots: @risbot_1_bot is not one of ours.

The display name your chat list shows is the same star, capitalised: Rigel Risbot for @rigel_risbot. That is why the names differ at all - a chat list shows display names, and calling every one of them Risbot would leave anyone holding two of ours unable to tell them apart. They are otherwise identical: one bot serves many people, and which of them you use changes nothing about what it can do.

Send /start

/start opens the main menu. This is what a first-time account sees:

Your account was created by that message. Unprepared 🟠 is the normal first state, and the lines under it say why: no Risbot account is linked to this Telegram one yet, and no exchange key is on the bot. The warning at the bottom names the first thing to do. Neither stops you looking around - every button on the menu already opens. See The Main Menu for what each line means and what each button does.

/main opens the same menu later. Every panel also has its own command, and Telegram's / menu lists them all, so /settings, /sniper or /positions jumps straight to a screen without walking back through the menu.

The chat is a control panel, not a conversation

Two behaviours surprise people on the first day, and both are deliberate:

• Your command disappears. The bot deletes the message you sent and opens the panel in its place, so the chat stays one live screen instead of a scroll of old menus.
• Ordinary messages get no reply, and are kept. Anything that is not a command, and not an answer to something the bot asked for, is deleted from the chat - and before it goes, the text is stored on our side along with your Telegram user id, username, name and language. Nothing is sent back, so there is no sign this happened. Saying hello does nothing at all - it is not ignoring you, it is that the bot has no conversation to have.

When the bot does want something typed - a price, a password - it asks with a prompt you reply to, and it deletes both the prompt and your answer as soon as it has read them.

One account per bot

Your account is keyed to the bot you messaged, not to you alone. Messaging a second one of our bots gives you a second, entirely separate account on it: its own settings, its own risk rules, its own exchange connection and its own history. Nothing is shared between the two.

That is occasionally useful - two bots is how you would run two Bybit accounts, since one exchange account can only be linked to one bot. It is a surprise if you did it by accident, wondering where your settings went.

If your bot is retired

A bot we replace tells you so, and points at the one that took over:

That message is accurate: your account follows the slot the bot occupied, not the bot itself, so the replacement opens on the same settings, the same history and the same exchange connection. A retired bot stays on the verification list, marked retired, and still answers a message with the same pointer - so "retired" is a safe answer, and absent from the list is the warning sign.

Next

Connecting Your Exchange - the API key to create, the permissions it needs, and what the bot checks before it accepts one.