Introducing the Disaster Recovery Program

A creator we work with sells access to a picks channel, per slate. On a Sunday afternoon in August, with forty holders of that day’s pass inside, Telegram took the channel away. Not restricted — gone. Then, an hour later, the account they signed in with. Then the bot.

Nothing about their business had changed. Forty people had paid for something that no longer existed, the creator could not sign in with Telegram to tell anyone, and the only way back was a manual rebuild on both sides that took the better part of two days. We helped by hand. It was the worst kind of support ticket: one where the platform had no answer.

Today we are shipping the answer: the Disaster Recovery Program. It watches your account, your bots and your channels around the clock, tells you the moment Telegram takes one away, and lets you move to a new account, a new bot or a new chat from one calm page — with every paying member re-admitted automatically and your plans, subscriptions and payments untouched. It is included on every plan, including Free. On Growth, standby bots, standby channels with a live mirror of every post, a backup Telegram account and automatic failover turn a recovery into one click, or no clicks at all. Nobody else does this. That is the peace of mind the program is built for.

Three things Telegram can take away

Every membership on Subscriby stands on three Telegram objects, and each can be lost separately: the account you sign in with, the bot that serves a project, and the channels and groups that hold your content. Each is fixed differently, so the program treats them as three kinds of recovery, each with its own allowance.

You hear about it before your members do

Every project bot is probed hourly. Every channel and group is probed hourly, and every five minutes while a pass window is open or about to open. Your own account is checked every six hours. And the moment real work fails — an invite link cannot be minted after a sale, a join request cannot be approved — the resource is probed immediately.

Only a transition counts, so a ban is announced once, not once an hour. When something breaks, an incident opens, you receive an email and a Telegram message with a one-tap link into the recovery page, a banner appears across your dashboard, and a new project.resource.status_changed webhook fires for your automations. Members who write to your bot in the meantime are answered automatically — we are restoring access to this community right now, you do not need to do anything — and your portal says the same.

The recovery page

It is not a wizard. People who arrive there are usually panicking, so it is one page: what we detected at the top, the three kinds of recovery as cards below, and the fix for the detected one already open. Each recovery finishes with a roll call — Re-admitted 40 / 40 · Joined 33 — read live from the invite links as members come through them, a Remind button for anyone still outside, and a 24-hour Undo.

Members our bot cannot reach on Telegram — they bought through the portal and never started the bot, or the bot was lost in the same incident — still hold their new link; it appears in the portal and the moment they start the bot. You choose, per project, whether Subscriby also emails them, at $0.01 per email, added to your transaction fees, or whether you download the member list as a CSV and reach them your own way. Members the bot reaches cost nothing.

Everything ends with a report in your inbox and a line in the new Recovery History, where every incident and every recovery ever run stays, with its undo while the window is open.

Active Disaster Prevention, on Growth

Recovering fast is good. Not having to is better. Growth adds the things you set up before anything happens:

• A backup Telegram account, proven through the same handshake, that you can sign in from, that receives the alerts your lost account cannot, and that the page switches you to in one click.

• A standby bot per project, stored without a webhook so it receives nothing until it takes over, probed hourly so you know it still works.

• A standby channel or group per resource, already administered by our bot, so a swap needs no Telegram round trip.

• A live mirror. Every post you publish in a channel is copied into its standby as you publish it, so a failover lands members in a channel that already holds your content. Only channels are mirrored, and the page says why: a channel is content and a channel you lose takes every post with it; a group is conversation, and copying its members’ messages into an empty standby would be noise. Nothing can be read from a banned channel afterwards — not by us, not by Telegram Desktop — which is exactly why the mirror copies before.

• Automatic failover. A switch per project that lets the platform swap an unreachable channel for its healthy standby the moment we detect it, with nobody signed in. Because it runs while you sleep and the bot may be banned too, switching it on asks you to accept the $0.01-per-email fee for members the bot cannot reach. Every failover reaches you by email and Telegram with the roll call and the undo; every failover that could not run tells you why.

• A readiness checklist that scores all of it, with a Set Up button on every tile that is not yet in place.

Swap & Grant, for the moves that are not disasters

The same swap and re-admission are now available from the Resources table, for a healthy channel you simply want to move: Swap & Grant Resource. It spends no allowance and is filed as On Demand. A degraded resource is routed to the recovery instead, so the allowance cannot be sidestepped through a different door.

Fair use, said plainly

This program is not a way around Telegram’s Terms of Service, and we have zero tolerance for using it as one. Every surface that describes it says the same four things:

1. It exists for creators who lost access or were restricted through no fault of their own.

2. Each kind of recovery is self-service once per rolling 90 days. The kinds are counted independently; several channel swaps within 24 hours of the first count as one; automatic failovers count; on-demand swaps do not.

3. Anything beyond that goes through our support team, who audit the account, the content of the channels involved and the history of the bans before releasing another recovery, and tell you what they found.

4. A confirmed violation of Subscriby’s or Telegram’s terms — content Telegram removes for breaking its rules, or a pattern of bans for the same reason — means the recovery is refused and the account is restricted and closed under our Terms of Service.

A recovery tool that could be used to hop from one closed channel to the next would make every honest creator on the platform look like a bad actor to Telegram. Keeping the program tight is what keeps it available.

Availability

Detection and every recovery are included on every plan, Free included, from today. Active Disaster Prevention — the backup account, standby bot, standby channels, live mirror, automatic failover and readiness checklist — is part of Growth. Member emails sent on your behalf are $0.01 each, reported as transaction-fee units on the invoice you already read.

The full walkthrough, with a page for each kind of recovery and worked examples, is in the Disaster Recovery guide. Support can see the same ledger you see, so if you ever need a second recovery inside the window, the conversation starts from the facts.

We would rather you never open this page. If you do, it will be the calmest one in the dashboard.

See your readiness at app.subscriby.net/recovery