Alpheous·
Intelligence

Troubleshooting

Frequently Asked Questions

Why Doesn't Trigger Monitor Post in Slack?

Trigger Monitor has no Slack interface by design. It is a quiet background agent that updates priorities on advisor contacts; the surfaces that read those priorities (the Sales Assistant, your CRM, the prospect feed) are where you see the result. A Slack post for every filing would be noise. If you want a regular read on regulatory activity, the Regulatory Digest is built for that.

Where Do I See What Trigger Monitor Has Done?

Three places: the ranking the Sales Assistant gives you when you ask for your top advisors or prospects; the intent score and reason note on an individual advisor's contact in your CRM; and the order of advisors in the prospect feed. If a contact's score changed recently, the reason note will say what filing caused it.

Why Did an Advisor's Score Change?

Open the contact and read the reason note attached to the score. It names the event type, the platform, and points back to the source filing. If the note is not what you expected (the event is real but the advisor should not have been affected), see "An advisor moved up the list and I don't think they should have" below.

Can I Change Which Filings Trigger a Priority Lift?

Yes, but not directly. The event types Trigger Monitor acts on, the distribution channel it cares about, and the threshold for "qualifying" are set in your firm's configuration. Ask your firm administrator to adjust them. Changes take effect on the next cycle.

Will Trigger Monitor Ever Reach Out to an Advisor Directly?

No. The agent only updates contact priorities and writes reason notes. Any outbound message to an advisor goes through a drafting agent and a human approval step. Trigger Monitor is upstream of all of that.

How Quickly Does a New Filing Show Up as a Score Change?

Within roughly a minute of the filing being published. The agent checks the feed continuously on a short interval; a qualifying filing landing at 9:14 a.m. is reflected in priorities by about 9:15 a.m. There is no daily batch.


Common Issues

An Advisor Moved Up the List and I Don't Think They Should Have

  1. Open the advisor's contact and read the reason note next to the intent score. The note names the filing.
  2. Confirm the filing is real and that the advisor is tied to the platform or channel it references.
  3. If the filing is real but the advisor's connection to the platform is out of date in your CRM, ask your firm administrator to refresh the advisor's record. The next cycle will reflect the correction.
  4. If the filing itself looks wrong for your channel, let your administrator know so the channel filter can be reviewed.

A Filing I Expected to Move Things Did Not

  1. Confirm the filing is the right event type. Trigger Monitor acts only on the specific event types your firm has configured (for example, platform approvals and removals). News articles and analyst commentary do not qualify.
  2. Confirm the filing references the distribution channel your firm covers. Cross-channel filings are ignored by design.
  3. Check whether any advisors on the affected platform are present in your CRM. If no advisor is matched, no score writes happen even when the filing is otherwise qualifying.
  4. If all of the above check out, contact your firm administrator.

The Intent Score Says It Lifted but the Sales Assistant Still Ranks the Advisor Low

  1. Refresh the Sales Assistant by asking for the top advisors again. Open lists do not auto-update.
  2. Confirm the score change actually wrote (open the contact and check the value).
  3. The ranking blends intent score with other factors (territory, recent activity, account stage). A small lift may not be enough to overcome a competing factor. Ask the Sales Assistant directly why a specific advisor is ranked where they are.
  4. If you believe the ranking is misweighting the lift, let your firm administrator know so the scoring weights can be reviewed.

Many Advisors Suddenly Lifted at Once

  1. This is normal after a large platform-level event. An approval or removal on a major channel can affect dozens of advisors at the same time.
  2. Open any of the affected contacts and read the reason note. The same filing should be referenced across the cluster.
  3. Use the Sales Assistant to triage: ask for the highest-value affected advisors first rather than working through the whole cluster at once.

If you need help that isn't covered here, contact support@alpheous.com.