> For the complete documentation index, see [llms.txt](https://www.degenbot.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.degenbot.wiki/everyday-use/notifications-and-preferences.md).

# Notifications and preferences

Control interruptions and understand the difference between viewing a market and filtering alerts.

There are two different layers: **Telegram notification settings** and **any preferences offered by the bot**.

### Telegram notifications

Check the conversation's mute setting, Telegram's **Notifications and Sounds**, and your device's notification permissions. Focus or Do Not Disturb settings may affect when you notice a message. Telegram's [official troubleshooting guidance](https://telegram.org/faq#troubleshooting) is the reference for app-specific problems.

Muting is useful when you want to review messages later without interruption. Blocking or stopping the bot prevents it from messaging you; do not use that as a substitute for cancelling a subscription.

### Bot preferences, where available

The live release may offer settings for instruments, stream selection, or other delivery preferences. Use only the options actually shown and read the save confirmation. This guide does not claim that every proposed filter is implemented.

A selected market in an analysis view may affect only the next analysis request. It does not necessarily change the automatic alerts you receive. Likewise, a preference for one stream does not prove that all other streams are disabled unless the interface confirms it.

Change one setting at a time so the effect is easy to understand. If a control has no description or confirmation, ask support before relying on it.

### Why alert frequency changes

A condition-based alert service does not have to send a fixed number of messages every hour. The active rules, eligible markets, delivery restrictions, and service health can all matter.

A quiet period is not proof that the bot is broken—but it is not proof that everything is healthy either. Check a fresh request and any service notice before drawing a conclusion.

### Notifications arriving late

Compare the message's observation and send times, where shown, with when you saw the notification. Keep that distinction in a support report. A late push notification does not establish when the bot detected the condition.

For a new menu that does not respond or an account that unexpectedly loses access, use **Help and account → Troubleshooting**.