Introducing Revenue Recovery

Revenue Recovery is here. It is the feature you asked us for more than any other, and it is finally live in Subscriby 5.0.14. A failed renewal keeps the member’s access while they fix the payment, a member who cancels is asked why and made one offer, and a member who left, a lead who never bought, a checkout that stalled and a trial about to end each hear from you in your own words, on the days you chose. Every recovered renewal and every recovered checkout is counted, with what it was worth, and the reasons members leave are drawn as bars you can act on. It runs on the dashboard, in the bot, on the portal, on the REST API, the MCP server, webhooks, Zapier and n8n, from today.

Here is the one-sentence version: most members who stop paying never decided to leave, and from today your project notices, keeps the door open, and asks them back.

And the one-sentence version for the number-minded: a revenue recovery system this complete, with a churn analysis beside it, is not available on any other Telegram membership platform today. More on that below.

The Short Version

• A grace window when a renewal fails. You set it, per project, from zero to 30 days. The member keeps their access while the gateway retries and is let straight back in by the first charge that settles.
• A ladder of four notices, each with the payment method’s own link to pay again: at the failure, on day 3, the day before the window closes, and once when access pauses. Where the member already is: their chat or their email.
• A cancellation screen that asks why, from ten reasons and Other in the member’s language, takes a sentence if they want to write one, and makes one offer the member’s payment method can honour: a billing cycle on hold, a discount on the renewals, or a coupon to come back with.
• Recovery sequences in your words: up to 8 steps, up to 180 days apart, with the member’s name, your project, the coupon and the way back filled in, on four moments: a member who left, a new lead, a checkout that stalled, a trial about to end. A starter writes the first three steps for you.
• A checkout ledger. Every checkout a member starts on your portal or in your bot is written down; one that stays open past your window with no payment counts as stalled, and the ones that come back are counted with what they brought.
• Churn analysis. Why members cancel as bars, which offers were shown and taken, the leads who arrived and bought, the trials reminded and kept, and a ledger of every notice, offer and message with whether a payment followed. The same figures on the project dashboard, in the exports, and in a daily digest to your chat.
• A Stop for the member on every message, a button in the bot and a one-tap link in an email, and a switch in their portal account settings.
• Everywhere Subscriby is: a Revenue Recovery page with five faces, a 💸 Revenue Recovery screen in the bot, the Revenue Recovery and Recovery Sequences APIs, 12 MCP tools, 15 webhook events, and the same operations on Zapier 4.3.0 and n8n 4.3.0.

Why Revenue Recovery

Look at the members your project lost last quarter and most of them did not decide anything. A card expired. A bank declined a renewal at three in the morning. A wallet ran short on the day. The tool saw a failed charge, removed the member from the channel, and nobody told them why the group went quiet. The member assumed something broke, or that you cancelled them, and did not come back.

Then there is the second group: the people your project already knows and who never paid. Everyone who opened your bot, signed in to your portal or followed one of your Smart Links is in it. They tapped Pay and stopped at the gateway. They took a free trial and let it lapse. Online stores win back a tenth to a fifth of abandoned carts with a few timed messages; a membership tool that writes a stalled checkout down and follows up is rarer than it should be.

Revenue Recovery turns both silences into something you can see and act on. It does not charge anyone again, ever; your gateway holds the card and retries on its own schedule. It keeps the member’s access while that happens, tells them with the gateway’s own link, asks the ones who cancel why, and reaches the ones who left or never arrived in your words. And it writes every step down, so you know what came back and why members go.

When a Renewal Fails: the Grace Window and the Ladder

A renewal that fails on a recurring membership opens a grace window you set per project, from zero to 30 days. A new project starts at zero, which pauses access at the failure as before, so nothing changes until you choose a window. Once you do, the member keeps every place and perk their membership grants while the gateway retries, and the clock starts at the first failure and never restarts on a failed retry, so a card that keeps declining does not keep the window open.

Four notices go out, each carrying the payment method’s own way to pay again: a Stripe invoice page, a PayPal autopay page, a Paystack or Razorpay checkout, or the portal where a rail has no page of its own.

1. At the failure, within minutes, where the member already talks to your project: their chat, or their email when that is where they asked to hear from you.
2. On day 3, a reminder.
3. The day before the window closes, a last warning.
4. When access pauses, one notice saying so, and that a settled payment opens the door again.

