> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/telegram-and-promotion/43-token-alerts.md).

# 43. Token alerts in Telegram

Get a private Telegram message when a token's market cap moves or its bonding curve reaches a milestone.

**Open:** any token page on [the Spawn Feed](https://spawnmeme.com/launchpad) and tap **Alerts**, or message [@spawnmeme\_bot](https://t.me/spawnmeme_bot).

## Before you start

* Alerts cover SPAWN tokens that are still on their bonding curve. Graduated tokens are not covered.
* Alerts arrive in a private chat with the bot, so you need Telegram.
* Checks run every five minutes. A message can arrive a few minutes after the move.
* You can have 20 active alerts.
* Alerts are information, not advice.

## Set an alert

1. Open the token page and tap **Alerts**. Telegram opens a private chat with the bot.
2. Press **Start** if Telegram asks.
3. Choose one:
   * **Up 25%** or **2x**: one message when the market cap reaches that level.
   * **Down 25%**: one message if it falls that far.
   * **Curve milestones**: a message at 25%, 50% and 75% of the bonding curve, and again at graduation.
4. The bot confirms the alert and the level it is watching.

Price alerts are measured from the market cap at the moment you set them, and each sends once. You can also send `/alert` followed by a mint address to the bot.

Launched a token? Choose **Curve milestones** on your own token page to follow its progress.

## See or remove alerts

Send `/alerts` to the bot in the private chat. Tap an alert in the list to remove it.

## Troubleshooting

| Symptom                                            | What to do                                                                       |
| -------------------------------------------------- | -------------------------------------------------------------------------------- |
| The bot replies in a group that alerts are private | Tap **Open alerts** and continue in the private chat.                            |
| "The price for this token has not been read yet"   | Try again in a few minutes.                                                      |
| "You already have this alert"                      | Each token and alert type can be set once at a time.                             |
| "You can have 20 active alerts"                    | Send `/alerts` and remove one first.                                             |
| No message arrived                                 | Check you have not blocked or muted the bot, and remember the five-minute check. |
| Your alert ended at graduation                     | Price alerts stop when a token graduates. The bot tells you when that happens.   |

**Success:** the bot confirms the alert, and `/alerts` lists it.

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Telegram command reference](/spawnmeme-docs/feature-guides/reference-and-support/36-telegram-commands.md) · [Trade on a token page](/spawnmeme-docs/feature-guides/discover-and-trade/13-token-trading.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/telegram-and-promotion/43-token-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.