Notifications & Alerts
Email, Telegram, and WhatsApp alert configuration
Predite supports four notification channels: Email, Telegram, WhatsApp, and Push (PWA). This doc covers how to configure each and design alert rules that catch what matters without spamming you.
Channels Overview
| Channel | Setup difficulty | Delivery speed | Best for |
|---|---|---|---|
| 0 minutes (default) | 10-60 sec | Detailed alerts, daily digests | |
| Telegram | 2 minutes | < 5 sec | Fast time-sensitive signals |
| 5 minutes (admin config) | 5-30 sec | Mobile-first users | |
| Push (PWA) | 1 minute | < 2 sec | Power users with PWA installed |
Active by default for all users. Configure in Settings → Notifications:
- •Toggle on/off
- •Frequency: instant, hourly digest, daily digest
- •Categories: which alert types you want emailed
Delivery via Resend. Typical latency 10-60 seconds depending on the email provider on your end (Gmail is fastest; some corporate filters add delay).
Telegram
Setup: 1. Open Telegram and search for @PrediteAlertsBot (or whichever bot is configured for your deployment). 2. Tap "Start" — the bot replies with your unique Chat ID. 3. Copy the Chat ID and paste it into Settings → Notifications → Telegram Chat ID. 4. Enable the Telegram toggle.
Behavior:
- •Each alert is sent as a Telegram message.
- •Messages include a link back to the relevant Predite page.
- •You can mute the bot in Telegram (right of header) to suppress for short periods without disabling globally.
- •The bot responds to /start, /connect, /portfolio, /signals, /whales and /help — see the Telegram Bot doc.
WhatsApp uses Twilio for delivery. Requires the deployment to have Twilio credentials configured (admin-level setup).
User setup: 1. Enter your full international number including country code in Settings → Notifications → WhatsApp Number (e.g., +5541999888777). 2. The first time we send an alert, you'll receive a WhatsApp message asking you to opt in. Reply "yes" to confirm. 3. Subsequent alerts come through normally.
Note: WhatsApp Business API has restrictions on message content. Some highly-templated messages may be delayed during their approval flow. Generally fine for trading alerts.
Push (PWA)
If you've installed Predite as a PWA (Progressive Web App) — via your browser's "Install" or "Add to home screen" — you can enable native push notifications.
Setup: 1. Install the PWA from your browser 2. Open Predite 3. Settings → Notifications → Push Notifications → Enable 4. Grant permission when the browser prompts
Push notifications work even when the browser is closed (on most platforms). Fastest delivery channel.
Alert Rules
Go to Dashboard → Alerts → New Rule. Each rule has:
Trigger — what fires the alert:
- •Edge threshold reached (e.g., "edge > 10pp on any market")
- •Specific market price crosses level (e.g., "market X reaches 75¢")
- •Volume spike (e.g., "volume > 5x normal in any market")
- •Whale activity (e.g., "any wallet > $25k buys YES")
- •News sentiment (e.g., "Fed-related headline with magnitude > 50")
- •Bot event (trade executed, error, stopped)
- •Custom (combine multiple conditions with AND/OR)
Scope — which markets the rule monitors:
- •All markets, or specific category
- •Specific market by URL/ID
- •Markets you've starred
Channels — which delivery channels to use (multiple can be selected).
Cooldown — prevents the same alert firing twice within a window:
- •Default: 60 minutes per market per rule
- •Tighten to 10 minutes if you want more frequent updates
- •Widen to 24 hours for daily-digest-style alerts
Active hours — quiet hours (don't notify between 10pm and 7am your time, for example).
Sample Alert Rules
Catch every strong signal:
- •Trigger: edge > 12pp AND confidence > 75
- •Scope: all markets
- •Channels: Telegram + email
- •Cooldown: 30 minutes per market
Whale watch:
- •Trigger: any wallet trades > $25k YES or NO
- •Scope: politics + economics categories
- •Channels: Push
- •Cooldown: 5 minutes per market (whales come in bursts)
Bot health:
- •Trigger: bot error OR bot stopped
- •Scope: all my bots
- •Channels: email + Telegram
- •Cooldown: none (always notify)
Daily digest:
- •Trigger: time of day = 8am
- •Scope: my watchlist + my open positions
- •Channels: email
- •Frequency: daily
Avoiding Notification Fatigue
The most common mistake: enabling too many rules at too-loose thresholds, getting buried in alerts, and ignoring them all.
Tips:
- •Start with 2-3 rules. Add more only after you've tuned the existing ones.
- •Use the cooldown aggressively. Same-market alerts hourly is plenty for most use cases.
- •Use scope filters. You don't care about sports markets if you only trade politics.
- •Use active hours. Trading alerts at 3am aren't actionable.
- •Tier your rules by urgency. Edge > 15pp → push. Edge > 10pp → email digest. Bot error → all channels. This way urgent things actually get attention.
Auditing Delivered Notifications
The bell in the topbar is the delivery log you actually have: it lists your most recent notifications (the latest 50) with type, severity, title and time, and marks what you have read. There is no separate history page and no per-channel delivery report — if an alert never reached Telegram, WhatsApp or e-mail, the bell will still show it, because the in-app row is written first and the external send happens after.
When an alert you expected is missing, work through this order:
- •Is it in the bell? If yes, the rule fired and only the external delivery failed — check that the channel is verified in Settings (an unverified channel is never sent to).
- •Is the channel alive? Settings has a test notification button that sends through every configured channel and reports success or failure per channel. That is the fastest way to separate "the rule never fired" from "the channel is broken".
- •Is the rule what you think it is? Open Alerts and re-read the scope: a narrower condition than you remember is the most common cause.