The ladder stops the moment a charge settles. A payment that lands on day two of a seven-day window restores nothing, because nothing was taken away; one that lands after the pause lets the member straight back in with fresh links and a welcome back, and counts as a recovery. A trial that was never paid is removed at once, as it always was, and a one-time purchase never enters grace: it ends at the close of its window, and the renewal reminders and the portal are its way back.

When a Member Cancels: One Question, One Offer

Cancelling now opens a screen before the cancellation goes through. It asks why, from ten reasons and Other in the member’s own language, with an optional sentence in their words. Then it makes one offer, the one the member’s payment method can keep:

• A pause: one billing cycle on hold, where the gateway can hold a charge. It ends by itself, with fresh links and a welcome back.
• A discount on the renewals, where the gateway can carry a coupon.
• A coupon to come back with, which works on every payment method.

The member takes it or passes. Passing cancels as before, keeping their access until the period ends, and the pass is counted so you know how often the offer works. Every answer is written down for you. The question runs on every plan; the three offers are on Growth, or on any plan with the Revenue Recovery Addon.

After They Leave: Win-back Sequences

A sequence is the ordered set of messages a member receives on the days you chose after one of four moments. The first is the one everyone asked for: a member whose last live membership ended. Build it on the Sequences face of the Revenue Recovery page: a name, then up to 8 steps, each with its day and your message, with {name}, {project}, {coupon}, {discount} and {link} filled in for each member. Steps go out up to 180 days apart, the first may go out within the hour, and a coupon on a step turns {link} into the way back with that code already in place.

A member enrols once per departure, never while they hold a live membership, leaves the sequence the moment they pay, and you are told when they do. One the platform can no longer reach leaves it quietly; nothing is sent twice. A pass or a season that simply ran its course is not a departure and starts nothing.

Before They Join: Leads, Stalled Checkouts and Trials

The same engine runs on three more moments, and a starter writes the first three steps of each for you, every word yours to change.

• A new lead. Anyone your project records for the first time without a purchase: a first message to your bot, a sign-in to your portal, a Smart Link or a referral link followed. A lead sequence reaches them from their first contact and stops the moment they buy or start a trial.
• A stalled checkout. Every checkout a member starts on the portal or in the bot, on any payment method, is written to a ledger the moment they are handed the way to pay. An hourly sweep counts it as stalled once your window has passed with no settled charge and no live membership, one hour by default, up to 24, once per member per day. The step’s button reopens that plan on the surface the member is on, with the step’s coupon already applied.
• A trial about to end. For the trials that will not convert on their own, the cardless and access-code ones, a sequence starts the days before the end you chose, three by default, up to 14. A shorter trial enters it at its start, a paid membership ends it as a conversion, and a trial with a card on file keeps the reminder it always had.

Every step carries a Stop: a button in the bot and a one-tap link in an email. Pressing it ends every open sequence for that member and keeps them out of every sequence until a charge settles for them or they switch the follow-ups back on in their portal account settings. Checkout and trial steps fall back to email when no account can be reached; lead steps stay in the chat unless the member asked for copies.

Churn Analysis: Why Members Leave, and What Came Back

Revenue Recovery writes everything down, and the Revenue Recovery page reads it back in five faces:

• Overview: failed renewals, reminders sent, access paused, payments recovered and what they brought back, access restored, sequence messages sent and members won back; the members in grace and paused right now; and a third row for the leads who arrived, entered a sequence and bought, the checkouts started, stalled and recovered with what they were worth, and the trials reminded and kept.
• Sequences: every sequence under its trigger, with its steps, its enrolments, who is still receiving steps, and who converted.
• Checkouts: every checkout with the member, the plan, the rail, where it started, and what became of it.
• Cancellations: the reasons as bars with each one’s share, the words members wrote, and the offers shown and taken.
• Activity: the ledger, one row per notice, offer, feedback and message, with whether a payment followed.

The project dashboard carries the same figures as a card, with the top reasons across it; the PDF, CSV, text and Excel exports carry a Revenue Recovery section; and on the days something happened, a daily digest brings the figures to your chat. That is a churn analysis you can act on the same day: a reason that climbs is a thing to fix, an offer nobody takes is a thing to change, a sequence that wins nobody back is a message to rewrite.

Nobody Else Does This

