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

# Use Telegram controls and alerts

> View ANSIO accounts and alerts in Telegram, understand Manager and Client access, confirm supported strategy actions and manage reminders without stopping bots.

Telegram gives authorized users account views and alerts. Managers can also prepare supported strategy actions, which require a separate confirmation.

## Access

The owner authorizes a Telegram user in **Alerts → Telegram**, with Manager or Client scope. A Client sees the assigned client's read-only status, balances and book.

The owner can separately enable **Ask Autopilot** for questions. It does not grant trading permission.

For the Telegram Mini App, sign in to the ANSIO team account and use **Sections → Telegram access → Link this Telegram**. After linking, **Continue with Telegram** is available.

![ANSIO Telegram menu and an Autopilot task with its completed result.](https://mintcdn.com/ansio/TbUlSsAFRzZei_af/images/docs/telegram-autopilot.png?fit=max\&auto=format\&n=TbUlSsAFRzZei_af\&q=85\&s=6dba9834d9da558db83303d0ee69447d)

The Telegram screenshot used on the ANSIO landing page. The final task card records the affected account, changed fields and result.

## Commands

Replace `NAME` with the client name. If several accounts match, select the exchange shown in the response.

| Command | Purpose |
| - | - |
| `/start` or `/home` | Open the menu. |
| `/help` or `/faq` | Read help. |
| `/clients` · `/client NAME` | Find a client and its accounts. |
| `/bots` · `/running` · `/exited` | View strategy status. |
| `/balances NAME` · `/book NAME` | Read balances or the book. |
| `/changes NAME` | Read account changes with Manager access. |
| `/autopilot NAME` | Open the client's Autopilot view. |
| `/alerts` · `/health` | View alerts or connection health with permitted access. |

`/ask` is available when the owner enables questions. Manager `/askcontrol` can prepare supported Start, Stop or Restart actions; it still requires confirmation.

## Confirm a strategy action

**1. Select the strategy**

Open **Clients → account → Strategy controls → strategy**.

**2. Read the preview**

Confirm the account, strategy and intended action.

**3. Use Yes, execute**

The confirmation is single-use and expires after two minutes. Changed settings require a new preview.

**4. Read the result**

Accepted means the request was received. Wait for the execution result before deciding whether another action is needed.

## Alerts and reminders

**Acknowledge / Ack** records that you saw the incident. It does not stop reminders. **Snooze 10m / 1h** postpones notifications for that incident. Neither action fixes the condition or stops the bot.

Default repeats are **10 minutes for Critical**, **20 minutes for High**, and **60 minutes for Medium or Low**. A personal rule interval overrides the default; **0** disables ordinary repeats.

The rule's first-alert wait is separate. Delivery also respects the recipient's schedule, timezone, severity preference and vacation pause.

![ANSIO Telegram alert, resolved state and Acknowledge and Snooze controls.](https://mintcdn.com/ansio/TbUlSsAFRzZei_af/images/docs/telegram-alerts.png?fit=max\&auto=format\&n=TbUlSsAFRzZei_af\&q=85\&s=2f07035ae70ed00d3e9a0070a190d678)

Margin and quote alerts in the landing-page demonstration.

See [Alerts](https://docs.ansio.trade/alerts/overview.md) for the incident controls, [delivery settings](https://docs.ansio.trade/alerts/delivery.md) for timing and missing messages, and [the rule reference](https://docs.ansio.trade/alerts/rules.md) for each trigger.

If an execution response is uncertain, inspect current status instead of repeatedly confirming the same action. See [Connection and data issues](https://docs.ansio.trade/troubleshooting/connections.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.