> For the complete documentation index, see [llms.txt](https://docs.kai.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kai.finance/vaults/liquidity-provider-vaults/telegram-notifications.md).

# Telegram Notifications

Kai Finance's Telegram notification system ensures you stay informed about your LP positions in real-time through alerts sent by the Kai Finance Bot. 

Follow this [step-by-step guide](/vaults/liquidity-provider-vaults/how-to-connect-telegram.md) to link your Telegram account with Kai Finance and start receiving timely notifications.

These notifications cover four critical areas: Deleverage, Liquidation, Range Alerts, and Health Status.

### 1. Deleverage Notifications

Alerts you when your position is deleveraged.

**Example**: *"Your position SUI-USDC \[0x123...abc] has been deleveraged on 29th Nov 12:22"*

### 2. Liquidation Notifications

Notifies you when your position is liquidated.

**Example**: *"Your position SUI-USDC \[0x123...abc] was liquidated on 29th Nov 12:22"*

### 3. Range Alerts Notifications

Sends alerts about your position's range status. You will receive two types of notifications:

* Warning alert
  * When your position reaches a 90:10 ratio (10% from range boundary)
  * Helps you take proactive action before going completely out of range
  * **Example**: *"Your position USDT-USDC \[0x123...abc] is almost out of range. Current price is 1.0003551 USDC per USDT"*
* Out of range alert:
  * When your position exits the range completely
  * **Example**: *"Your position USDT-USDC \[0x123...abc] is out of range. Current price is 1.0003551 USDC per USDT"*

Notification Rules:

* For each type of alert, you will receive one notification when the condition is first met
* If the position returns to range and triggers the same condition again within 12 hours, you will not receive a new alert
* After the 12-hour cooldown period, new alerts can be sent if conditions are met again

### 4. Health status notifications

Health status alerts keep you informed about the health of your positions and help mitigate liquidation risks.

#### Warning Alert (80%)

* **Trigger**: Health drops below 80%.
* **Notification Frequency**: One-time notification.
* **Example**: *"WARNING: Your position USDT-USDC \[0x123...abc] health has dropped below 80% (current: 63.40%)"*

#### Critical Alert (50%)

* **Trigger**: Health drops below 50%.
* **Notification Frequency**: One-time notification.
* **Example**: *"CRITICAL: Your position USDT-USDC \[0x123...abc] health has dropped below 50% (current: 23.26%)"*
  * **Note**: Positions with health below 50% are at a higher risk of liquidation.

#### Recovery

* **Trigger**: Health improves above 80%.
* **Cooldown**: A **12-hour cooldown** period starts once the health goes above 80%.
  * During this period, you will not receive new notifications unless the health drops again after 12 hours.

This system helps prevent excessive notifications while keeping you informed of critical changes in your LP positions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kai.finance/vaults/liquidity-provider-vaults/telegram-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.