We compare Subscriby against the tools creators choose between on our site, and we checked them again for this launch. As of October 2026, none of the Telegram membership tools in that set documents a grace window and a notice ladder for a failed renewal, a cancellation screen that asks why and makes an offer, timed messages after a member leaves, or a reason-by-reason breakdown of why members go. Nas.io sends two abandoned-checkout emails; InviteMember sends renewal reminders; and that is where the field ends today. A revenue recovery system this complete, with churn analysis beside it, built into the membership tool rather than bolted on, is not available on any other competitor yet.

How to Switch It On, Step by Step

1. Open Revenue Recovery in your project

The cancellation question and the daily digest are already running on every plan. Set the grace window to the days your audience needs; a new project starts at zero. Set the checkout window and the trial reminder beside it.

2. Switch the offers on

On Growth, or with the Revenue Recovery Addon on any plan, switch on the pause, the discount coupon and the return coupon, each coupon one of your own codes.

3. Build a sequence from a starter

On the Sequences face, pick the moment, a member who left, a new lead, a stalled checkout or a trial ending, and three steps on the right days are written for you. Change every word, add steps up to eight, put a coupon on the last one, and preview it for a sample member.

4. Watch the figures

The overview, the Checkouts face and the project dashboard card fill up as the engine runs; the Cancellations face shows why members leave; the Activity face shows every message and whether a payment followed.

Where It Shows Up

• The dashboard. Revenue Recovery in every project’s menu, with its five faces, and a card on the project dashboard.
• The bot. The 💸 Revenue Recovery screen: the grace window, the checkout window, the trial reminder, the question, the digest and the offers, each a button away.
• The portal. The cancellation screen, the pay-again links, and a Follow-up messages switch in every member’s account settings.
• Alerts. A payment recovered, a member won back, and the daily digest, routed like any other class under Settings → Notifications.
• The REST API. The Revenue Recovery API for the settings, the figures, the cancellations, the activity ledger and the checkout ledger, and the Recovery Sequences API for the sequences, their steps and their enrolments.
• The MCP server. Twelve tools, from get_retention_stats to create_sequence and list_checkouts, so Claude and any other MCP client can read the figures and build a sequence for you: the Revenue Recovery tools.
• Webhooks. Fifteen events, among them subscription.payment_recovered, subscription.access_suspended, subscription.cancellation_feedback, the seven sequence.* events, member.lead_created, checkout.stalled and checkout.recovered: the sequence events and the checkout events.
• Zapier and n8n. Zapier 4.3.0 and n8n 4.3.0 carry every trigger, the settings, the figures, the sequences and the checkout ledger, published today.

Questions

Which plan do I need?

The notices, the pay-again links, the grace window and the cancellation question are on every plan, Free included. The cancellation offers and the sequences are included on Growth; on every other plan the Revenue Recovery Addon unlocks them for $9 a month, prorated to the days left in your billing period, with no extra transaction fee.

Does Subscriby charge the member again?

No. Your payment gateway holds the member’s card or wallet and retries on its own schedule. Subscriby keeps the member’s access while it does, tells them with the gateway’s own link to pay again, and lets them back in the moment a charge settles.

What does the member see?

A message where they already talk to your project: that the payment failed, that their access stays until the window closes, and a button that opens their payment method’s own page. A reminder on day 3, a last warning the day before the pause, one notice when access pauses, and nothing once they have paid.

Can a member stop the sequence messages?

Yes, with one press, on every message, and the Stop holds until a charge settles for them or they switch the follow-ups back on themselves. Nothing is ever sent twice, and nothing is sent to a member who holds a live membership.

Does a trial sequence keep going after the trial ends?

Yes. Only a paid membership ends it, and while it runs the win-back trigger leaves that member alone, so nobody gets two sequences for one lapse.

More under Questions in the guide and on the feature page.

Keep the Members You Were About to Lose

Open the dashboard, pick a project, and press Revenue Recovery in the sidebar; or tap 💸 Revenue Recovery on the bot’s project menu. Set the window, switch the offers on, build the first sequence from a starter, and let the engine run. Everything else, from the first failed charge to the member walking back in, we handle.

Read the full guide at docs.subscriby.net/creators/revenue-recovery, the feature page at subscriby.net/features/revenue-recovery, and what your members see at docs.subscriby.net/subscribers/follow-up-messages. Welcome back, to them.