Too Few High Relevance Mentions

Matches show up, but most posts land as low relevance—or alerts rarely fire—because scoring or thresholds are strict.

Use this guide when the feed is not empty, yet few posts rise to “high” relevance, Slack or Discord pings rarely trigger, or you mostly see weak matches.

1. Sorting by “Recent” masks score

If you sort by Recent, you may scroll past high-relevance items that are slightly older. Switch to Most relevant when auditing whether scoring itself is the problem vs timing.

2. Listener Intent is too vague or misaligned

Scoring reads your Intent to decide what “good” looks like. If Intent is short, generic, or unrelated to your keywords, strong buyer threads can still score low.

Rewrite Intent so it names who you want, what situations (complaints, comparisons, switching), and what to prioritize.
Add or tighten Negative intent only for noise you truly want penalized—overly broad negative intent can drag down borderline-good posts.

3. Notification relevance cutoff is high

For Slack or Discord, each listener can require a minimum relevance before alerting. If that threshold is aggressive, you will see mentions in the feed but almost no notifications.

Lower the relevance bar for that listener, or test with alerts muted and scan the feed first. See Per-listener notifications and Relevance threshold.

4. Feed filters hide high-relevance rows

Confirm you have not narrowed the feed with relevance, sentiment, date, listener, or tag filters that exclude the rows you care about. Temporarily clear filters to audit what is actually scoring high.

5. Brand Context is thin or outdated

Brand Context grounds AI in who your company is. If it is empty, stale, or wrong after a pivot, relevance can feel arbitrary.

Update Brand Context after major positioning changes, or run Reanalyze on your website from AI Settings when copy has changed materially.

Not Getting Mentions — zero or near-zero volume.
Feed is noisy — opposite problem: volume is high but junk-heavy.