Skip to Content
ProspectingLead Co-pilot

Lead Co-pilot

Lead Co-pilot runs overnight (or on manual trigger) to source and score new leads against your ICP. Each morning, proposed leads wait in a review queue — you promote the best fits into the primary Leads table or dismiss the rest.

What it is

Co-pilot automates the top of funnel:

  1. Copilot run — cron or manual job reads your ICP snapshot, searches Apollo/Redrob/web via the research pipeline, scores candidates, and stages ~10–20 proposals per run.
  2. Copilot leads — staged records with ICP and reachability scores, company intel, enrichment metadata, and status.
  3. Your review — humans promote or dismiss; nothing auto-enters Leads.

The page (/co-pilot) shows:

  • Summary panel — latest run stats (fetched, qualified, proposed, promoted, dismissed, averages)
  • Config bar — enable/disable, ICP linkage, target count
  • Review list — filterable lead cards
  • Run log — history of recent runs with status and errors

Co-pilot requires the lead_copilot module for your org.

Lead statuses

StatusMeaning
proposedAwaiting your review (default tab)
promotedAccepted into primary Leads — link to lead record
dismissedRejected — stays in log for audit
allEvery copilot lead regardless of status

Who uses it

RoleTypical use
RepMorning review — promote high-score leads, dismiss noise
Admin / OwnerTune config, monitor run log for failures

Step-by-step: review a proposed lead

  1. Open Lead Co-pilot → Proposed tab.
  2. Click a lead card to open the review sheet.
  3. Read ICP/reachability scores, company links, enrichment notes, and outreach summary.
  4. Verify or edit email, phone, and LinkedIn — promotion requires email and phone.
  5. Optionally Pull contact to run enrichment on missing fields.
  6. Choose:
    • Promote — moves lead to primary Leads pipeline
    • Dismiss — removes from proposed queue

Step-by-step: bulk promote or dismiss

  1. On the review list, select multiple proposed leads (checkboxes).
  2. Click Promote selected or Dismiss selected.
  3. Bulk promote skips leads missing required contact fields; errors summarize in a toast.

Step-by-step: check overnight run health

  1. Scroll to Run log at the bottom of Co-pilot.
  2. Inspect latest run: succeeded, failed, skipped, or running.
  3. Open run details for counts, average scores, and error messages.
  4. Fix integration issues (Apollo key, ICP config) if runs fail repeatedly.

Config bar

From the config section you can:

  • Enable or pause Co-pilot for the org
  • Align ICP snapshot used for sourcing
  • Adjust target proposal count (within system limits)
  • Trigger a manual run when you do not want to wait for cron

Manual runs respect the same qualification pipeline as overnight jobs.

Promotion requirements

Before Promote:

  • Email and phone must be present (edit or enrich first)
  • Lead moves to Leads with copilot source metadata and scores preserved
  • Promoted leads behave like any other lead — assign owner, run pipeline, approve drafts

Dismissed leads never appear in Leads.

Tips

  • Make Co-pilot part of your morning — summary panel shows how many proposals await review.
  • Enrich before promote — use Pull contact when Apollo had partial data.
  • Dismiss generously — low ICP fit clutters Leads; Co-pilot learns from your queue hygiene indirectly via config tuning.
  • Check run log after holidays — skipped or failed runs may mean zero proposals that day.
  • Promoted tab — quick link back to the primary lead record for outreach.
Last updated on
Discovery QueueAd Leads