Examples

Example 1: A Platform Approval Lifts a Cluster of Advisors

A regulator publishes a platform approval that opens a new product on the broker-dealer channel your firm covers. Roughly forty advisors in your CRM sit on that platform.

Step 1: The filing lands. Trigger Monitor reads the new filing on its next cycle. It recognizes the event as a platform approval on the channel the firm watches.

Step 2: The agent identifies the affected advisors. The agent looks up which advisors in your CRM are tied to that platform. Forty contacts match.

Step 3: Scores update. On each of those forty contacts, the intent score is lifted. A reason note is attached: "Platform approval on the relevant channel, recent filing." A source pointer back to the filing is stored alongside.

Step 4: You see it the next time you look. The following morning, a wholesaler asks the Sales Assistant for the top advisors to work this week. Several of the lifted advisors appear at the top of the list. The wholesaler clicks one and reads the reason note: a platform approval landed, and this advisor is on that platform. The wholesaler picks the most relevant three for outreach this week.

Step 5: Approval lives at the next step. The wholesaler asks the Sales Assistant to draft a brief introduction for one of the advisors. The draft references the recent platform change. The wholesaler reviews, edits a line, and approves. The outreach goes out.

Example 2: A Platform Removal Surfaces a New Conversation

A regulator publishes a platform removal: a product is being pulled from a channel a handful of advisors in your CRM are on.

Step 1: The filing lands. Trigger Monitor reads the filing on its next cycle and identifies it as a removal event on the relevant channel.

Step 2: The agent identifies the affected advisors. A small number of advisors are tied to the affected product on that platform. The agent matches them.

Step 3: Scores update with the removal context. Each affected advisor's contact gets a priority lift with a reason note explaining the removal. The reason is specific: the product, the platform, the type of event.

Step 4: A wholesaler notices an unexpected name. Later that day, a wholesaler opens the prospect feed and sees an advisor they had not been working with this quarter near the top. They open the card and read the reason note. The advisor has just lost the product that was a big part of their book.

Step 5: A focused conversation, well timed. The wholesaler asks the Sales Assistant for context on the advisor. They draft a short note acknowledging the change and offering a quick conversation about alternatives. The wholesaler reviews and approves. The note goes out the same day, before competitors have moved.

Example 3: A Quiet Day With No Score Changes

It is a normal Wednesday. Several routine filings publish during the day; none of them are the event types your firm tracks, or none involve advisors on the right platform.

Step 1: The agent checks the feed. Each minute, Trigger Monitor reads the regulatory feed. It evaluates each new filing against the configured rules.

Step 2: Nothing qualifies. No filing matches the channel and event type criteria. The agent writes nothing to any contact.

Step 3: The agent stays silent. No alerts, no audit rows, no score changes. The agent simply waits for the next tick.

Step 4: Your day continues unchanged. A wholesaler opens the prospect feed. The priorities are exactly what they were yesterday. There is no missing event to chase. Silence is the correct outcome: nothing relevant has landed.

Example 4: Auditing a Score Change

A compliance reviewer is doing a routine audit on the advisor contacts that received outreach this month. One advisor's contact shows a score that was lifted earlier in the month.

Step 1: The reviewer opens the contact. The intent score field shows the current value. Next to it is the reason note Trigger Monitor wrote: the event type, the platform, the rough date of the filing.

Step 2: The reviewer follows the source pointer. The source pointer references the specific filing that caused the lift. The reviewer reads the filing and confirms it is a real public-record event on the channel the firm covers.

Step 3: The audit closes cleanly. The score change ties directly to a public regulatory event and to a documented rule. The chain from filing to score to outreach is intact. The reviewer signs off and moves to the next contact.