Polymarket and Kalshi alerts, delivered in seconds.

Real-time alerts are the operational core of the Rivo copy-trading workflow. A copy-trader cannot act on a whale trade they do not see, and a whale trade observed five minutes after the print is rarely actionable because the price has already moved. The alert system is engineered for end-to-end latency under fifteen seconds, with delivery to three channels that cover every device a copy-trader is likely to have access to. This page describes the alert infrastructure, the filtering logic upstream of delivery, and the channel options available.

The three alert channels

Telegram

Telegram is the primary delivery channel for most copy-traders. Messages arrive in under two seconds end to end, the channel works identically on iOS, Android, desktop, and web, and the user interface for receiving and acting on alerts is the same Telegram chat experience the user already understands. The Rivo Telegram bot, @RivoMarketsBot, links to a user account in under two minutes and immediately begins delivering qualifying alerts. For the detailed Telegram integration, see our Polymarket Telegram bot page.

Web push

Web push browser notifications are the alternative primary channel for users who prefer not to install Telegram or who want alerts to appear as desktop notifications on their computer. Web push works in Chrome, Firefox, Safari, and Edge across desktop and mobile. The user grants notification permission once at signup, and alerts arrive whenever the browser is running, including in the background.

In-app inbox

Every alert is also written to the user's in-app inbox, which is the canonical record of all delivered alerts. The inbox is accessible from the dashboard and serves as a searchable history of every trade that triggered an alert, with markdown formatting, timestamps, and links to the underlying Polymarket or Kalshi market for execution.

What qualifies a trade for an alert

Not every whale trade triggers an alert. The Rivo pipeline applies five sequential filters before an alert is generated, and the filter set is calibrated to produce a manageable daily alert volume of high-quality signals.

The first filter is the size threshold. Only large opening positions clear this gate. Trades below the threshold are recorded in the whale-events table for backfill analysis but are not surfaced as alerts.

The second filter is the position-delta classification. Only opens, adds, and flips are eligible for alerting. Trims and closes are recorded but not alerted, because they represent profit-taking and risk management rather than new directional views.

The third filter is the contested-outcome check. Trades on contracts where the YES price is above 0.75 are excluded as effectively decided. The remaining contested-outcome trades are where the bulk of copy-trading edge lives, because the asymmetric payouts on extreme-price entries reward the trader disproportionately when the call is correct.

The fourth filter is the book-depth check. The order book on the trade's market must have sufficient depth to support a proportional copy-trade within two cents of the whale's executed price. Trades on books too thin to support the executed size are filtered out as fake-whale activity on illiquid markets.

The fifth filter is the AI quality judge. Trades that clear the four deterministic filters above pass to an AI judge that evaluates the market title, category, current price, and trade context, and produces a send-or-skip decision. The judge is the final gate before an alert is generated. Approximately one in twenty whale-sized trades clears all five filters.

Latency and reliability

The end-to-end latency budget for alerts is fifteen seconds, measured from the moment the underlying trade prints on Polymarket or Kalshi to the moment the notification arrives on the user's device. The budget breaks down approximately as follows: platform polling delay (three to ten seconds), normalization and filtering (under one second), AI judge processing (two to five seconds), channel delivery (under one second). Telegram and web push are sub-second on the delivery step; the in-app inbox write is also sub-second.

Reliability is maintained through the underlying Redis Streams infrastructure with consumer groups. Each consumer group processes the unified event stream independently, with automatic retry on failure and at- least-once delivery guarantees. A momentary downstream outage does not lose alerts; the events remain in the stream until acknowledged.

Alert customization

Each user can configure alert preferences from the dashboard. The available filters include:

• Category: politics, sports, crypto, macro, culture, and other. Each category can be independently enabled or disabled.
• Platform: Polymarket only, Kalshi only, or both.
• Minimum trade size: any value at or above our default whale threshold. Users who want a more selective feed can raise the floor.
• Channel selection: any combination of Telegram, web push, and in-app inbox.
• Quiet hours: optional time windows during which alerts are suppressed and queued for delivery at the next active period.

The filter configuration is applied uniformly across all enabled channels. A category disabled in one channel is disabled across all channels for that user.

What an alert looks like in practice

A typical Polymarket alert reads as follows: "Polymarket whale opened $42,000 YES at $0.18 on 'Will [event] happen by [date]'. Politics. Wallet has 47 resolved positions, positive PnL in politics. Headline: contested entry at long-tail price, sharp wallet history."

A typical Kalshi alert reads as follows: "Kalshi whale opened $18,500 NO at $0.62 on 'September CPI prints above consensus'. Macro. Wallet has 122 resolved positions, positive PnL in macro. Headline: contested entry, wallet shows consistent macro alpha."

Each alert is concise enough to read at a glance, with enough context to decide whether to copy the trade without leaving the notification. A link to the underlying market is included for one-click navigation to execute the position in the user's own Polymarket or Kalshi account.

What to read next

For the broader copy-trading framework, see our copy-trading prediction markets guide. For the underlying whale-tracking infrastructure, see our Polymarket whale tracker page. For the specific Telegram integration, see our Polymarket Telegram bot page.

Frequently asked questions