> For the complete documentation index, see [llms.txt](https://docs.raybot.app/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raybot.app/start/telegram/interface-navigation/signals.md).

# Signals

The **Signals** section brings all signal alert types together in one place. Here you manage three notification types that detect unusual or notable wallet behavior.

**📌 What's inside Signals**

* **🤝 Multi Wallet** — multiple tracked wallets buying the same token
* **🔴 Accumulation** — one wallet repeatedly buying the same token over time
* **⚠️ Unusual Behavior** — off-hours buys or oversized positions

Each signal type is configured independently — with its own presets, filters, and trigger thresholds.

***

**🔔 Show "non-signal" alerts**

This setting controls whether regular transaction notifications come through alongside your signal alerts.

✅ **On** — you receive both regular notifications and signals (Multi Wallet + Accumulation + Unusual Behavior)

❌ **Off** — only signals come through; regular notifications are suppressed

{% hint style="info" %}
💡 If you're focused purely on signals and don't want noise from every individual transaction — switch this to **Off**.
{% endhint %}


---

# 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://docs.raybot.app/start/telegram/interface-navigation/signals.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.