Troubleshooting

Frequently Asked Questions

Does Prospector Ever Email or Message an Advisor Directly?

No. Prospector is a research agent. It builds profiles, updates HubSpot, and posts cards inside Slack to your team. It never contacts an advisor, wholesaler, or LP. Any outbound message built on a Prospector profile goes through Signal Outreach or Sales Assistant and waits for your approval before it sends.

Why Did I Not Get a Card for an Advisor I Know Was Just Enriched?

Silence is intentional. If a re-enrichment run finds nothing material since the last stored profile, Prospector does not post. The profile and the freshness timestamp on the dashboard update either way; the Slack card is only for changes worth your attention.

What Does Material Change Mean?

A material change is a new, removed, or meaningfully altered section in the profile: a role change, a firm change, a new press hit, a new BrokerCheck disclosure, a new section on the practice site, a notable LinkedIn signal. Trivial deltas (a reformatted bio, a re-uploaded headshot, a minor LinkedIn engagement) are filtered out.

How Confident Should I Be in a Discovery Email?

Every email Prospector returns carries a confidence band and a source. Emails found and validated by the email finder are high confidence. Emails guessed from a configured firm pattern and then validated are medium confidence; the guess is marked as such. Emails that failed validation are flagged. Do not treat a low-confidence email as confirmed; use it as a hypothesis to verify by another channel before outreach.

Can I Trust the BrokerCheck and Press Sections?

Both come from public sources Prospector pulls directly. The press summary surfaces what the agent considers most material in the last window; trivial hits and aggregator listings are filtered. The BrokerCheck section reflects what is on file at the time of the pull. Always confirm regulatory facts in BrokerCheck itself before acting on them; the profile is a working summary, not a system of record.

What Happens When a Source Is Down?

If a source returns errors during a run, Prospector records the failure on the row, moves on, and runs the remaining sources. The profile that lands is built from whichever sources responded. The dashboard shows which sources contributed and which were skipped, so you can see the picture without surprise. If a source is down across enough runs to matter, you will see a provider issue notice.

Why Is Prospector Not Auto-Enriching Some Entities?

A few reasons. The entity may be inside its source cadence window (Prospector waits the configured interval between re-checks of a given source). The entity may be suppressed (someone on the team clicked Suppress for 30 Days on a prior card). The provider envelope for the month may be near its cap. You can force a refresh from Slack at any time to override the cadence.

How Do I Promote a Discovery Candidate to a Full Profile?

High-confidence candidates auto-promote into the enrichment queue. For lower-confidence rows, open the discovery tab on the dashboard and promote the row manually. The next enrichment pass picks it up.

What Is the Freshness Score on the Dashboard?

A single number per entity that combines the per-source last-checked timestamps, weighted by each source's cadence. A high score means the profile is current across all sources. A score that has slipped means at least one source is overdue for re-check.

Common Issues

A Profile Looks Out of Date

1. Check the freshness timestamps at the top of the profile. The age of each source's last check is visible per section.
2. If the profile is older than you expected, click Refresh Now on the card or ask Prospector in Slack to refresh the entity. The pull runs within the minute.
3. If the refresh runs but the profile still looks wrong, the source itself may be the issue (the advisor's LinkedIn is private, the practice site has changed structure, the press search is returning a namesake). Open the source links in the profile to confirm.
4. If the source is fine but Prospector is not picking up the change, contact support@alpheous.com with the entity name and what you expected to see.

A Discovery Candidate Email Bounced

1. Confirm the email's confidence band on the candidate row. A medium-confidence pattern guess is more likely to bounce than a high-confidence found email.
2. If the email validated as deliverable but bounced anyway, the inbox may have been disabled recently; this happens often when an advisor has just left a firm. Cross-check the LinkedIn role on the candidate row.
3. Mark the candidate as a false positive on the dashboard so the row drops out of follow-ups. If the candidate is still the right person at the right firm, you can ask Prospector to re-run the email finder against the new firm.

A Wrong Person Came Back from Discovery

Namesake confusion is a real problem in this work. The discovery pipeline does its best to distinguish, but a common name plus a firm domain that hosts multiple business lines can return the wrong person. Mark the row as a false positive on the dashboard; Prospector will not surface that pairing again.

The HubSpot Record Did Not Update

1. Check the HubSpot contact or company record directly. The writeback writes to specific properties only (the agent's approved property allowlist); fields outside that list are not touched by design.
2. Open the Timeline on the record and look for the most recent Timeline Event from Alpheous. The event body shows what the run wrote and when.
3. If the record looks untouched and you expected an update, the run may have found no material change to write. Open the profile on the dashboard to confirm the last-changed timestamp.
4. If the dashboard shows a change but HubSpot does not reflect it, contact support@alpheous.com with the entity name and the time of the run.

The Morning Meeting Prep Did Not Run

1. Confirm the meetings on your calendar carry external attendees (someone with an email outside your firm's domain). Meeting prep only fires when there is something to research.
2. Confirm your Google Calendar connection is active in Alpheous settings.
3. If both look fine but no card arrived, contact support@alpheous.com with the date and the meetings you expected to see.

The End-of-Day Digest Did Not Post

If there was no enrichment activity in the day, the digest skips on purpose (skip-if-zero). If you know there was activity and the digest still did not post, contact support@alpheous.com.