Inbound Lead Dedupe Auditor

Scenario

Use after normalization when the same inquiry can arrive from a form, email, ad platform, or a repeated CRM import.

Input and output

Input is a JSON object with leads, each containing lead_key, email_ref, phone_ref, and company_ref, plus an optional known_keys list. Output separates unique records, duplicates, and conflicting contact references.

Execution and recovery

Run python scripts/dedupe.py examples/input.json. If a key is absent, fix the upstream contract first. The skill does not query a CRM or delete records.

Privacy boundary and acceptance

Use hashes or placeholders only. Acceptance requires deterministic duplicate groups, stable unique records, and an explicit conflict list.