Alerts are only as useful as the rules behind them. An alert system that fires constantly becomes noise. One that fires too rarely misses incidents that compound while you’re looking the other way. This guide covers the event types worth alerting on, how to set thresholds that aren’t overwhelming, and what to do when an alert fires.
The four alert event types
AI visibility monitoring surfaces four fundamentally different types of events. Each warrants a different urgency and response.
1. Brand safety events
What triggers them: An AI engine generates a response containing a factually incorrect claim about your brand — wrong pricing, wrong features, discontinued products described as current, fabricated incidents, or harmful associations.
Why they’re urgent: Brand safety issues spread. A user who asks ChatGPT about your pricing and gets a wrong answer doesn’t flag it — they just form the wrong impression, or worse, share it. Most brand safety events go uncorrected for weeks unless you’re actively monitoring.
Recommended setting: Alert immediately on every new detection, regardless of severity score. You want to know about every instance.
Initial response: Document the exact query, engine, and response text. Assess severity (pricing error vs. minor description inaccuracy). Escalate to the fixing workflow described in the remediation guide.
2. Position drift events
What triggers them: Your brand’s position tier in an AI response drops — moving from first mention to prominent mention, or from prominent to listed, on a tracked query or query cluster.
Why they matter: Position drift is a leading indicator, not a lagging one. If you catch it in the first week, a content refresh is usually sufficient. If you catch it after 6 weeks, a competitor has likely built entrenched authority you’ll need more time to overcome.
Recommended setting: Alert when your brand drops one tier on any query that accounts for more than 5% of your tracked query volume. For your highest-priority query clusters, alert on any tier drop. For long-tail queries, alert only on two-tier drops (first mention → listed or worse).
Initial response: Compare the current response to the previous week’s stored response. Identify whether a competitor gained ground or your content simply aged out of preference. Assign to the position drift remediation workflow.
3. Visibility score threshold events
What triggers them: Your composite visibility score drops below a defined threshold, or drops by a defined magnitude within a defined window (e.g., a 5-point drop in 7 days).
Why they matter: Score-level alerts catch systemic issues that affect many queries simultaneously — model updates, broad competitive shifts, or a piece of content that many queries depended on getting deindexed or changed.
Recommended setting: Alert if score drops more than 5 points in a 7-day window (sudden change) or more than 10 points in a 30-day window (slow erosion). The first catches acute events; the second catches gradual decay you might miss in daily charts.
Initial response: Check whether the drop is localized to one engine, one query cluster, or one content source. A broad multi-engine drop usually signals a model event. A narrow drop to one query cluster usually signals a content or competitive issue.
4. Competitor gain events
What triggers them: A monitored competitor moves to first mention on a query where you were previously first, or gains significant share of voice on a query cluster you’ve been winning.
Why they matter: A competitor gaining position is not the same as you losing it — it tells you the direction of your next content investment.
Recommended setting: Alert when a tracked competitor achieves first mention on a query cluster where your brand was first-mentioned in more than 60% of recent runs. For share of voice, alert on a gain of 10+ percentage points on any cluster.
Initial response: Identify the specific competitor page driving the gain. Read it. Understand what it does better than your current content for that query context.
Threshold design principles
Calibrate to your query volume. If you’re tracking 50 queries, a single query’s fluctuation means less than if you’re tracking 500. Set tier-drop thresholds as a percentage of your tracked queries, not as absolute counts.
Separate Slack from email. Use Slack for events that need same-day attention (brand safety, sudden visibility drops, major position losses on key queries). Use email digest for slower-moving events (week-over-week position trends, competitor gains on secondary queries). Mixing both at the same urgency level trains you to ignore one.
Use mute windows intentionally. If you know a model release is happening or you’ve just published a major content refresh, mute certain alert types for 48–72 hours to avoid reacting to transient fluctuations before patterns stabilize.
Review your alert rules quarterly. What triggers a meaningful alert changes as your query set, competitor landscape, and content footprint change. An alert rule set in month one may be generating noise by month six.
Alert triage workflow
When an alert fires, the goal is to answer three questions within 24 hours:
1. Is this real or transient? AI engines produce variable outputs. Run the triggering query 3–5 more times. If the position or safety issue appears consistently across multiple runs, it’s real. If it appears in 1 of 5 runs, it may be temperature-driven variation rather than a true shift.
2. What specifically changed? Use the stored response diff to identify exactly what is different about the AI response now versus the baseline. A different competitor? A different source being cited? New phrasing in your brand description?
3. Who owns the remediation? Position drift → content team. Brand safety → brand/comms + content team. Competitor gain → content strategy + SEO. Score drop → investigate root cause before assigning.
Document this triage in your tracking system before closing the alert. Patterns across multiple alerts — the same competitor gaining repeatedly, the same query cluster generating consistent drift — are worth more than any single alert.
What not to alert on
Minor sentiment fluctuations. Sentiment scores fluctuate naturally as AI responses vary. Alert on sustained negative trends (e.g., negative sentiment on more than 30% of runs for 3+ consecutive days) rather than individual neutral or slightly-negative responses.
New competitor mentions. A competitor appearing in a response you also appear in is not an emergency — it’s normal. Alert on competitive gains (they move ahead), not competitive co-presence.
Single-run anomalies on low-priority queries. High-temperature AI responses produce outlier outputs. Don’t let a single unusual response to a query you don’t prioritize generate alert noise that dilutes your attention for real events.