--- name: lead-triage-form-fill description: Triages a new inbound lead from a form submission by enriching it, scoring it against the ICP, recommending an owner or route, and drafting a first-touch reply. Use when a form is submitted or the user asks to "triage this lead", "score and route this inbound", "is this lead worth working", "draft a reply to this inbound". license: MIT compatibility: Requires a connected CRM and web enrichment. Read-first — proposes routing and a draft, no auto-writes. metadata: author: Builder.org version: 2.0.0 persona: Marketing Meg, Operator Owen rave: R4 A4 V3 E4 category: crm --- # Lead Triage (Form-Fill) ## What it does Does the first-five-minutes work on a fresh inbound lead: enrich the person and company, score against the ICP, recommend where it should go, and draft the first reply. Speed is the whole economics of inbound; a lead answered inside an hour converts at a multiple of one answered tomorrow. Everything is proposed for confirmation; nothing writes or sends itself. ## When to use - "Triage this lead", "score and route this inbound", "is this lead worth working". - "Draft a reply to this inbound", or triggered on a form submission. - Not for enriching an existing contact outside the inbound flow; that is `contact-enrichment-on-create`. This skill's job ends when the lead has a score, a route, and a reply. ## Inputs The form submission or a contact email. Works with any CRM your assistant can read (HubSpot, Salesforce, or similar). Optional: the ICP definition and routing rules. Without an ICP, it scores against a stated default (company size, industry fit, role seniority, and intent shown in the form) and says so. ## The bar - The score comes with its top three reasons, visible. An unexplained 74 out of 100 teaches nobody anything and gets ignored by Friday. - The scoring assumptions are stated every time. "Scored against: 10-500 employees, services industries, manager or above" makes disagreement productive. - The draft reply references what they actually asked for on the form. An inbound reply that ignores the form field they filled in is a cold email with worse timing. - "Nurture, not sales-ready" is a first-class outcome with a reason, not a failure. Protecting rep time is half the point of triage. ## Workflow 1. **Enrich.** Person: role, seniority, LinkedIn if findable. Company: size, industry, region, anything notable and recent. Sources: the web and whatever enrichment tool is connected. Mark anything unverifiable as blank rather than guessed. 2. **Score against the ICP.** 0 to 100, from the provided ICP or the stated default. Weight what the form itself reveals highest; a specific question about pricing outranks a matching industry, because intent beats fit at the margin. Show the top three reasons for the number. 3. **Recommend the route.** An owner or team from the provided rules (territory, segment, size), or the default: sales-ready to the round-robin, partial fit to nurture with the sequence named, poor fit to a polite decline. State which rule fired. 4. **Draft the first touch.** Short, warm, specific to their form answer, one next step. If they asked a question, answer it in the first two lines; earning the meeting comes after earning the reply. 5. **Present the triage card** with score, route, and draft, and wait for confirmation before any field is written, any owner assigned, or anything sent. If you cannot ask, mark the card "unconfirmed" and stop there. ## Output ``` ## Lead triage · [Name, Company] **ICP score:** [N]/100 **Why:** [top 3 reasons] **Scored against:** [the ICP or default assumptions used] **Enrichment:** [role · company size · industry · region] (unverified fields left blank) **Route:** [owner/team/nurture] · rule: [which rule fired] **Draft first-touch:** Subject: [subject] [body] Confirm to apply enrichment / assign owner. Nothing sends automatically. ``` ## Worked example ``` Fictional example. Never reuse these names or numbers in real output. ## Lead triage · Rachel Imani, Summit Physical Therapy **ICP score:** 78/100 **Why:** exact industry match (multi-location clinics); asked a pricing question on the form, which signals evaluation intent; company size (6 locations, ~90 staff) sits mid-range for us. **Scored against:** default ICP: 10-500 employees, services industries, manager or above, form intent weighted highest. **Enrichment:** Director of Operations · ~90 employees · outpatient physical therapy · Colorado (LinkedIn title verified; employee count from their site) **Route:** round-robin, sales-ready · rule: score over 70 with direct pricing intent. **Draft first-touch:** Subject: your scheduling question Rachel, you asked whether the platform handles per-location scheduling rules, and it does; each clinic keeps its own hours, providers, and booking logic under one account. Happy to show you how a 6-location group set it up, in 20 minutes this week. Would Wednesday or Thursday afternoon work? If it's faster, I can send a 3-minute video first. Confirm to apply enrichment / assign owner. Nothing sends automatically. ``` ## Never - Never output a score without its reasons and its assumptions. - Never force a confident score on a thin lead; a low-confidence 50 routed to nurture beats a fabricated 80. - Never draft a reply that ignores the form content. Their words are the warmest thing about a warm lead. - Never write fields, assign owners, or send email without confirmation. Read-first means read-first. ## Recovery - Free-email address and no company field: enrich from the name and any domain clues; if the company stays unknown, score what is known, cap the score, and say why it is capped. - Enrichment finds nothing: triage on the form alone, mark every enrichment field blank, and let the form's intent carry the routing decision. - Obvious spam or a student or a vendor selling to you: classify it as such, recommend no reply or a polite template, and skip the scoring theater. - No routing rules and multiple possible owners: recommend by the visible tiebreaker (territory match, then least recently assigned) and name it, so the team can codify the rule later.