> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/telegram.md).

# Telegram

Telegram is TradeSurge's second control surface. It will send breach, fill and recap alerts, with trading from Telegram to follow.

Telegram is a second surface on the same engine as the web app. It will bring breach warnings, fills and daily recaps to your phone without opening a browser. Because both surfaces talk to one engine, what you see in Telegram will always match the app.

{% hint style="info" %}
**Coming soon.** Pairing and alerts open with the alpha. Trading from Telegram, including the kill switch, follows later.
{% endhint %}

## What Telegram will do first

* **Breach alerts** when an account nears or crosses a firm limit.
* **Fill alerts** when an order fills or a position changes.
* **Recaps** at the end of a session, in R.

## What comes after

* Placing and closing trades from chat, with the same confirm step as the Terminal.
* The kill switch from Telegram, so you can flatten everything from your phone.

## Pairing starts on the web

You link Telegram from your signed-in web session, never the other way round. This keeps your Telegram account tied to a verified TradeSurge login.

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Pair Telegram</strong></td><td>Link your account in under a minute.</td><td><a href="/platform/telegram/pair-telegram.md">Pair Telegram</a></td></tr><tr><td><strong>Alerts reference</strong></td><td>Every alert and what it means.</td><td><a href="/platform/telegram/alerts.md">Alerts reference</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tradesurge.co/platform/telegram.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.