How to Use AI Playbooks to Automate Your Trading Alerts (+330% MFE Setups)
Turn your best small-cap setups into automated alerts. A trader's guide to building multi-step AI playbooks that flag runners like LHAI's +330% MFE before they run.
Most traders miss the move because they were looking at the wrong chart at the wrong second. An AI playbook fixes that: you encode the exact conditions of a setup once, and the platform watches all 2,500+ scanner tickers for you, firing an alert the moment price, volume, and structure line up. This guide teaches you how to turn a repeatable setup into an automated alert chain — using real runners from last week (Jun 29–Jul 03) as the worked examples.
TLDR
- An AI playbook is a multi-step setup (historical context → setup → trigger → entry → exit), each step on its own timeframe, that live-matches against every scanner ticker and fires an alert on a match.
- Last week (Jun 29–Jul 03) was runner-heavy: 26 runners closed up 50%+, 5 topped 100%, versus a 4-week baseline of ~6.8 runners/week — the exact backdrop a well-built alert harvests.
- Worked example #1: LHAI ran +143.8% close-to-close ($0.65 → $1.58) on 338.2M shares. On July 1 its true low-to-high MFE was +330.3% — an alert on the volume trigger put you in front of it.
- Worked example #2: CLRO printed a +208.3% intraday MFE (low $3.12 to high $9.62) on July 2 into a merger announcement — a filing-plus-volume playbook flagged the ignition.
- The pitfall: alerts without cooldowns and without an exit step turn into noise. You build the whole chain, not just the entry ping.
What Is an AI Playbook and Why Automate Alerts?
An AI playbook is a saved, multi-step definition of a trade setup that the platform monitors in real time and alerts you on when a live ticker matches every step. Instead of eyeballing 2,500 symbols, you describe the setup once — historical context, the base, the trigger, the entry, and the exit — and the AI Playbook Builder does the watching.
The reason to automate is simple: small-cap ignitions happen on a clock you can't beat manually. LHAI traded 338.2M shares on July 1 — its full-day range ran from $0.66 to a day high of $3.24, and the regular-session high tagged $2.84 before it closed at $2.74 (+50.5% on the day). That entire expansion happened inside a single session. If you were scrolling a watchlist by hand, you saw it after the fact. An alert tied to the volume-and-price trigger reaches you while the move is still forming.
Each playbook step carries its own timeframe, which is what separates it from a single scanner filter. A scanner filter is a snapshot — "show me everything over 5x RVOL right now." A playbook is a sequence — "the daily chart shows a multi-week base (historical context), the stock is basing above a level on the 15-minute (setup), then it breaks that level on rising volume on the 1-minute (trigger)." The platform tracks that progression per ticker and only pings you when the sequence completes. When a live ticker matches, a star indicator appears next to it in the SNACS scanner so you get both the push alert and the visual on the stream.
This matters more in a runner-heavy tape. Last week produced 26 runners that closed up 50%+, with 5 clearing 100% and one clearing 200% — against a four-week baseline of roughly 6.8 runners of 50%+ per week. When the tape is running that hot, the constraint isn't finding candidates, it's reacting to them in time. Automation is the reaction layer.
The macro backdrop supports leaning into small-cap setups right now. The Russell 2000 (IWM) closed at $298.90, just -1.3% from its 52-week high of $302.72, and the platform's macro call is Small-Cap Leadership — small caps outperforming large caps, which is the condition under which squeezes follow through. For contrast, the S&P 500 (SPY) sat at $751.28 (-1.2% from its 52-week high) and the Nasdaq 100 (QQQ) at $722.82 (-3.5% from its high). When the small-cap proxy is leading, your low-float alerts have more fuel.
How Do You Build a Multi-Step Playbook Alert?
You build a playbook by defining five sequential steps — historical context, setup, trigger, entry, and exit — each on the timeframe where that condition actually reads. Below is the anatomy, mapped to how last week's runners actually behaved.
| Step | Timeframe | What it encodes | LHAI July 1 example |
|---|---|---|---|
| Historical context | Daily | The regime/base the move launches from | Real Estate rotating in (sector RVOL 1.38 → 12.45, +800%) |
| Setup | 15m | Price coiling above a reclaim level | Basing off the prior close before the volume surge |
| Trigger | 1m | Volume + price expansion | 338.2M shares, 1430.7x average daily volume |
| Entry | 1m/5m | The confirmation candle | Break of the pre-market high ($2.01) into the open |
| Exit | 5m/15m | Target and stop | Day high $3.24; MKT close $2.74 |
The trigger step is where the alert actually fires, and it's the step most worth getting precise. LHAI's trigger wasn't the price — it was the volume. At 1430.7x its average daily volume, the relative-volume expansion preceded the bulk of the price move. That's the whole thesis behind RVOL as the number-one scanner filter: unusual volume is the earliest honest signal that a catalyst is live. Encode the trigger as an RVOL threshold plus a break of a session level, and the alert reaches you at ignition rather than at exhaustion.
The platform ships templates you can clone and modify rather than building from a blank canvas: First Green Day, Bull Trap Reversal, and Capitulation Bounce. First Green Day is the natural fit for the LHAI-style setup — a stock that has been dead reclaiming a level on its first real volume day. You clone the template, set your RVOL and price thresholds, draw the reclaim level, and save it. From that point the playbook live-matches every scanner ticker.
Alert channels are configurable per playbook: in-app, email, and SMS, each with its own cooldown. The cooldown is not optional housekeeping — it's the difference between a usable alert and a firehose. More on that in the pitfalls section.

