Why "worked, then quiet" leads are a different cohort entirely
Most lead-stall views treat all silent leads the same — never-touched leads sit alongside leads that got worked then dropped. That's a mistake. The two cohorts need different responses:
- Never-touched leads are a queue problem. The rep didn't pick them up. Solution: assignment audit, SLA enforcement, lead-distribution review.
- Leads worked then gone cold are a follow-through problem. The rep judged them worth pursuing, made initial contact, and then went silent. Solution: re-engagement, hand-off to a nurture sequence, or explicit recycling.
Lead status — Attempting to Contact, Connected, Not Interested, etc. — is what separates the two cohorts. A lead with Attempting status was actively being chased. A lead at default status was never picked up.
The dollar cost of worked-then-cold leads is high because someone already invested time qualifying them. Letting them fade is wasted SDR effort. Re-engaging often surfaces real opportunities that just needed the rep to try again at the right moment.
What lead status really separates from default
Three filter conditions together:
- Lead status is
Attempting to ContactORConnected(the in-progress lead statuses, notNewand notDisqualified). - Last activity date is more than
21days ago. - (Optional) Lifecycle stage is Lead or MQL — exclude leads that already progressed past pre-deal stages.
The 21-day threshold comes from the HubSpot Community recommendation (Ruben Burdin's nurturing-pattern thread). Some teams tighten to 14 for high-velocity SDR motions, loosen to 30 for enterprise discovery cycles.
Why the rule misses the leads that need it most
Last activity date carries the same problem it does everywhere — sequence emails count as activity. A lead at Attempting to Contact enrolled in a sequence that's been sending to them for 3 weeks shows Last activity date = 2 days ago even though no human has actually reached out. The rule then misses them.
Two community workarounds:
Custom "human-touch" property. A workflow updates a custom date field only when an activity is logged that isn't a sequence-source email. Filtering on this custom date instead of Last activity date gives the honest signal.
Sequence-aware lead status flips. Some teams configure their sequences to NOT advance lead status, so the status reflects only human-rep judgment. Then Lead status = Connected plus Last activity date > 21 days captures the right cohort whether or not sequences are running.
The deeper friction is that lead status itself is a manually-maintained property. Reps don't always update it after a call ("yeah, I talked to them, they're considering it") because nothing forces them to. A lead can stay at Attempting to Contact for months even though a successful conversation happened — the status is just stale. The rule then misclassifies that contact's actual state.
The view catches the obvious cases. Genuine accuracy requires status discipline that most SDR teams maintain partially at best.
The manual HubSpot recipe
Three filters and you're done. The harder discipline is keeping Lead status honest — but even with imperfect status discipline, this view surfaces real cohorts worth re-engaging.
- Open Contacts → Create viewNavigate to Contacts → Contacts. Click 'Create view' in the top right.
- Add filter: Lead status is Attempting OR ConnectedFilter by Contact properties →
Lead status→ 'is any of' → 'Attempting to Contact', 'Connected'. These are the in-progress lead statuses, not 'New' (never picked up) or 'Disqualified' (already dropped). - Add filter: Last activity date is more than 21 days agoAND group →
Last activity date→ 'is more than' → 21 days ago. The 21-day threshold comes from the Ruben Burdin community pattern. - Add filter: Lifecycle stage is Lead or MQLAND group →
Lifecycle stage→ 'is any of' → 'Lead', 'Marketing Qualified Lead'. Excludes contacts that already progressed past pre-deal stages. - Sort by Last activity, ascendingColdest leads at the top. The rep should review in order — oldest first, since they've been silent longest.
- Save as 'Active leads gone cold'Pin to the SDR's daily dashboard. Optional: pair with a workflow that flips Lead status to 'Nurturing' after 30 days, so leads gracefully exit the active queue.
What Bloated does instead
Worked leads gone cold — sequence noise excluded, by stale-lead severity.
Bloated separates rep-touched leads from sequence-touched leads so the cohort surfaced is genuinely cold. The 'worked then dropped' signal is distinct from 'never picked up' — different action (re-engage vs. assign), different message (you started this, finish or recycle vs. someone needs to start). Pair with the suggested action: re-engage call, hand off to nurture, or recycle to MQL.
hs_lead_status, notes_last_contacted · HubSpot contact properties