- Shipped
- August 5, 2026 at 7:51 PM UTC
- Author
- Kamo
- Commit
- 8f3c1ec
Every lead-creation path funnels through LeadService.createLead — CSV import, the lead-intake endpoints and their scheduled DaemonService job, the public webinar/demo form behind the marketing site, and the API — and none of them set requiresAssignment. It stayed at its false default, so an imported lead was unassigned AND invisible to **************** which is exactly what the Manage-Credits and Leads-Available surfaces count. Vendors that had just been fed a batch reported 0 Leads Available, and nobody could accept the leads that were sitting right there. createLead now flags a lead for the pool when it arrives without an owner and carries the vendor product + market the pool is keyed on, mirroring **************** and publishes the same availability event the accept-lead flow uses so open grids re-render live instead of waiting for a refresh. LeadRealtimePublisher gains that publish so the shared path can fire it from services with no SecurityService beans — notably MediaService, which owns the public demo leads. No status gate: the disqualifying states live in status/subStatus, which CreateLeadRequest cannot carry. prospectTypeId is the lead's SOURCE (LeadProspectType 1-4), not its status, and VENDOR is the pooled case.