Skip to main content
When your Watchlist Agent runs, each candidate goes through a pipeline of checks before landing in your List. Understanding this pipeline helps you debug when things don’t match your expectations.

​
The 5 stages

1

Search

Guhan queries LinkedIn (or a signal-specific data source) for people matching your ICP + signal. May return 5-500 candidates per run.
2

Enrich

For each candidate, Guhan reads their full LinkedIn profile — current company, headline, recent activity. This is the raw material for scoring + message-writing.
3

Score

Apply your must-match filters (title, location) + weighted filters (industry, headcount, signal). Anything below threshold is rejected here.
4

Deduplicate

Check whether this prospect already exists in your workspace (from a prior sweep or a different Watchlist Agent). If yes, skip — no double-messaging.
5

Land

Add the prospect to your List. From here, your Outreach Agent picks them up.

​
Where prospects get filtered out

Not every candidate lands. Each stage can reject:
  • Search — LinkedIn returns nobody / search quota exhausted for the day
  • Enrich — LinkedIn profile is private, blocked, or a company page (not a person)
  • Score — filters didn’t match (wrong title, wrong location, wrong industry, etc.)
  • Deduplicate — already in your workspace from a prior sweep
  • Channel check — no reachable identity (no LinkedIn URL AND no email AND no phone)
The Watchlist Agent detail page shows every rejection with a reason under the Filtered accordion.

​
What “landed” means

A prospect that lands has:
  • ✓ Passed all must-match filters
  • ✓ Been enriched with LinkedIn data
  • ✓ Been added to your target List
  • ✓ Cost you 1 credit (that’s what “landed” means for billing)
From there, your Outreach Agent may or may not enroll them into a sequence — depends on whether there’s an active Outreach Agent bound to that List.

​
Sender enforcement

Guhan used to reject prospects at Stage 5 if you had no matching sender account connected. That check moved to send time — a prospect lands regardless, and the send-time gate catches any missing sender + tells you what to connect. Meaning: you can start finding prospects before you’ve connected all your sender accounts. Guhan will build up a List of qualified prospects and start messaging as soon as senders are wired.

​
Debugging: why didn’t X land?

Common cases:
Your location filter didn’t match their LinkedIn location. Check if the person’s LinkedIn city is spelled differently or if they’re in a different country than you targeted.
You already found this person via a prior sweep. Guhan won’t add duplicates — they exist elsewhere in your workspace. Search the Prospects page to find them.
LinkedIn returned a Page or Company ID instead of a real person. This happens when engagement signals pick up company-branded reactions. Auto-handled.
Guhan couldn’t find any way to reach this person — no LinkedIn URL, no email, no phone. Typically happens with private profiles or profiles blocked in your region.
Your filters are too tight. Loosen a signal, expand the location, or add more title variants. Check the Watchlist Agent detail page — the “Today’s sweep” strip shows what searched.

ICP scoring

How the score gets calculated + how to loosen or tighten it.

Signals

The triggers that drive the search stage.