A funnel icon on each column header opens a chip popover. The Contacted stage has hand-tuned chips matching its follow-up SOP: Followed up once, twice, three or more, Short-term nurture, Long-term nurture, Needs callback, No response. Every other stage derives its chips from its own checklist steps plus Needs callback and Next action overdue. Selected chips combine with OR and persist per stage.
Also called: filter by follow-up count · needs callback filter · batch similar work
- 1Filters read the deal's SOP checklist state, next action type and due date
- 2Contacted has explicit overrides; other stages generate a 'Did: <step>' chip per checklist step
- 3Multiple chips OR together so mutually exclusive buckets do not cancel out
- 4The chip set persists per stage
Every stage asks a rep to do different work, but the board offered one filter set for all of them, so pulling up everyone in Contacted who had been followed up twice meant reading the whole board card by card. Each stage now builds its own filter chips from its own checklist, and selected chips combine as OR so mutually exclusive buckets like followed-up-once and followed-up-twice don't cancel each other out. Reps batch similar work in one tap instead of hunting.
- No way to batch the same kind of work across a stage
- Follow-up counts recorded but unusable
- Callbacks scattered across a whole column
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →