Alert Intel
Build custom multi-condition alerts that notify you when up to 3 conditions across 7 analytical engines are simultaneously displayed. Configure filters for study workflows, such as session context, volume readings, or pattern labels; notifications are informational and do not constitute trade triggers.
What this page covers
- How to build an alert from scratch with multi-condition logic
- The 7 source engines and what conditions each provides
- How to configure Telegram and web push delivery
- Strategies for avoiding alert fatigue while staying informed
Why Multi-Condition Alerts?
Single-condition alerts can produce more notifications. Adding conditions narrows the displayed set; the resulting count and relevance depend on the selected pair, timeframe, data, and filters.
Alert Intel helps learners revisit combinations of model readings. Three conditions appearing together are a data point to inspect, not proof that an event is significant or a reason to act.
The 7 Source Engines
| Engine | Available conditions | Typical use case |
|---|---|---|
| Kill Zone | Window active (London-NY / NY Midday), window approaching (N minutes), session bias (bullish/bearish) | Timing-based triggers for any strategy tied to session windows |
| Volume | Configurable IIS score filter, smart pattern detected (absorption/climax/breakout), MTF comparison | Review volume readings on specific pairs |
| Wyckoff | Phase detected (accumulation/markup/distribution/markdown), configurable WPS filter, specific event (Spring/SOS/UTAD/SOW) | Review phase labels and events |
| Reversal | Divergence confirmed (regular/hidden), RSI divergence, MACD divergence, momentum exhaustion signal | Counter-trend setups at key levels |
| Sweep | Sweep detected, configurable score filter, cluster sweep, sweep at HTF level | Review modeled liquidity events |
| Breakout | Structure break (BOS), level break (S/R), high/low breakout, range breakout with volume | Review structural changes |
| Pattern | Pattern completion (any or specific type), configurable confidence filter, MTF stacked pattern, harmonic at PRZ | Review pattern classifications |
Building an Alert — Step by Step
- Go to Alert Intel
Click 'Alert Intel' in the sidebar under Tools.
- Click 'New Alert'
Opens the alert builder modal.
- Name your alert
Use a descriptive name you'll recognize in Telegram DMs — e.g. 'XAUUSD Kill Zone + Sweep Combo'.
- Select pairs
Choose which pair(s) this alert monitors. You can select multiple pairs — the alert fires when any of them meet the conditions.
- Add Condition 1
Select the source engine and configure the specific condition. Example: Engine = Kill Zone, Condition = 'Window active (London-NY)'.
- Add Condition 2
Click '+ Add Condition'. All conditions use AND logic and must be displayed together for the notification. Example: Engine = Sweep, Condition = 'Sweep detected'.
- Add Condition 3 (optional)
Add a third study filter if useful. Example: Engine = Volume, Condition = 'IIS reading displayed'.
- Configure delivery
Toggle: In-app notification, Telegram DM, Browser push. All three can be active simultaneously.
- Set cooldown
To prevent the same alert firing repeatedly, set a cooldown period: 15 minutes, 1 hour, 4 hours, or 24 hours. After an alert fires, it will not fire again until the cooldown expires.
- Save and activate
Click 'Save Alert'. The alert is immediately active and monitoring your selected pairs.
Example Alert Configurations
// Alert 1: XAUUSD Institutional Sweep Entry
Pairs: XAUUSD
Condition 1: Kill Zone = Active (any window)
Condition 2: Sweep = Detected, score > 75
Condition 3: Volume = IIS > 70
Delivery: Telegram + Push | Cooldown: 4H
// Alert 2: Wyckoff Spring Alert (any pair)
Pairs: EURUSD, GBPUSD, USDJPY, XAUUSD
Condition 1: Wyckoff = Event detected (Spring)
Condition 2: Volume = Smart pattern = Absorption
Delivery: Telegram only | Cooldown: 24H
// Alert 3: High-Confluence Pattern Completion
Pairs: All watchlist pairs
Condition 1: Pattern = Completion, confidence > 80
Condition 2: Pattern = MTF stacked (2+ timeframes)
Delivery: In-app only | Cooldown: 1H
Managing Your Alerts
The Alert Intel dashboard shows all your active alerts, their current status, and the last 7 days of trigger history. Key management actions:
- Pause an alert — stops monitoring without deleting the configuration
- Edit an alert — modify conditions, pairs, or delivery settings in place
- View trigger history — see every time an alert fired in the past 7 days, with the market context at the time of each trigger
- Duplicate an alert — copy an existing alert as a template for a new one
- Archive an alert — remove it from the active list but preserve the configuration for future use
Frequently asked questions
Can I create more than 3 conditions per alert?
No — the maximum is 3 conditions per alert. This is intentional: more conditions make the alert fire so rarely it loses utility. If you need more specificity, create a separate alert and use the cooldown system to manage overlap.
Does Alert Intel work when the Hanzo AI tab is closed?
Browser push notifications work when the tab is closed as long as your browser is running. Telegram DMs work regardless of browser or app status — they arrive on your phone even if you haven't opened Hanzo AI in days.
How many active alerts can I have at once?
Active-alert limits vary by access path. Review the current in-app limit before creating a new alert; paused alerts may be treated differently.
What's a 'cooldown' and when should I use it?
Cooldown prevents the same alert from firing again within a set window (15 min / 1 hour / 4 hours / 24 hours / session). Use it for high-frequency signal types like Kill Zone or Volume Anomaly where the same condition can trigger repeatedly within minutes. Without a cooldown, you may receive 10 alerts for the same ongoing condition.
Can I set an alert that triggers when price reaches a specific level?
Not directly — Alert Intel is condition-based (engine signals, not price levels). For price level alerts, use the standard price alert in the Kill Zone Panel or Intelligence Feed. Alert Intel is designed for multi-engine confluence triggers — it fires when two or three analytical engines simultaneously detect qualifying events.