The firehose problem
A viral video can dump dozens of "high-intent" comments in an hour. Not all of them are real. And the same person asking the same question five times should not ping your sales channel five times.
Rules by scope
VocLens lets you set noise rules at three levels of precision:
| Scope | Matches | Use it for |
|---|---|---|
| Channel | every comment on a channel | "this channel is mostly tire-kickers" |
| Video | a single video | "the Q&A / giveaway video — don't push" |
| Commenter | one person's channel ID | "this account spam-comments daily" |
The most specific rule wins: a video rule overrides a channel rule, which overrides a commenter rule.
Three ways to quiet the noise
- Mute — block every auto-push in that scope. The simplest and the most used.
- Throttle — cap pushes to, say, one per commenter per 24 hours, so repeat askers don't drown the signal.
- Digest — roll every high-intent lead in a window into a single summary card with counts and top links, instead of N separate pings.
Why it matters
Rules only touch the automatic path. When you manually push a lead, it always sends. You stay in control of the exceptions while the firehose gets filtered for you.