> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jupiclick.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Telegram bot

<Frame>
  <img alt="Tg Bot" lightAlt="Tg Bot" darkAlt="Tg Bot" src="https://mintcdn.com/jupiclick/ModJgoi_7YymZlS_/images/tg_bot_w-4.png?fit=max&auto=format&n=ModJgoi_7YymZlS_&q=85&s=48b7e70a87d04a02248ee488ffbfbd79" className="dark:hidden" width="2400" height="1350" data-path="images/tg_bot_w-4.png" />

  <img alt="Tg Bot" lightAlt="Tg Bot" darkAlt="Tg Bot" src="https://mintcdn.com/jupiclick/pyZWRG4jhQGaoldT/images/tg_bot-3.png?fit=max&auto=format&n=pyZWRG4jhQGaoldT&q=85&s=3397efa1300a21064990bffcd49d375c" className="hidden dark:block" width="2400" height="1350" data-path="images/tg_bot-3.png" />
</Frame>

The **JupiClick Telegram bot** lets you trade on Solana directly from Telegram - no browser, no extension, no extra setup. Open a chat, send a command, and execute trades from any device where you run Telegram.

Use the bot when you want to:

* Trade on the go without leaving Telegram
* React quickly to market moves from your phone
* Manage multiple wallets and fire one-click buys and sells
* Route orders through [smart transaction routes](/smart-transaction-routes) for better fills

## Get started

<Steps>
  <Step title="Open the bot">
    Start a chat with [@JupiClickBot](https://t.me/JupiClickBot) on Telegram.
  </Step>

  <Step title="Create or import a wallet">
    Follow the in-chat prompts to generate a new Solana wallet or import an existing one. Back up your seed phrase before you deposit funds.
  </Step>

  <Step title="Fund your wallet">
    Send SOL to the deposit address shown in the bot to cover trades and network fees.
  </Step>

  <Step title="Make your first trade">
    Paste a token address or use an in-bot command to buy or sell. The bot quotes the price, shows the route, and confirms the transaction.
  </Step>
</Steps>

<Tip>
  Prefer trading from a desktop browser? Try the [Chrome extension](/chrome-extension) instead.
</Tip>