> 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.md). # Overview Every button in the Telegram interface leads to a specific feature or action. This documentation is built to match the bot 1:1. That means:\ **Every button in RayBot has its own section here.** *** ### **📲 What you see in Telegram:**
**The main menu includes buttons like:** * [**✨Add**](/start/telegram/interface-navigation/add.md) * [**👀Wallets**](/start/telegram/interface-navigation/wallets.md) * [**🪙Tokens**](/start/telegram/interface-navigation/tokens.md) * [**🆕Multi Wallet**](/start/telegram/interface-navigation/signals/multi-wallet.md) * [**⚙️Settings**](/start/telegram/interface-navigation/settings.md), etc. *** ### 📚 What you’ll find in the docs: **Each button has its own dedicated section. Inside, you’ll find:** ✅ Feature overview\ ✅ How it works\ ✅ Examples\ ✅ Interactive video guides *** ### 🔍 How to use this documentation: 1. Tap a button in the Telegram bot 2. Go to the section with the same name in this doc 3. Find everything related to that feature in one place {% hint style="info" %} **💬 Looking for a command?**\ Check the [**Command Reference**](/start/getting-started/command-reference.md) section — every command is explained there. {% 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.md?ask=&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.