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.

A recovery is yours to run, but your members live through it too. The program keeps them informed in plain words, never asks them to pay again, and never asks them to do anything a person could not do in one tap. Here is everything they can see, in the order they usually see it.

While an incident is open

On the portal

Every visitor to your project's public portal — signed in or not — sees a calm notice above the plans: Access Is Being Restored. We are restoring access to this community right now. You do not need to do anything: the moment it is back, your new invite link is waiting for you in the bot and in the portal. It shows only for a bot or channel incident; your own account being unreachable changes nothing for the people in your channels, so it says nothing.

In the bot

A member who writes to your project bot while a bot or channel incident is open receives the same sentence as an automatic reply, ahead of any fixed acknowledgement you configured for the support inbox. Their message still lands in your inbox. (If the bot itself is the thing that was banned, Telegram delivers nothing at all in either direction; the portal notice is what they have until the bot is replaced.)

When a channel or group is replaced

Every member with active access receives, from your project bot:

🔁 Signals has moved

The channel you have access to was replaced with a new one. Your membership is unchanged — tap the button below to join it. Your join request is approved automatically.

🥰 Join "Signals" Channel

Tapping the button opens Telegram's join request; our bot approves it within a second. Nothing else is asked of them — no code, no payment, no re-registration.

Members the bot cannot reach — they bought through the portal and never started the bot, or the bot was banned in the same incident — still hold their new link. It appears:

in the portal, on their membership, the moment they open it;
in the bot, the moment they press Start;
by email, if you chose Email them for me — Signals has moved, with the same Join button and, when your project has a portal, a link to it. (Emails are sent from Subscriby and signed by our team, without a support reply-to, so a reply goes nowhere by mistake.)

A member who has not joined after a while may receive the same "has moved" message again when you press Remind Members Still Outside. It is the identical message with the identical link, so a member who already joined and taps it again simply lands in the chat they are already in.

Pass and pass-series holders

A time-limited pass or a pass series grants the resource for a window, not open-endedly, so the swap treats holders by where their window stands at that moment:

Holder	What happens
Inside a window that is open right now	Treated exactly like a live subscriber: a fresh personal link into the new chat, the has moved message with its Join button, automatic approval. They are back inside within a minute and counted in the roll call. When the window ends, they are removed from the new chat on time, because the window's schedule follows the resource, not the chat.
Holding a window that has not opened yet	Nothing arrives now. The link they were sent ahead of the date opened the old chat, so it is forgotten, and the ordinary pre-window sweep sends them a fresh link into the new chat before their window opens — the same message they would have received anyway. They are not part of this swap's roll call.
Holding a series with several dates	Each date is its own window, so both rows above apply date by date: today's date is re-admitted now, the remaining dates get fresh links ahead of time.
Whose window has already closed	Nothing. Their access ended before the swap, and a swap never grants access to anyone who did not hold it.

Holders are never charged again and their window never moves: a Sunday pass bought on Wednesday is still Sunday's pass, in whichever chat Sunday's channel turns out to be.

When a bot is replaced

Nothing arrives by itself: Telegram does not let a new bot message people who have not pressed Start on it. What members see depends on what you do next:

Your announcement — wherever you post it — asks them to press Start on the new bot. Once they do, the bot answers as your project's bot with all their links and subscriptions intact.
Email Your Members sends Your project's bot has moved with a Start button that opens the new bot, and the portal link when there is one.
The portal shows the new bot's Start button on every screen that used to show the old one.

Their subscriptions, invite links and payment history were bound to your project's bot record, which the recovery rebinds, so a member who presses Start finds everything exactly as it was.

When your Telegram account is relinked

Members notice nothing. Your account is how you sign in and are alerted; it plays no part in what they receive. Your creator bot's private chat with you moves to the new account, and that is all.

When a swap is undone

The members receive the same "has moved" message again, this time pointing at the previous chat, and are re-admitted there through the same queue. Members who never left the old chat are simply approved again; nothing is revoked from them.

What members never see

Any change to billing. No charge, no refund, no new invoice, no pause. Their renewal date does not move.
The old chat disappearing. The chat a recovery replaced is left as it is; only the links into it are revoked. If Telegram deleted it, it was gone before the recovery started.
Your reasons. No notice names a ban, a restriction or Telegram. Members are told that access is being restored and where to go — nothing about why.
Each other. Every link is personal and every message is a private one from the bot.

Example: a member's afternoon

Ana holds a monthly plan that grants Signals. At 14:07 Telegram bans the channel; she notices the chat is gone at 14:20 and writes to the bot: "Where did the channel go?" The bot answers at once: We are restoring access to this community right now… — and her message lands in your inbox anyway. At 14:13 (before she even asked) the swap had already sent her 🔁 Signals has moved; she scrolls up, taps Join, and is inside Signals II by 14:21. Her plan renews on the 3rd as it always did, and she never learns what the ban was about.

During a connector outage

When the platform refuses your bot outright — a revoked or regenerated token, a deleted bot — Subscriby treats the gap as a connector outage. Members who already hold access keep it; nobody is removed. Would-be members meet Temporarily Unavailable on every plan that unlocks a place on that connector, on the portal and in the bot alike, so nobody pays for access that cannot be delivered. When the connector answers again and the outage lasted an hour or more, every member whose paid access overlapped it has the lost time banked on their purchase automatically, as long as the project's Outage Compensation setting is on. A member on a one-time purchase sees their end date move; a member on a recurring plan keeps their renewal date and charges exactly as they were, and receives the banked time at the end of their membership, after the last period they paid for, because no payment provider lets a renewal move by a few hours. Each member hears it twice, in the bot chat and by email, and the same line then shows on their portal membership card and in the bot's subscription screen ("Outage credit: 3 hours added to the end of your membership"). As with every recovery notice, members are never told why: only that access is being restored and, later, that time was added.

What Your Members See

On this page