Trigger Monitor
Trigger Monitor watches the public regulatory record for events that change the priority of an advisor on your distribution list. When a filing crosses a threshold that matters to your firm, the agent quietly lifts the priority of the affected advisors so they rise to the top of your sales workspace the next time you look.
You will not see Trigger Monitor talking in Slack. It has no inbox, no command interface, and no chatter. It runs in the background, reads what was filed, and re-ranks the contacts it should re-rank. You see the result downstream: a higher-priority advisor in the Sales Assistant, a new face near the top of your prospect feed, or a fresh reason note attached to a contact in your CRM.
Every score change carries a reason and a source pointer, so any priority lift you see is traceable to the exact filing that caused it.
What It Does
Regulatory filings are noisy. New approvals, removals, and platform changes are published constantly, but only a small share of them actually change who you should be calling this week. Trigger Monitor reads the feed continuously, applies the rules your firm has set for the distribution channel you cover, and acts only on the events that meet those rules.
When a qualifying event lands (for example, an approval that opens a product on a channel an advisor sits on), Trigger Monitor lifts the intent score on the affected advisors and writes a short, plain-English reason next to it. Your CRM, your prospect feed, and the Sales Assistant all read that score. So while you do nothing, the right advisors quietly move up the list.
When nothing qualifies, Trigger Monitor stays silent. No filings of interest means no score changes and no audit rows; the agent simply waits for the next tick of the feed.
One kind of event is treated differently. When a competing product is removed from a platform, the advisors holding it face a forced decision rather than a gradual one, and a quiet score change is too slow a response. On a removal, Trigger Monitor re-ranks the affected prospects, stages a batch of outreach drafts for the top of that list, and posts to Slack with an accompanying email to the people covering those advisors. That notification goes to your own team, never to an advisor, and the staged drafts wait for a person exactly like every other draft in the product.
Key Capabilities
| Capability | What it gives you |
|---|---|
| Continuous filing watch | Reads the regulatory feed on a short interval so a qualifying event is reflected in priority within minutes, not days |
| Channel-scoped filtering | Acts only on filings tied to the distribution channel your firm covers; cross-channel noise is ignored |
| Intent score lifts | Raises the priority of affected advisor contacts so they surface higher in the Sales Assistant and prospect feed |
| Attached reason and source | Each priority change carries a one-line reason and a pointer to the source filing so any score is auditable |
| Deterministic behavior | The same set of filings against the same set of contacts always produces the same result; no probabilistic scoring |
| Forced-displacement response | On a platform removal, affected prospects are re-ranked, outreach drafts are staged for the top of the list, and your covering team is alerted by Slack and email |
What Requires Your Attention
Nothing Trigger Monitor produces reaches an advisor on its own. On an approval event it does not notify anyone at all: it adjusts the priority of contacts already in your CRM and attaches the reason for the change, and that is the whole of it.
On a platform removal it does more, and the difference is worth knowing so an unexpected Slack post is not a surprise. It stages outreach drafts and alerts your team by Slack and email. Both of those stay inside the firm. The drafts are drafts: they sit waiting for a person to read, edit, and release them, on the same approval step every outbound artifact in the product passes through.
The human approval gate lives where it always does: on whatever you do next. When the Sales Assistant surfaces a newly lifted advisor and you ask it to draft an outreach, that draft is what you review and approve.
If you want to understand why a particular advisor moved up the list, open the contact and read the reason that Trigger Monitor wrote there. The reason names the filing and the rule that fired.
Who It's For
- Distribution leads: See the highest-priority advisors first without manually tracking the regulatory feed. New approvals on your channel move advisors up automatically.
- Wholesalers: Find the advisors most likely to be receptive this week. A lifted score means a recent event has changed something on that advisor's platform.
- Sales operations: Trust the priority order in the prospect feed. The ranking already reflects what was filed; you do not need a side spreadsheet of recent events.
- Compliance and oversight staff: Audit any score change to its source. Every lift is attributable to a specific filing and a specific rule.
Related
- Commands - Why this agent has no direct commands and where you see its work
- Notifications - What Trigger Monitor surfaces and where it appears
- Schedule - How often the agent reads the regulatory feed
- Examples - Walkthrough scenarios showing how a filing becomes a higher-priority advisor on your list
- Troubleshooting - Common questions and what to check if a score change looks off