Route incoming leads without a human triaging every one
Build-along · ~15 min at your own keyboard
Leads arrive from five places and get triaged by hand, or not at all, until the good ones go cold. A router fixes the pipeline: it ingests each new lead, scores it against a rubric you can see and tune, dedupes against what you already have, and routes it, hot ones to a call list, the rest to a nurture row. This is the sheet-pipeline pattern grown a brain. Three rules make it trustworthy. The SCORE is transparent, every point traces to a rule you wrote, no black box, so you can defend and adjust it. DEDUPE is real, matched on a stable key (email, phone, or owner+address), so the same lead never gets worked twice. And the guardrail holds: the score uses behavior and fit (source, budget, timeline, property match), never a protected characteristic or a proxy for one, because routing by who someone is rather than what they need is the line you don't cross. Build it to write back to your CRM or sheet, and the agent hands you a worked call list instead of a pile.
Your starter: Lead router rules
ChecklistMake it yours: Replace the buckets with how your desk actually divides work, name the people, and add the one rule that keeps a bad lead from reaching a principal.
LEAD ROUTER A lead arrives as [form submission / forwarded email] at [inbox or folder]. Bucket by asset and size: - [Asset A] under [size]: to [person] - [Asset A] over [size]: to [person] - [Asset B]: to [person] - Anything else: to the holding list, never to a principal Before routing, write the facts table: who, what, where, size, source. A field the lead did not give is [SOURCE NEEDED: field], never filled in. No number without a source and a date: a size the lead states is written as stated, with the lead's date. Output: one line per lead, the bucket, and the facts table. I forward; the router never sends.
The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.
Do this
0/5Share what happened
Paste your scoring rubric with weights, one batch's routed output showing per-lead score components, proof dedupe caught a repeat, the protected-class guardrail note, and your cost cap.