Save a view and share it
A filter you named. It keeps the definition, not the result, so it is right every time you open it.
A saved view stores the definition rather than the result, so it re-evaluates every time you open it. That is what makes it useful three months later when a static list would have gone stale.
The underrated benefit is linguistic. When a team agrees what "stale lead" means and saves it as a view, every conversation about stale leads gets shorter — because everybody is looking at the same definition rather than each building their own filter.
Before you start
- A filter you have already built and verified by opening a few records.
- A name that states the rule rather than a person.
Steps
Build the filter and check it first
Open a few records. Naming a filter you have not verified propagates the mistake to everybody who uses it.
Save it with a name that states the rule
"Open leads · Mumbai · no contact in 30 days" tells the next person exactly what they are looking at. "Priya's list" tells them nothing and will outlive Priya.
Remember it stores the definition
It re-evaluates when opened. It is not a snapshot, which is why it stays useful — and why it is the wrong tool when you need a fixed set that must not change.
Use it as a shared vocabulary
Views are how a team agrees what its own words mean. That is worth more than the time they save.
Review views quarterly
A view referencing an attribute whose meaning has drifted is worse than no view, because people trust it.
Check it worked
Open a view you saved a month ago. If the count has moved in a direction you did not expect, either your business changed or the rule was never quite right — and both are worth knowing.
The parts people get wrong
- Use a saved view for a segment, and a static list when you need a fixed set that must not change.
- Deleting an attribute a view depends on breaks the view silently.
The ones people actually ask
Is a saved view a snapshot?
No. It stores the definition and re-evaluates when opened, which is why it stays useful — and why it is the wrong tool when you need a fixed set that must not change. For that, use a static campaign list or an export.
How should I name one?
After the rule, not the person. Open leads, Mumbai, no contact in 30 days tells the next person exactly what they are looking at. Priya list tells them nothing and will outlive Priya.
Should we review views?
Quarterly. A view referencing an attribute whose meaning has drifted is worse than no view, because people trust it.