Does the Telegram bot place orders on its own?

No. A card waits for a tap. Confirm places the order at the size you chose on the broker route your account is on; Skip logs the decision and places nothing. If no tap arrives within 15 minutes the signal expires and can never be executed.

Can I confirm from the web instead of Telegram?

Yes. The same pending card sits on the dashboard. Whichever surface you tap first wins; the other one sees the result. Unlinking Telegram leaves the web cards working.

What does Sarathi send to Telegram?

Your chat id, the card text, the result after a decision, and a held notice when credits are exhausted. Never broker credentials, never your TradingView login. The webhook URL is shown once in the link confirmation, so keep the chat private.

How do I mute the cards?

There is no mute switch in Sarathi today. Pause the alert in TradingView, or unlink Telegram from Settings and keep using the web cards. Muting the chat in Telegram silences the notification, but the card still arrives and still expires.

Telegram order cards

What a Sarathi order card looks like in Telegram, what the four buttons do, how linking and unlinking work, what is never sent, and how the web mirrors it.

Updated 30 Aug 2026

Live

Telegram is where the decision happens during market hours. A TradingView alert lands on your webhook, becomes a signal, and a message with four buttons arrives in your chat with the Sarathi bot. Tap one, and the message rewrites itself with the outcome.

What arrives

One message per signal: side and symbol, the strategy label from the payload, entry, stop with its distance in points, target with its reward-to-risk multiple when sent, quantity, and two derived numbers, rupee risk and notional. The footer shows when the alert fired, when it expires, and the signal number.

LONG · BANKNIFTYORB
Entry       57,530Stop        57,400  (−130 pts)Target      57,790  (2R)Qty             30Risk        ₹3,900Notional ₹17,25,900
fired 09:20 · expires 09:35 IST · #142

Times are IST. The expiry clock is 15 minutes from arrival, the same clock the web dashboard shows. A card that reaches expiry without a tap is rewritten as Expired by a sweeper that runs every minute, and its buttons stop doing anything.

The buttons

Button	What it does	Size
Confirm	Places the order on your current broker route	1× the payload quantity
Skip	Logs a skip, places nothing	n/a
½ size	Places at half quantity, rounded to whole lots, minimum one lot	0.5×
2× size	Places at double quantity	2×

Every tap goes through the same decision path as the web. The first tap claims the signal, so a Confirm on the phone and one on the laptop a moment apart place exactly one order. A tap on an expired or already-decided card places nothing; the message keeps its final state.

After a Confirm the message is edited in place to show the fill: quantity, price, slippage against the price hint, stop, rupee risk, route and broker order id. A Skip edits it to a Skipped line; a broker rejection edits it to Rejected with the broker's note. The edited message is the record.

Multipliers are rounded to the instrument's lot size, never below one lot, so a ½ tap on a one-lot signal places one lot and a 2× tap places two.

Two commands exist: /pending re-sends every card still waiting on you, with fresh buttons, and /journal lists the last ten signals with status and fill price. Neither changes anything.

Linking

Linking ties your Telegram chat to your Sarathi account through a one-time token.

Open Settings on the web dashboard and press the Telegram button. It opens the bot with a start token attached.
Press Start. The bot stores your chat id and replies with your webhook URL for the TradingView alert.
The Settings page polls every few seconds and flips to Linked on its own.

One account per chat: linking a chat another account uses moves it. To switch Telegram accounts, unlink first and repeat.

Unlinking and muting

Unlink lives in Settings behind a confirmation. It clears the chat id; cards then land only on the web dashboard. Signals, decisions and journal are untouched.

There is no mute switch in Sarathi today. Pause the alert in TradingView, or unlink and use the web. Muting the chat inside Telegram only silences the sound; the card still arrives, still counts toward your allowance, and still expires.

What is never sent

The bot sends card text, decision results, low-credit footers and a held notice. It never sends:

Broker credentials. They are envelope-encrypted on the server and decrypted only at the moment an order is placed.
Your TradingView login. Sarathi never has it.
The raw alert body. The card carries parsed fields only.
Your webhook token in any recurring message. The held notice, sent when credits are exhausted, omits it by design.

The link confirmation shows the webhook URL once. Treat the chat as private and rotate the URL from Settings if it leaks.

Delivery, limits and cost

Sarathi sends one message per signal and one edit per decision. Telegram's Bot API allows a bot roughly 30 messages per second across all its users and returns HTTP 429 beyond that, per the Bot FAQ; one trader's alert volume is nowhere near it. Telegram can refuse edits to old messages; the journal still holds the outcome.

Each delivered card costs 2 credits beyond your monthly free allowance (30 on the free tier). Taps, expiries, fills and the journal are never metered. When credits run out, delivery continues on credit for a grace period; after that new signals are marked Held and journaled, and you get one Telegram notice per ten minutes rather than one per card. Held cards are never delivered later. Details are on pricing.

The web dashboard mirrors it

/dashboard shows the same pending cards with the same four actions, and /dashboard/journal records whether each decision came from Telegram or the web. The two surfaces are peers: receive on one, confirm on the other. The alert itself is described on the webhooks page.

Get started

Create an account, link Telegram from Settings, paste the webhook URL into a TradingView alert, and send a test alert. The paper route is on by default.