# Telegram operations > Run your product from Telegram. Connect a chat, use commands to check status, tasks, deployments and credits, create work in plain language and reach the Orkosi team. Source: https://support.orkosi.com/docs/telegram Everything the chat assistant can do in the dashboard, it can do in Telegram: answer questions about your product, create and track tasks, report deployment state and balance, and hand a conversation to a human. This page shows how to connect a chat and what each command does. ## Connect Telegram There are two ways to connect. Both live under **Settings → Telegram**. ### Use the Orkosi bot (recommended) 1. Open **Settings → Telegram → Chat on Telegram** and click **Connect**. 2. Orkosi shows a one-time link and code. Open the link; it starts a chat with the Orkosi bot. 3. Send `/start ` if Telegram did not fill it in for you. The chat is now bound to your account. Conversations, credits and history are shared with the dashboard assistant, so you can start a thread on your laptop and continue it on your phone. ### Bring your own bot If you prefer a bot under your own name: 1. In Telegram, talk to `@BotFather`, create a bot and copy its token. 2. Paste the token in **Settings → Telegram → Chat on Telegram → Use my own bot**. Orkosi verifies the token and stores it encrypted. 3. Open your bot and send `/start ` with the code Orkosi shows. The first chat that sends the code is bound; messages from any other chat are ignored. You can also add a list of allowed Telegram user IDs and standing instructions the assistant should follow when it answers from this bot. ## Available commands Commands are free. They never consume credits. Everything else you type goes to the assistant and is billed like a chat message (see [Billing](https://support.orkosi.com/docs/billing)). ### Check on things | Command | What it returns | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | `/status` | An overview of your account: products, open tasks, recent activity | | `/tasks` | Your tasks and their stage | | `/deploy` (or `/deploys`) | Every product and environment with its state (live, building, deploying, failed, paused) and URL | | `/credits` (or `/balance`) | Your credit balance | | `/products` (or `/apps`) | Your products | | `/analytics [7\|14\|30\|90]` | Replies, chat credits per day, tasks done versus the previous period, open tasks and live apps for the last N days | | `/tickets [open\|resolved\|all]` | Your support tickets | | `/history` | Your last ten Telegram conversations | ### Work and control | Command | What it does | | ------------------------- | -------------------------------------------------------------------------------- | | `/new` | Starts a fresh conversation with the assistant | | `/tier` | Switches the assistant between Fast and Smart; this changes what a message costs | | `/ticket ` | Opens a support ticket with your text as the first message | | `/human` (or `/escalate`) | Hands the current conversation to the Orkosi team | | `/settings` | Link to your settings | | `/help` | The command list | | `/start` | Connects the chat (used once, with the code) | Buttons under the assistant's replies trigger the same commands, so you rarely need to type them. ## Manage your product in plain language Anything that is not a command is a message to the assistant, with your account, products and recent activity as context. The assistant can act, not just answer. Examples: - "Add a dark mode toggle to the settings page" — creates a task on the right product and tells you its ID. - "What is the status of task 4123?" — reads the task and reports its stage and progress. - "Is production up?" — checks your deployments. - "Change the tagline on the landing page to 'Ship faster'" — updates the product and queues the change. - "Make me a hero image of a mountain at dawn in our brand colours" — generates an image (charged at what the image provider bills us plus our markup, like every other action). - "I think billing is broken, can someone look?" — offers to escalate to a human. Voice messages are transcribed and treated as text. Photos are acknowledged; attach them to a task from the dashboard if the agent needs to see them. Long answers are formatted for Telegram, and cards such as deploy status or ticket lists come with buttons for the next action. ## Notifications **What arrives in your Telegram chat today** - Replies from the assistant, including results of actions you asked for. - Replies from the Orkosi team after `/human` or `/ticket`, in the same thread. - Requests for input when a task needs a decision from you. **Event notifications** (task completed, task failed, deployment succeeded, agent started or failed, credits low) are delivered through **webhooks** to any HTTP endpoint you configure under **Settings → Webhooks**, including chat services that accept incoming webhooks. Forwarding these alerts straight to your Telegram chat is on the roadmap; the switch under **Settings → Notifications** is visible but not yet active. Until then, `/status`, `/tasks`, `/deploy` and `/credits` give you the same information on demand. ## Limits and safety - Messages are rate-limited per chat to protect your credit balance from runaway loops. - The assistant only acts on products your Telegram-linked account can access. - Disconnecting the chat under **Settings → Telegram** stops all messages immediately. Conversations remain in your dashboard history. - Tokens for your own bots are stored encrypted and are never shown again after saving.