What it can be a view of
One building block backs three different targets: conversations, contacts, or a report. Conditions are stored as a single query, the same shape the filter bar itself produces — so anything you can filter a list down to by hand, you can save. Your account has a limit on how many views one person can save at once, so clearing out ones you no longer use is worth doing occasionally.It is personal — not shared with a team
If that gap matters for how your team works, keep the underlying conditions documented somewhere everyone can copy from — a pinned message, a wiki page, anything outside Tied — since there is no single saved view that propagates to the rest of the team automatically.Where the same idea shows up elsewhere
The conversation list’s own filter bar is this exact mechanism, just unsaved — see Conversation views. A custom view is that same filter, given a name and kept around. The report variant applies the identical idea to reporting, letting you reopen a specific cut of a report without reconfiguring it from nothing each time.A view is not a rule
It is worth being direct about what a custom view cannot do: it has no actions. A saved view is a query and nothing else — it changes what you see, not what happens to a conversation. Automation rules look structurally similar, since both are built from conditions over the same conversation attributes, but a rule pairs those conditions with actions that fire on their own, unattended.A common path is to prototype with a view, then graduate to a rule. Save a view for “unassigned,
high priority, over two hours old” and watch what actually shows up in it for a week. Once you trust
what the filter catches, the same conditions become the trigger for an automation rule that acts on
them automatically instead of waiting for someone to open the view.
Next
Conversation views
The filter bar this feature saves a copy of.
Automation rules
Turning a filter you check manually into one that acts on its own.