Worked Example: LHAI's +330% MFE and the Alert That Caught It
LHAI is the cleanest illustration of why the trigger step is a volume condition, not a price condition. Over four sessions (Jun 30, Jul 1, Jul 2, Jul 6) it ran +143.8% close-to-close, from $0.65 to $1.58, on 338.2M shares at peak — a multi-day runner that opened the stretch at $0.72 and closed it at $1.58 (+120.4% on the multi-day measure).
The single most important number is the July 1 session: a true low-to-high MFE of +330.3%. The regular session opened at $1.82, ran to a high of $2.84, dipped to $1.26, and closed at $2.74 — but the full-day range spanned $0.66 to a day high of $3.24 across all sessions. A trader who was alerted at the volume trigger and rode even a fraction of that expansion had a defined, tradeable move. On a $10,000 base, capturing the full +330.3% MFE would have returned $33,030 in favorable excursion; the more realistic open-to-close portion (open $1.82 to close $2.74, +50.5%) captured $5,050.
The catalyst was documented: Linkhome Holdings completed its acquisition of Mortgage One Group and launched a GPU financing business (8-K filing, July 2), with the press release hitting July 1. That's the historical-context step doing its job — the sector was rotating in (Real Estate RVOL surged +800% week-over-week) and the ticker had a real corporate event, not a rumor. For the deeper structural context on this name, the weekly playbook covering LHAI's Computer Equipment rotation walks the multi-day arc.
How you would have caught it before it ran: an alert built on RVOL ≥ 5x, price under $3, and a break of the pre-market high ($2.01) would have fired as the regular session opened at $1.82 and pushed through prior levels on 1430.7x average volume. The volume was the tell — it expanded before the price completed its range. That's the pattern behind every high-volume breakout the platform tracks: 154 high-volume breakout setups (100M+ shares traded intraday) have triggered over the trailing window and every one hit its target — 100% follow-through, with 6 firing this week against a 90-day weekly average of 34.9.
Worked Example: CLRO's Filing-Plus-Volume Playbook
CLRO shows how you combine a filing trigger with a volume trigger in one playbook, and it printed a +208.3% intraday MFE to prove it. On July 2, ClearOne traded 87.4M shares at 7910.7x average daily volume — its regular session opened at $3.60, ran to a high of $9.62, held a low of $3.12, and closed at $6.29 (+74.7% on the day), with an after-hours close of $7.80. The low-to-high MFE was +208.3%.
The driver was a corporate event, not earnings: ClearOne announced entry into a merger agreement with Cortigent, Inc., a wholly-owned subsidiary of Vivani Medical (8-K filing, July 6; merger press release July 2). This is exactly why small-cap earnings are a weak catalyst but filings are a strong one — a merger agreement reprices the equity in a way a quarterly number never does. A playbook that watches for an 8-K on a low-float name and confirms with an RVOL spike gives you two independent confirmations before you commit.
On a $10,000 base, CLRO's +208.3% MFE represented $20,830 of favorable excursion from the $3.12 low to the $9.62 high. The open-to-close portion (open $3.60 to close $6.29, +74.7%) captured $7,470. Reading the filing chain ahead of these moves is a skill in itself — the guide to reading SEC filings for day trading covers how to spot the 8-K before the volume confirms it.

