Setting up filters

What you'll learn

What filters are, how they differ from lists and labels, how to build a filter condition, and how to use filtered views for daily reply prioritisation.

What filters do (and why they matter)

Filters are rule-based conditions that decide which conversations appear in a view. They're the action layer — they let you narrow the inbox down to exactly the replies you care about right now.

Use them to:

• Prioritise hot leads
• Avoid missed follow-ups
• Separate signal from noise
• Move faster without juggling multiple tabs

A few examples of useful filters:

• Labels NOT spam / unwanted / casual
• Reply since less than 7 days

Lists vs labels vs filter views

The dashboard uses three layers that often get confused:

List item — conversation pipeline stage

List items show where a reply sits in your pipeline. Examples: Lead, Deal, Client, Other. Lists answer: what type of conversation is this?

Label — reply intent

Labels classify a conversation and feed filters and views. Examples: Hot lead, Interested, Follow-up, Not interested, Client, Information request, Spam. Labels answer: what does the prospect actually want?

View — a dedicated display

A view is a tab that shows only the conversations matching specific filter rules. Examples: High intent, Follow up, Casual, LinkedIn only.

A few common scenarios

Scenario 1 — new lead reply

• List: Lead
• Label: Interested
• View: High intent
• Filter: label EQUALS interested

Scenario 2 — lead asked for time

• List: Lead
• Label: Follow-up
• View: Follow-up later
• Filter: label EQUALS follow-up

Scenario 3 — existing client reply

• List: Client
• Label: Client question
• View: Clients
• Filter: label EQUALS client OR list EQUALS client

Scenario 4 — not a sales opportunity

• List: Other
• Label: Not interested / Informational
• View: Unwanted
• Filter: label EQUALS unwanted/spam

Useful label combos for common views

View: High-intent

• Label EQUALS interested, hot lead
• Last message from EQUALS prospect
• Reply since prospect less than 14 days

View: Follow-up later

• Label EQUALS follow-up
• Reply since prospect less than 7 days

View: Casual chats

• Label NOT hot leads, interested, client

What filter views answer for you, daily

Good filter views answer one question at a time:

• What needs my attention now?
• What can wait?
• What can be ignored?
• What belongs to a client vs a lead?

How to set up a filter

1. Click the ➕ (plus) icon at the top of the workspace.
2. Enter a filter name and create it.
3. Select the filter in the view you want it applied to.
4. Choose the values to filter on.
5. Click Apply.
6. Save the filter.

You can stack more than one filter on the same view.

How filter conditions work

Every filter has three parts.

1. Field — what to filter on

Common fields:

• Label — prospect intent
• List — conversation stage
• Channel — email or LinkedIn
• Campaign name — which outreach campaign the contact came from
• Domain — company email domain
• Reply since / Prospect reply since — time-based filtering
• Read status — read vs unread
• Follow-up count — how many follow-ups have gone out

2. Condition — how to match

• Equals → exact match
• Doesn't equal → exclude something
• Contains → partial match
• Doesn't contain → strip out noise
• Starts with / Ends with → subjects or domains
• OR → match either condition
• NOT → exclude specific cases

3. Value — what you're looking for

A few concrete examples:

Hot leads to reply first

• Field: Label
• Condition: Equals
• Value: Interested

Client conversations

• Field: List
• Condition: Equals
• Value: Client

LinkedIn replies only

• Field: Channel
• Condition: Equals
• Value: LinkedIn

Replies in the last 24 hours

• Field: Prospect reply since
• Condition: Equals
• Value: Last 24 hours

Exclude warmup or noise

• Field: Subject
• Condition: Contains
• Value: warmup

Exclude multiple lists

• Field: Lists
• Condition: NOT
• Value: Not Interested, Follow Up, etc.

If a filter isn't behaving

See How labels, filters and views work together for a walkthrough of the common gotchas — view population, Needs Reply logic, and sent-only filtering behaviour.