The RevenueCat failed-renewal recovery playbook

Start with the RevenueCat event and the customer state it represents. A billing issue should open a recovery case tied to the affected app user, product, plan value, event time, entitlement state, and the channels through which the customer can actually be reached.

Keep the case open only while recovery is possible. Renewal, payment resolution, an entitlement change, or a later event that makes the original message irrelevant should close or reroute it. This state discipline prevents the most damaging failure in recovery messaging: asking someone to fix a payment problem they have already resolved.

Exposed revenue is a useful starting point, but the highest-priced subscription is not automatically the best first target. Recency, active entitlement, recent app activity, and channel reachability all affect whether a customer can reasonably be recovered.

Create a simple priority view that separates commercial value from execution confidence. A recently active annual subscriber with a valid email address may deserve immediate attention. An old, unreachable record with unclear state should not receive the same operational priority, even if its theoretical value is high.

The recovery message should explain what happened, preserve trust, and point to one safe next step. Avoid turning a payment interruption into a generic feature campaign. The customer does not need another tour of the product; they need a clear route to maintain access.

Channel sequencing should reflect context. An in-app prompt can be effective when the customer returns while still entitled. Email provides room for explanation and a durable payment-update route. Push can create timely awareness, but should remain concise and should stop as soon as the underlying case changes.

Delivery metrics help diagnose the sequence, but recovered renewal is the outcome. Build the report from the original exposed cohort so every stage has a stable denominator: cases detected, customers reachable, customers messaged, payment actions started, renewals recovered, and cases still unresolved.

Separate correlation from attribution. A customer may recover because of an automatic store retry, direct product use, support intervention, or the campaign. Use a consistent attribution window and keep a comparison cohort when volume permits. The purpose is to make the result decision-useful, not to force every renewal into a marketing claim.

The first production flow does not need complex personalization. It needs correct event handling, one reachable cohort, trustworthy copy, suppression on recovery, and reporting that ties back to RevenueCat. Start with one app and one billing-issue cohort before adding offer logic or deeper branching.

Review the first cohort manually. Look for stale states, duplicate contacts, confusing payment routes, and customers who recovered between steps. Those observations will improve the system faster than adding more messages to an unreliable workflow.