> 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/alerts.md).

# Alerts reference

TradeSurge will send three kinds of alert. Breach alerts cannot be muted. Fill and recap alerts can.

TradeSurge will send three kinds of alert to Telegram. Each one is in R, never in dollars. Breach alerts are always on, because they protect money.

{% hint style="info" %}
**Coming soon.** Alerts open with the alpha, once your Telegram is paired.
{% endhint %}

## The three alerts

| Name       | What it means                                                                                                                |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Breach** | An account is near or past a firm limit. Shows the rule, the current value and the limit. On by default and cannot be muted. |
| **Fill**   | An entry or exit filled, or a position changed. On by default. Can be muted.                                                 |
| **Recap**  | An end-of-session summary of your results in R. Off by default. Can be turned on.                                            |

## Breach alerts cannot be muted

A breach alert means money is at risk. It is the one alert you cannot switch off. Breach Guard sends it when an account crosses its safety margin.

## One alert per event

TradeSurge aims to send one alert per event.

## Alerts never slow down trading

Alerts are composed after the fact. A failed alert never blocks or delays an order.

## 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>Breach Guard</strong></td><td>What happens when a limit gets close.</td><td><a href="/platform/risk/breach-guard.md">Breach Guard</a></td></tr><tr><td><strong>Pair Telegram</strong></td><td>Link your account.</td><td><a href="/platform/telegram/pair-telegram.md">Pair Telegram</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/alerts.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.