> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/statistics/ohlc-range-map-tm/faqs.md).

# FAQs

<details>

<summary><strong>Do I need to create separate alerts for every level?</strong></summary>

No. You only need to create **one** alert in the TradingView "Create Alert" dialog by selecting the indicator and choosing the `Any alert() function call` condition. This will funnel all enabled level crosses into a single alert stream.

</details>

<details>

<summary><strong>What does the alert message look like?</strong></summary>

A typical message follows this format: `[Ticker] ([Timeframe]): Price reached [Level Name] Level`.\
\&#xNAN;*Example:* `EURUSD (1D): Price reached Manipulation (+M) Level`

</details>

<details>

<summary><strong>Can I use these for Telegram or Discord bots?</strong></summary>

Yes. Because the indicator uses the `alert()` function, the dynamic messages can be sent via Webhook URL to any third-party automation service or bot.

</details>


---

# 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://docs.candelacharts.com/statistics/ohlc-range-map-tm/faqs.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.