lead_score
Score a website lead (the Minhelet lead form): the lead-quality score 0 to 10 from the form fields, combined with the Asset Analyzer feasibility of its building (final = round(0.4 x quality + 0.6 x feasibility), capped at 3 for NO-GO and 7 for GO-WITH-CAUTION) and its tier (חם, חמים, קר, חלקי, זבל, or מחוץ לביקוש). Before any GO or hot/warm tier the city is checked against city_demand (same source as GET /api/demand-cities/lookup). A known non-demand city or an unknown city (demand_city false or known false) is not GO: tier מחוץ לביקוש, decision OUTSIDE-DEMAND, dial_allowed false. The numeric score stays in lead_quality_score and reasons. If the demand table cannot be read, demand_city is null and the tier is not forced. With analyze: true it starts the asset check of the lead's building and adjacent buildings (counts against the asset_analyze daily limit; junk leads are not checked); past wait_seconds it returns {pending, run_id}, then call lead_score again with the same lead and that run_id. Without either, it scores lead quality alone.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lead | Yes | The lead form body as the website posts it (first_name, last_name, email, phone, city, street, building_number, building_units, building_floors, project_status, has_active_project, has_active_representation, adjacent_buildings_addresses, resident_consensus, known_opponents, has_signed_poa, message, ...). | |
| run_id | No | The run_id an earlier lead_score or asset_analyze returned: combine with that check. | |
| analyze | No | Start the asset check of the lead's building(s). | |
| wait_seconds | No | With analyze: how long to wait before returning {pending, run_id} (default 50, max 290). |