Inbound — morning queue
? what this feature does·💡 where we’re taking it·💡 how it’s implemented — the walkthroughclick any wherever you see them
Product development by playbook & runbook — each line of business (flood · fire · hurricane) is a configuration-driven playbook; the runbook is that playbook resolved for a context (state, business line); every field and rule carries effective/expiry dates — a new state is an activation, not a release.
0 editable leads. Inspect & change any field (chips flip input → missing live), then Submit all → intelligent prefill fills every service-owned field (assessor, hazard/GIS, aerial, permits, cat-model), and each lead reaches its terminal: most auto-quote, runbook declines auto-send, conflicts land in UW review, customer-only gaps in Outbound. Submitted leads leave this queue until a master reset.Source:
All caught up
Every lead has been submitted and routed. They now live in the UW Cockpit (review) and Outbound (request-info / approved). Master reset brings back the offline morning queue for another clean scenario.