Alert Badges — Intercepted, Dropped, Low Visibility and Context
What the badges on Prompt Tracking rows mean, the rule behind each, the +N counter, the keyword alert dialog, data gaps, how alerts reach the bell, email and Slack, and how they clear.
The badges
| Badge | Rule | Priority |
|---|---|---|
| Intercepted | An engine's latest scan did not mention you and named at least one competitor | Conversion risk |
| Dropped | Not mentioned now, mentioned on that engine's previous scan | Urgent if you were in the top 3, otherwise high |
| Low visibility | Not mentioned and no competitor named either, or your position slipped by a full place | Urgent below 30% coverage |
| Context | Mentioned, but described as the wrong kind of company, off-topic, or in the wrong language | Watch |
A row shows its most severe badge, with +N for the rest. Order: intercepted, dropped, low visibility. Engines that errored or hit a quota never raise alerts. Alerts come from real scan data; unchecked prompts have no badge.
The alert dialog
Clicking a badge opens Keyword alerts: one entry per engine with a title and explanation, and a red dot on interceptions. The dialog reminds you that engines usually take days to weeks to reflect a fix; after publishing, re-check with Scan now.
Data gaps
When at least half of one engine's latest checks returned no answer, the alerts show a single data-gap item for that engine. It is a collection problem, not a visibility drop: those results are left out of the mention rate for now and filled in once collection recovers. Data gaps appear in the app only and are never emailed or sent to Slack.
What to do
- Intercepted: read the evidence, see which sources the engine cited for the competitor, then generate a strategy article for that prompt cluster or fix the cited sources (Citation Sources → View fix / Outreach). These also show up as competitor-ahead tasks in This week’s tasks on the Workspace.
- Dropped: check whether the page that earned the mention changed or went offline; republish and ping indexing from Integrations. First check the Workspace for Platform-wide changes to rule out the platform.
- Low visibility: a content gap; create a page that answers the prompt directly.
- Context: correct the Business info in Content Rules, then use "Fix n misidentifications" to generate one clarifying article for every mismatched prompt.
Bell, email and Slack
New alerts always reach the bell in the top bar (prompts intercepted by competitors, prompt visibility dropped). Email and Slack are set per project under Settings → Email Notifications → Project alert notifications: Competitor Intercept and Visibility Anomaly each go to email and/or Slack (incoming webhook), Instant or as a Daily or Weekly digest, with optional quiet hours. The Visibility Anomaly switch also covers high-risk brand-search errors and agent readiness drops. Emails are sent in your account's interface language. See Notifications.
Clearing
Badges are recomputed from the latest scan: they disappear when the next scan mentions you (intercepted, low visibility), the position recovers (dropped) or the verdict is match (context). A resolved interception shows up in Achievements as "interception beaten".
Was this article helpful?