Smart lists and acting on many leads at once
A smart list is a named filter you can come back to. It stores the rules, never a frozen set of names, so it is always current. Once you have the set, a toolbar acts on all of it.
What you can filter on
- Temperature band, or a minimum and maximum score.
- Pipeline stage.
- Source. This is the lead's acquisition source, the channel they arrived through, such as your branded site, organic search, a paid ad, a referral, an import, or the API.
- Owner, or unassigned.
- Whether they are on the working list, and their pre-qualification status.
- Created before or after a date.
- Tags, matching any of them or all of them.
- Activity recency: active in the last N days, or nothing for N days.
- Whether there is a consent record for email or for text.
Archived and deleted leads are never in a smart list, whatever the filters say. There is no setting that lets them back in. Reach an archived lead through the archived view instead.
Filing a scanned document against a lead does not count as activity for the two recency filters. It is something you did to a file, not contact with the person, and counting it would drop them out of a re-engagement list.
The bulk actions, and what each really does
- Reassign. Moves the pipeline owner. The agent it lands on gets a bell.
- Change stage. Moves the pipeline stage.
- Tag and untag.
- Add to the working list. Read the next section before using it.
- Export CSV. Downloads the selection. Changes nothing.
Every action previews a count before it runs, and asks you to confirm. Large sets are processed in chunks, so one bad row does not undo the rest, and you get a per-lead result. Re-running the same action is a no-op rather than an error.
Add to the working list does not start a cadence
This is the one that is easy to misread. It marks leads as enrolled on the working list and writes a timeline entry. That is all it does.
Being on the working list makes a lead ELIGIBLE for Today's top calls and the stalled-lead readout, and it is a filter on the leads list. It does not make them appear there: those lists also require a score and then take the top few.
It creates no strategy, plans no touch, schedules nothing and sends nothing. A real Cultivate cadence is only started from a lead's own record with Generate strategy, or automatically if your brokerage has switched on auto-enroll.
The text-consent filter returned fewer leads than I expected.
Good. In Florida, Washington and Oklahoma a consent record is not consent on its own: the contact has to reply to confirm first. The filter applies exactly the rule the send gate applies, so it cannot offer you a set that every send would then refuse.
Does that filter mean I can definitely reach them?
No. It only says a consent record exists and is not held down by a strict-state rule. It does not check suppression, do-not-call, carrier type or your text registration. The delivery card on the contact's own record answers can I reach this person.
Need more help? Contact support.