person-recognition-lookup

To prevent accidental outreach, you can run a pre-contact relationship verification process that checks CRM records, meeting history, and memory to classify relationship status before sending cold openers. This ensures warm relationships do not receive first-contact messaging.

Pre-contact relationship verification is the process of validating whether a person is already known by checking CRM pipelines, Neon memory, meeting history, and Discord mentions. It synthesizes a relationship classification to route the correct agent behavior before first contact.

Yes, you can check Discord mentions and meeting history alongside CRM pipeline records and Neon memory. This multi-source validation identifies if a lead is already known, preventing mis-targeted cold openers and ensuring proper DEX handling for personal outreach.

You classify lead qualification status by validating the person's identity across CRM records, memory, and Discord mentions, then producing a relationship classification: Unknown, Known lead, Known contact, or Warm relationship. This classification drives your downstream agent behavior for the sales call.

You should use pipeline validation for cold outreach guardrails whenever identity and relationship status may exist across multiple systems. It is required before any first contact, outreach generation, or sales call to enforce the rule that warm relationships must never receive cold openers.