Allowances and Support Review
How the once-per-kind-per-90-days allowance is counted, what does and does not spend it, what you see when it is spent, and what our support team audits before releasing another recovery.
The program's promise to Telegram, and to every honest creator on the platform, is that it cannot be used to hop from one banned channel to the next. The allowance is how that promise is kept.
The rule
Each kind of recovery — Telegram Account, Project Bot, Channels and Groups — is self-service once per rolling 90 days, counted per creator and per kind independently:
- Using one kind never reduces another. You may run all three in one sitting, or one today and the others next month.
- The window is rolling: a channel recovery run on 1 March opens again on 30 May, whatever else happened in between.
- The count is taken from the moment a recovery starts, not from when it finishes, so a recovery that never finished still counts (and a recovery that failed before changing anything gives its use back).
What spends the allowance, and what does not
| Spends it | Does not |
|---|---|
| Relinking your Telegram account, by handshake or by switching to the backup account. | Registering or removing a backup account. |
| Replacing a project bot, by token or by switching to the standby. | Registering or removing a standby bot. |
| The first channel swap of a channel recovery — and every automatic failover. | Further swaps within 24 hours of the first: they join the same recovery and count once. |
| A swap of a degraded resource from the Resources table (it is routed to the recovery). | A Swap & Grant Resource of a healthy resource: on demand, never a recovery. |
| Undoing a recovery. Undo is not another recovery. | |
| Running a recovery when nothing was detected — it spends the allowance like any other, but it is allowed. |
What you see when it is spent
The recovery card for that kind shows Used on date — support review instead of Self-Service Available, and its step opens with Support Review Required: You already used the self-service channel recovery inside the current 90-day window. Our support team reviews the account and its content before releasing another; a confirmed violation of Subscriby's or Telegram's terms closes the account. The Contact Support button opens the support chat with the incident, the kind and the project already attached, so you do not have to explain what happened.
The other two cards are unaffected and say so.
What support audits
When you ask for another recovery inside the window, a person looks at:
- the account — how long it has existed, its billing standing, previous incidents and recoveries;
- the content of the channels and groups involved, as far as it can still be seen (the live mirror, the portal, your plans and their descriptions);
- the history of the bans — how many, how close together, and whether Telegram's stated reason points at content or at a pattern.
They tell you what they found. If the bans read as errors, reports by a competitor, or a pattern that is not yours, they release a grant: one or more extra uses, for one kind or any kind, optionally with an expiry, with their note and their name kept on your history page. The grant is spent before any refusal, exactly like the self-service allowance.
A confirmed violation closes the account
If the audit finds you directly violating Subscriby's or Telegram's terms — content Telegram removes for breaking its rules, or a pattern of bans for the same reason — the recovery is refused and we take the necessary steps to restrict and, under our Terms of Service, close the Subscriby account. You are told by email why, and your members are told that the project has ended. There is no appeal path inside the program; the program is not for that.
Where the numbers come from
config('subscriby.recovery') holds the window (90 days), the self-service uses per kind (1), the absorption grace (24 hours) and the undo window (24 hours). They are deliberately tight; a change needs no deploy, and every page reads the live values rather than repeating them.
Integrations read the same allowances at GET /v1/recovery/allowances, one row per kind with allowed, uses_grant and next_self_service_at already worked out, and an agent through get_recovery_allowances.
Example: three creators, three outcomes
- Maya had her channel banned in March and swapped it herself. In May a second channel is banned. The card says Used on 12 March — support review. Support finds both channels were reported by the same account with no rules problem, releases one channel-kind grant valid for 30 days, and Maya swaps the second channel the same afternoon. In June, 90 days after 12 March, her self-service allowance returns on its own.
- Dev runs a channel that Telegram removed for content it does not allow, replaced it, and two weeks later the replacement is removed for the same reason. Support's audit finds the reason in Telegram's own message and the same content in the mirror. The recovery is refused and the account is closed under the Terms; his members are told the project has ended.
- Lina never touched the allowance: on Growth, her standby channel with automatic failover took over when her channel was banned, which spent the channel-kind allowance automatically. Her account and bot allowances are untouched, and the page tells her the date the channel one returns.
How is this guide?
Active Disaster Prevention
The Growth-only safeguards that turn a recovery into one click, or no clicks at all — a backup Telegram account, a standby bot, standby channels with a live mirror, automatic failover with its email-fee consent, and the readiness checklist.
What Your Members See
Every message, notice and email a subscriber can receive while a recovery is open or after it completes — so you know what they know, and what they are asked to do.