How labels, filters and views work together
Why a label you applied doesn't always show up in the view you expected — and how Needs Reply is actually populated.
What you'll learn
Why a label you applied doesn't always appear in a prospecting view, how Needs Reply is actually populated, and what shows up in your inbox versus what doesn't. Understanding the rules makes troubleshooting almost instant.
People ask the same questions in different ways: Why doesn't my label show up in a prospecting view like "warm" or "hot" do? Or why is Needs Reply pulling stuff I didn't expect?
The answer comes down to how three pieces interact: labels, filters, and views.
The hierarchy: labels → filters → views
The dashboard uses a three-layer system to decide what appears where.
Labels Labels classify the intent of a reply — Interested, Not Interested, Follow-up, Out of Office. They're context markers. They don't control where a conversation appears on their own.
Filters Filters are rule-based conditions that decide which conversations appear in a view. A filter might say "Label equals Interested" or "Last message from equals Prospect." This is the logic layer.
Views Views are the displayed result — a dedicated tab that shows only the conversations matching your filter rules. Views are what you click on in your inbox.
The key insight: applying a label doesn't automatically make a conversation appear in any specific view — unless that view's filter rules actually include it.
Why a label doesn't show up in a view
If you apply a custom label and it doesn't surface in your prospecting view, it's almost always one of these:
1. The filter doesn't include that label
Check the filter conditions for that view. If the filter says Label equals Interested, Information Request, Meeting Request, then a conversation labelled Hot lead won't appear there — even if you just applied it.
Fix: edit the view's filter to include your label, or create a separate view for it.
2. The filter needs additional conditions
Some views — especially reply-focused views like Needs Reply — use combined rules. The default Needs Reply view requires both:
Last message fromequalsProspect, and- A label indicating interest (or no exclusion label)
If you label a conversation Interested but the last message was from you (not the prospect), it won't appear in Needs Reply. It will appear in a Follow-up view instead.
Fix: check whether the view has multiple filter conditions. A label alone isn't always enough.
3. The view excludes certain labels
Some views use NOT conditions to keep noise out. If your label falls into an excluded bucket — Warmup, Spam/Unwanted, Not Interested — the conversation won't appear even if other conditions match.
Fix: review the filter's exclusion rules. If a label is meant to be actionable but is being excluded, update the filter or reconsider the label's sentiment.
How Needs Reply is populated
Needs Reply is one of the most important default views. It shows the conversations that require your response right now.
Needs Reply is populated by message direction + label logic, not by activity alone.
Included in Needs Reply
- Last message is from the prospect
- Label indicates positive intent (Interested, Information request, Meeting request, etc.)
- No exclusion label is applied (Not Interested, DNC, Out of Office, etc.)
Not included in Needs Reply
- Last message is from you (your team sent the most recent reply)
- Label is negative or neutral (Not Interested, DNC, Out of Office)
- The conversation has no reply yet — only an outbound send
The default Needs Reply view is configured as Last message from equals Prospect. The conversation only surfaces here when the prospect has the last word. If you replied and they haven't come back, that conversation moves to a Follow-up view.
Common confusion points
"I labelled a conversation as Interested but it's not in Needs Reply" Check the last message direction. If you sent the most recent reply, the conversation no longer matches "Last message from equals Prospect". It should appear in your Follow-up view, waiting for their response.
"A conversation I expected to see in Needs Reply is missing" Three common causes:
- Message direction — the prospect hasn't actually replied yet. Needs Reply only shows conversations with a reply from the prospect.
- Exclusion labels — the conversation may have a label that excludes it (Warmup, Spam, Not Interested).
- Sync timing — if the reply is very fresh, it may not have synced yet. Wait a few minutes or trigger a manual sync.
A note on sent-only filtering
The Algominds dashboard is a reply management platform — not an outbound sending tool. Your inbox surfaces replies from prospects, not every email you've sent.
This is intentional.
- What appears: conversations where a prospect has replied to your outreach.
- What doesn't appear: sent emails that haven't received a reply yet.
If you need to see outbound sends that haven't been replied to, check the sending platform we run for you (Smartlead, Instantly, Algominds LinkedIn, etc.). The dashboard focuses on the reply side — what happens after we send.
Why this matters for views
Because the inbox is reply-focused, views like Needs Reply and Prospecting are populated by prospect response activity. A sent email with no reply yet won't show — it's not missing, it just hasn't triggered a reply-based view yet.
What labels surface in prospecting views
Prospecting views typically show active opportunities — conversations with engagement and potential forward movement.
The labels that actually surface depend on how the filters are set up, but the common patterns are:
| Label type | Typical view placement |
|---|---|
| Interested, Hot lead, Meeting request | Prospecting / Needs Reply |
| Follow-up, Needs info | Follow-up |
| Out of Office, OOO Sequence | Out of Office (timing view) |
| Not Interested, DNC, Block List | Not Interested / DNC (tracking only) |
| Warmup, Spam/Unwanted | Excluded from most active views |
Labels don't automatically create view membership. The table is a typical pattern, but your actual view behaviour depends on the filter rules you've configured. If a label isn't appearing where you expect, edit the view's filter to include it.
Quick troubleshooting checklist
When a view doesn't show what you expect, run through these:
- Check the filter conditions — does the filter include your label? Any extra conditions like message direction?
- Check the last message direction — is the prospect's reply the most recent, or did your team reply last?
- Check for exclusion labels — is there a NOT condition filtering out your label?
- Check for a prospect reply — if there's no reply from the prospect yet, the conversation won't surface in reply-focused views.
- Check sync status — very recent replies may take a few minutes to appear.
Still stuck after the checklist? Hit the Ask Algominds button and we'll dig in.
Need a hand with this?
Use the “Ask Algominds” button in the corner to send your question straight to our support team.