Standby Bots and Automatic Failover
The part of Disaster Recovery you set up before anything happens: a second bot, mirrored standby places and a backup account, switched to with one click or no clicks at all
Recovery on every plan gets you back in a few clicks; prevention on Growth means you may never need those clicks. Each project keeps a second bot stored without being registered, each place keeps a standby of the same kind, a broadcast place's standby can mirror every post as you publish it, and your creator account keeps a backup you can sign in from. Switch on automatic failover and Subscriby swaps to the standby the moment a ban is detected, then tells you what it did. That is the peace of mind the program is built for.
- Included on
- Growth
- No addon to buy; a readiness checklist shows what is still unprotected before anything goes wrong.
- Standby bot
- One per project
- A second set of credentials, stored but not registered, so it receives nothing until it takes over.
- Standby places
- One per place
- Handed over on the platform in advance; a broadcast place's standby can mirror every post the moment it is made.
- Automatic failover
- One switch per project
- A banned place or a refused bot is swapped for its healthy standby with nobody signed in; each failover counts as a recovery.
- Probes
- Every 15 minutes
- Bots, places and standbys are checked on that cadence, and every member's access is re-verified as often.
- Undo
- 24 hours
- A place failover can be undone like a manual swap; a bot switch cannot.
What prevention adds
A bot that is already waiting
The standby bot's credentials are stored without being registered, so it receives nothing and the platform never sees it act until it takes over; when the live bot is refused, the standby's credentials are written in, every member chat follows, and checkout is back within minutes.
Places with your posts already in them
A standby place of the same kind is handed over in advance. With the live mirror on, every post is copied into the standby the moment it is made, edits included, so a swap lands members in a place that holds everything you published since you switched it on.
Failover while you sleep
With the switch on, a place the platform reports as gone or a bot it refuses outright is swapped for its healthy standby automatically; members are sent a personal link to the new place, or emailed the new bot, and you read the report in the morning.
A way back into your own account
A backup account is proven through the same handshake as a relink and registered in advance; if the platform deactivates the account you sign in with, the alert reaches the backup and one button switches to it.
How to set it up
- 1
Open Disaster Recovery in your dashboard; on Growth the Active Disaster Prevention section and its readiness checklist are live.
- 2
Register a backup sign-in account: generate a link or a code, open it from the second account, confirm.
- 3
Store a standby bot for each project: create the bot on the platform and paste its credentials; it stays unregistered until it is needed.
- 4
Add a standby for each place, hand it over on the platform, and switch on Mirror Content for the places you broadcast in; nothing is backfilled, so do it early.
- 5
Switch on Automatic Failover per project and accept the $0.01 per email for members the bot cannot reach; every tile the platform can verify turns green.
Best for
- Communities that cannot afford an hour offline
- Signal, trading and news channels whose posts are the product
- Creators running several projects who want the switch made for them
Goes with
The features creators switch on beside this one.
Fair Use Guidelines — Not a Bypassing Tool
The program is a temporary bridge for creators who lost access through no fault of their own. Keeping it tight is what keeps it available: a tool that could hop from one banned place to the next would make every honest creator on Subscriby look like a bad actor to the platforms it runs on.
- 1
It exists for creators who were banned or restricted through no fault of their own. It is not a way around Telegram's rules, and there is zero tolerance for using it as one.
- 2
Each kind of recovery is self-service once per rolling 90 days, counted separately for the account, the bot and the places.
- 3
Anything beyond that goes through the support team, who audit the account, the places involved and their content, and the history of the bans, and tell you what they found.
- 4
A confirmed violation of Subscriby's or Telegram's terms closes the account: the recovery is refused, you are told by email why, and your members are told the project has ended.
Common Questions
Read the guideDoes automatic failover need me to be online?
No. That is the point of it: with the switch on, a healthy standby and an allowance left, the swap runs the moment the incident opens, and you are told by email and on your connected account what happened, with the roll call and, when it was a place that moved, the undo.
What is mirrored, and from when?
Every post made in a broadcast place after you switch the mirror on: text, media and edits, copied the moment they happen. Nothing is backfilled, so the earlier you switch it on the more the standby holds; a conversation place gets a standby and failover but no mirror.
Does a failover count against the allowance?
Yes, exactly like a manual recovery: once per kind every 90 days. If the allowance is spent, the failover does not run and you are told why, so you can contact support.
What does prevention cost?
Nothing beyond Growth. The only charge is $0.01 per email for members the bot cannot reach during a failover, which you accept when switching it on.
What if I leave Growth?
You are asked to remove the standbys, the failover switch and the backup account first; nothing is ever deleted on a downgrade, because silently dropping a safeguard would leave you believing you are covered when you are not.
Start Free — Add Prevention When You Grow
Free plan includes 3 projects. No monthly fee — card on file required to charge transaction fees.
Set Up Free in 30 Minutes