> 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/help-and-support/raybot-and-telegram-rate-limits/setting-up-a-backup-bot.md).

# Setting up a backup bot

Route notifications through a reserve bot when your main bot is rate-limited.

### **What Are Backup Bots?**

Backup Bots keep your tracking running if the main bot gets rate-limited by Telegram. When that happens, your messages are automatically sent to your Backup Bots instead.

***

### **🌟 How to Set Up Backup Bots**

1. Send the command `/backup` in RayBot.
2. Follow the prompts to **add a few Backup Bots**.
3. Done — your alerts will switch to the Backup Bots automatically if the main bot is rate-limited.

***

### **💡 Why Use Backup Bots?**

* **No missed transactions**: Alerts keep arriving even if your main bot hits Telegram's limits.
* **No manual switching**: Alerts transfer to your Backup Bots automatically.

***

### **📢 What’s Coming Next?**

Right now, Backup Bots are available for **direct messages (DMs)**. Support for groups is planned.

***

For questions or help setting it up, send us a message via RayBot.


---

# 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/help-and-support/raybot-and-telegram-rate-limits/setting-up-a-backup-bot.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.