The merger-plus-volume combination is the highest-conviction version of the playbook because the two steps validate different things. The filing tells you why the stock should move; the volume tells you the market agrees and is acting now. When both fire, you're not guessing at a catalyst — you have the document and the tape.
Common Pitfalls That Turn Alerts Into Noise
The fastest way to ruin a good playbook is to fire the entry alert and forget the exit step and the cooldown. Three mistakes account for most of the damage.
No cooldown. A volatile runner will re-trigger your alert every time it re-crosses your level. Without a cooldown per channel, one ticker can send you a dozen SMS pings in ten minutes, and you'll silence the whole playbook out of frustration — right before the real move. Set a cooldown long enough that you get the ignition alert once, not the chop. LHAI's July 1 session swung from $1.26 to $2.84 in the regular session alone; a level-cross alert without a cooldown would have fired repeatedly through that range.
No exit step. An entry alert with no defined target or stop is half a trade. The exit step is where you encode where the move is supposed to go and where your thesis is wrong. CELZ is the cautionary tale: on June 30 it opened at $2.61, ran to a high of $4.72, then collapsed to a $1.37 low and closed at $1.41 (-46.0% on the day) — despite a +492.8% low-to-high MFE across all sessions. The move was real; the give-back was brutal. A stock can offer a triple-digit MFE and still close deep red, which is the entire lesson of why red days can be green trades. Without a defined exit, the CELZ alert put you into a +492.8% excursion that reversed to -46.0% — you needed the exit step to bank it.
Trigger set too loose. If your trigger is just "price up 5%," you'll get alerted on every wiggle. Anchor the trigger to unusual volume. The point of tying it to RVOL is that volume filters out the noise moves — a 5% pop on average volume is chop; a 5% pop on 1000x volume is a catalyst. The distinction between a true breakout alert and a false ping is almost always the volume condition, which is why breakout alerts are worth defining precisely.
One more structural pitfall: don't confuse a scanner match with a playbook match. A single filter fires on a snapshot; a playbook only fires when the full sequence completes. If you find yourself getting alerted on setups that never follow through, your playbook is probably collapsed into a one-step filter — add the historical-context and setup steps back so the trigger only counts in the right regime.
How to Find and Automate These Setups in SNACS
You find these setups by pairing a saved scanner filter with a live-matching playbook, then routing the match to an alert channel with a cooldown. Here's the exact workflow.
Start in the SNACS scanner. Set RVOL to a 5x minimum, price to $0.50–$20, and sort by RVOL descending — this surfaces the highest relative-volume names first, which is where every one of last week's runners originated. Add a float filter (under 25M shares captures the low-float ignitions; five of last week's classified tickers sat in the 5–25M float band). Save that filter combination as a named preset with a color so you can recall it instantly.
Then link that saved scan to a Dynamic Watchlist — the scan-to-watchlist auto-sync. Matched tickers populate the watchlist in real time and show a colored square on the main stream, so you see new candidates the instant they qualify without re-running anything. This is the passive discovery layer.
For the active layer, open the AI Playbook Builder, clone the First Green Day template, and encode the trigger as your RVOL-plus-level-break condition. Set alert channels — in-app for when you're at the desk, SMS for when you're away — each with a cooldown. When a live ticker matches, the star indicator appears next to it in the scanner and the alert fires. That star is your confirmation that all five steps lined up, not just one filter.
Before you commit to a match, click the ticker to open the ticker details page: chart, dilution risk panel (active shelf/ATM/warrant facilities), recent news, and SEC filings — all without leaving the scanner. This is where you validate the catalyst. For CLRO you'd have seen the merger 8-K; for LHAI, the acquisition filing. The scanner's Dilution Alerts column and the SEC research dilution snapshot give you two paths to the same risk data — check whether the runner is sitting on an active offering before you size in.
Finally, close the loop in your trading journal. Its AI Insights analyze your trading patterns — best setups, worst time-of-day, and your MFE capture rate. If your journal shows you're catching the alert but only banking 20% of the available MFE, that's a trade-management problem the exit step of your playbook is supposed to solve. The alert gets you in; the journal tells you whether you're holding long enough.
Reading the Rotation Behind the Alerts
The reason to automate now is that money is visibly rotating into specific sectors, and your playbook's historical-context step should reflect it. Week-over-week average RVOL rotation showed Communications Equipment surging from 5.67 to 117.50 (+1971%), Food & Kindred Products from 1.45 to 21.46 (+1376%), Computer Equipment +1219%, and Real Estate +800%. Those are the sectors feeding the runners — CLRO sits in Communications Equipment; LHAI in Real Estate.
When a sector's RVOL expands by four figures week-over-week, capital is rotating in, and setups inside that sector have more follow-through fuel. A playbook that only fires when the ticker's sector is one of the rotating-in groups filters out isolated one-off pops. That's the historical-context step earning its keep — it turns a generic breakout alert into a rotation-aligned one.
This is the same principle behind reading volume against a fixed supply. When intraday volume exceeds the tradeable float, the move becomes mechanical — buyers competing for shares that don't exist at current prices. The float rotation breakdown shows why volume-versus-float is the condition that separates a fade from a squeeze, and it's a clean trigger condition to encode.
Conclusion: What to Watch Next Session
An AI playbook is only as good as the discipline you encode into it — the trigger anchored to volume, the exit that banks the MFE, and the cooldown that keeps the alert usable. Last week's tape rewarded automation: 26 runners of 50%+ against a ~6.8 baseline, with LHAI's +330.3% and CLRO's +208.3% MFE sessions both preceded by the volume expansion an alert would have caught.
Going into the next sessions, watch the rotating-in sectors — Communications Equipment (+1971%) and Real Estate (+800%) — for the next continuation candidates, and keep your low-float, high-RVOL playbook live-matching. The setups will come; automation is how you're in front of them instead of behind them.
FAQ
What is an AI playbook in trading?
An AI playbook is a saved, multi-step definition of a trade setup — historical context, setup, trigger, entry, and exit — that the platform monitors against every live scanner ticker and alerts you on when all steps match. Each step runs on its own timeframe, so a playbook tracks a full sequence rather than a single snapshot filter. In SNACS, a match surfaces as a star indicator next to the ticker in the scanner plus an in-app, email, or SMS alert.
How is a playbook alert different from a scanner filter?
A scanner filter fires on a single condition in the current moment ("over 5x RVOL right now"), while a playbook only fires when a multi-step sequence completes across its defined timeframes. The playbook adds historical-context and setup steps ahead of the trigger, so it filters out breakouts that happen in the wrong regime. That's why a playbook alert has fewer false positives than a raw filter ping.
What should the trigger step be based on?
The trigger should be anchored to unusual volume, not just price. LHAI's July 1 move fired at 1430.7x its average daily volume before the price completed its +330.3% MFE range — the volume expanded first. A 5% pop on average volume is chop; a 5% pop on 1000x volume is a live catalyst. Encode the trigger as an RVOL threshold plus a break of a session level.
Why do I need an exit step and a cooldown?
An exit step defines your target and stop so you bank the move instead of round-tripping it, and a cooldown prevents a volatile runner from re-firing the same alert dozens of times. CELZ offered a +492.8% MFE on June 30 but closed -46.0% — without an exit step, the alert put you into a move that fully reversed. Without a cooldown, a level-crossing runner floods your SMS and you silence the whole playbook.
How do I set up a scanner to find these setups?
In the SNACS scanner, set RVOL to 5x minimum, price to $0.50–$20, and a float filter under 25M shares, then sort by RVOL descending. Save that combination as a named preset and link it to a Dynamic Watchlist so matches auto-populate in real time. Every runner last week — LHAI, CLRO, LUCY — originated from that high-RVOL, low-float profile.
Are small-cap earnings a good catalyst to build an alert around?
No — for penny stocks and small-caps, earnings rarely move the stock, so they make a weak trigger. The catalysts that actually move these names are SEC filings (offerings, S-3, ATM, mergers), FDA actions, contract wins, insider buying, and unusual volume. CLRO's +208.3% MFE came from a merger 8-K, not an earnings report — build your alerts around filings and volume, not quarterly numbers.
How do I know if a runner is a dilution risk before I enter?
Click the ticker to open the ticker details page and check the dilution risk panel, which shows active shelf, ATM, and warrant facilities, or use the SEC research dilution snapshot for the same data. The scanner's Dilution Alerts column flags names sitting on an active offering. Validate the catalyst and the dilution overhang before sizing in — a runner on a live ATM can be sold into by the company at higher prices.
How do I know if my playbook alerts are actually working?
Check your trading journal's AI Insights, which analyze your MFE capture rate and best setups. If you're catching the alert but banking only a fraction of the available MFE, that's a trade-management gap your playbook's exit step should close. The alert gets you in on time; the journal tells you whether you're holding long enough to realize the move.