> ## Documentation Index > Fetch the complete documentation index at: https://docs.attensira.com/llms.txt > Use this file to discover all available pages before exploring further. # Alerts: a rival moves, or you are named for the first time > The two alerts Attensira sends as they happen: a rival starting to be named on one of your questions, and a win. What triggers each, where they go (email, Slack), how often, and how to counter a rival or share a win from the alert itself. Most of what Attensira tells you waits for the [morning brief](https://docs.attensira.com/agent/morning-brief.md). Two things do not, because they are worth knowing the hour they happen: | Alert | What triggers it | What you can do from it | | - | - | - | | **Rival alert** | A rival started being named in AI answers to one of your questions, on at least two of the last three days, and on none of the earlier days we read. See [Rival alerts](https://docs.attensira.com/agent/rival-alerts.md). | **Counter it**: put a counter-move in your queue as a change | | **Win alert** | An engine named your brand, or linked to your site, in an answer to one of your questions for the first time since we started reading it. See [Wins](https://docs.attensira.com/agent/wins.md#the-instant-win-alert). | **Open the share card**: the win's own card page, to post it | Both say only what the answers did, counted over the days we read. Neither says why. ## When they arrive Each alert is written in the hourly pass that finds it, not the next morning. It reaches your inbox or Slack within 24 hours of detection, and usually within minutes. [Quiet hours](https://docs.attensira.com/account/notifications.md#quiet-hours) can hold your email copy until your window ends; the Slack post is never held. ## Where they go | Alert | Email | Slack | | - | - | - | | Rival alert | Always, as an **Attention** email | Also posted to the workspace's Slack channel, when the workspace sends the Monday note or the win message there | | Win alert | When **Settings → Notifications → Wins** includes Email | When **Wins** includes Slack | Each person on the workspace gets their own email copy according to their own [notification preferences](https://docs.attensira.com/account/notifications.md#who-gets-email): the owner by default, teammates once they turn the category on. A rival alert is an Attention email; a win alert is a Wins email, and the **Wins right away** switch (off means "in the Monday note only") holds it back too. **If Slack cannot take it, you get it by email.** A Slack post that keeps failing, or a Slack connection that is gone, is sent by email instead after the last attempt, and the Inbox asks you to reconnect Slack. You get the alert once by email even if it was meant for Slack only. ## How often * **One rival alert per question, rival and day.** The same rival starting to be named on the same question on ChatGPT and on Perplexity in one day is one alert, not two. A different rival, or a different question, is its own alert. On top of that, a rival is alerted at most once a week for each question and engine. * **One win alert per question and day.** Being named for the first time on three engines for one question in one day is one alert. * **The day's win message still comes.** The win alert tells one win as it happens. The [win message](https://docs.attensira.com/agent/wins.md#the-win-message) is the day's roundup of every new win, at most once a day, and arrives as before. Switch the Wins email to the Monday note only to stop both. ## Counter a rival Every rival alert has one action, **Counter it**. It files one planned change in your queue to answer the rival on that question: a comparison page, or a pitch to a deciding source (see [how agents choose](https://docs.attensira.com/measure/playbook-win-rates.md#counter-it)). The change waits for your yes like every other change. A page that names a rival is always a claim, so nothing from it is published without one. You can counter from wherever the alert reached you: | Where | How | | - | - | | Email | Press **Counter it** under **Decide from here**. It opens a page that says what it will do; press **Counter it** there to confirm. Or reply **counter it** (or **yes**). See [Reply to act](https://docs.attensira.com/account/reply-to-act.md). | | Slack | Press **Counter it** on the alert, or reply **counter it** in the alert's thread. A button press counts as the person who pressed it. See [Slack](https://docs.attensira.com/account/slack.md). | | The app | **See the rival** opens the prompt's drill-down on the [Scoreboard](https://docs.attensira.com/tracking/scoreboard.md#in-the-app), with the alert and **Counter it** on top. | | API and MCP | `act` with the alert's ref (`attensira://{workspace}/alert/{id}`) and `action: counter`, or [`POST /v1/alerts/{id}/counter`](https://docs.attensira.com/api/endpoints#post-/v1/alerts/\{id}/counter). | However many times, and from however many places, a rival alert is countered, it files one change. A rival alert has nothing to decline: if you do nothing, nothing happens. A reply of "no" or "undo" changes nothing and says so. ## Share a win A win alert links the win's share card, a public page with your brand, the engine, the question, the quote and the date. Open it to post the card or copy its link. The link turns off when you unshare or dismiss the win. See [Sharing a win card](https://docs.attensira.com/agent/wins.md#sharing-a-win-card). A win alert with no share link is not sent; the day's win message still tells the win. ## For agents and integrations The alerts are one more reader of the same events your integrations can subscribe to: [`rival.gained`](https://docs.attensira.com/api/webhooks#events) and [`win.detected`](https://docs.attensira.com/api/webhooks#events) (the win's alert is in its `alert` field). Over MCP, `subscribe` with those events gets the same news, and `act(alert, counter)` counters a rival. Stopping an alert is done in [Notifications](https://docs.attensira.com/account/notifications.md), by a person. An assistant can ask to change your notification preferences, but that only files a proposal you accept or decline. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.