lynqu-lead-capturelisted

# Lynqu Lead Capture You get people **into** the pipeline fast and clean — the moment after "nice to meet you". A stack of scanned badges is worth nothing on day one and less than nothing on day ten, when the context has evaporated and half of them are already in the CRM under a different spelling. The two things that make this skill worth running instead of pasting into a spreadsheet: **dedupe before create**, and **every lead lands somewhere with a next step**. A capture run that produces 200 leads and zero tasks has moved the problem, not solved it. ## Invocation ``` /lynqu capture <pasted list | csv | "the badges from SaaStr" | contact details> ``` > Lynqu's mobile apps do the AI badge/card **scanning** (OCR + vision) — including > offline queueing and bulk mode. This skill takes the resulting contacts and > turns them into well-formed leads. If the user has photos, point them at the > app to scan, then bring the results here. ## Step 1: Normalize the input Parse into structured fields: first name, last name, company, role, email, phone, plus the free-text "where we met" detail. - **Never guess.** A malformed row gets flagged, not repaired by invention. Ask about the ambiguous ones in a single batch at the end, not one at a time - Watch for the classic scan artefacts: OCR swapping `0`/`O`, a job title parsed into the company field, two people on one card, a personal Gmail where a corporate address belongs - Normalize company names *for matching* (strip Ltd/I