> For the complete documentation index, see [llms.txt](https://runtimedesigns.gitbook.io/token-buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://runtimedesigns.gitbook.io/token-buzz/product-guide/alerts.md).

# Alerts

Alerts let you define rules that fire automatically when a token's social buzz, sentiment, or price crosses a threshold you set. Triggered alerts land in an in-app inbox.

## Creating an alert rule

1. Go to **Alerts** in the sidebar (or navigate to `/alerts`).
2. In the **New rule** form at the top of the page, fill in:
   * **Symbol** — the token to watch (e.g. `PEPE`).
   * **Condition** — what should trigger the alert (see below).
   * **Threshold** or **Target** — the condition-specific value.
3. Click **Create alert**.

The new rule appears immediately in the **Active rules** list below the form.

## Alert conditions

### Buzz spike

Fires when the token's mention volume increases by at least the threshold percentage within the monitoring window.

* Set **Threshold %** to the minimum percentage increase that should trigger the alert (e.g. `100` means a 100% / 2× spike).

### Sentiment flip

Fires when the prevailing sentiment classification for the token changes.

* Set **Target sentiment** to the sentiment you want to detect: **Any** (fire on any flip), **Bull** (fire only when sentiment turns bullish), or **Bear** (fire only when sentiment turns bearish).

No threshold percentage is needed for sentiment flips.

### Price move

Fires when the token's price changes by at least the threshold percentage in either direction.

* Set **Threshold %** to the minimum move size (e.g. `10` means a 10% price swing).

## Managing rules

The **Active rules** list shows every rule you have created. For each rule you can:

* **Toggle enabled / disabled** — use the toggle switch on the right of the row to pause a rule without deleting it. A paused rule does not fire.
* **Delete** — click the × icon to permanently remove the rule.

## Alert inbox

The **Inbox** section below the rules list shows a history of every time your rules have triggered. Each item shows:

* A blue dot if the notification is unread.
* The trigger message describing what happened and by how much.
* A relative timestamp.

Clicking an inbox item marks it as read and navigates to the relevant page (e.g. the Movers page or the Live Feed filtered to that token).

Click **Mark all read** in the inbox header to clear all unread indicators at once.

## Email notifications

By default, alerts are delivered in-app only. To also receive an email when a rule fires, go to **Account → Notifications** and enable **Email me when an alert triggers**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://runtimedesigns.gitbook.io/token-buzz/product-guide/alerts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.