Too Few High Fit Score Mentions

Use this guide when the feed is not empty, yet few posts rise to a high Fit Score, 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–Fit Score items that are slightly older. Switch to Fit Score (high to low) when auditing whether scoring itself is the problem vs timing.

2. Listener Intent signal is too vague or misaligned

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

• Rewrite Intent signal so it names who you want, what situations (complaints, comparisons, switching), and what to prioritize.
• Add or tighten Noisy signals only for noise you truly want penalized—making Noisy signals too broad can drag down borderline-good posts.

3. Notification Fit Score cutoff is high

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

• Lower the threshold for that listener, or test with alerts muted and scan the feed first. See Per-listener notifications and Fit Score threshold.

4. Feed filters hide high–Fit Score rows

Confirm you have not narrowed the feed with Fit Score, sentiment, date, listener, or intent 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, Fit Scores can feel arbitrary.

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

Related

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