Membership Renewal Decision

When memberships lapse at term end without a single reminder, or auto-renewal charges catch members by surprise and generate refund and complaint tickets, this journey is the fix. The renewal date, current price, plan, payment method and auto-renewal state must be verifiable 30 days ahead, the charge result and renewal event tracked, a plan change recorded apart from a cancellation, and email, push and WhatsApp consent held separately. If most non-renewals come from failed cards, that is a collection problem, not a reminder problem; run Payment Failure Recovery first.

Incremental renewal rate vs control

What counts is a new term actually starting, not a renewal decision or a click; the journey's value is how many more memberships the messaged group renews than the control group.

How it is counted: Among all memberships assigned at entry to the journey group and the control group, the share whose new term starts with a confirmed payment within the same follow-up window after the end date; read the gap separately for the auto and manual branches. A membership whose charge failed and moved to recovery does not count as renewed, and the delivery or click status of a message does not change the denominator.

Also track

• Cancellation before renewalMembers in the auto-renewal branch who cancel at the 7-day check or before the date, as a share of that branch; if the information email pulls cancellations forward, compare against the control group.
• Charge failure shareThe share of memberships whose charge fails on the date and moves to Payment Failure Recovery; that loss belongs to the payment method, not to the renewal message.
• Renewal per touch in the manual branchCount renewals after the renewal email, the push and the WhatsApp reminder separately; if the last touch adds nothing, try removing it.
• Opt-outs and complaintsTally push opt-outs, email unsubscribes and WhatsApp complaints by branch; if the final reminder near the end draws complaints, weigh the renewals it won against that cost.

• Trigger and entryEvery membership whose renewal terms and auto-renewal state can be verified enters 30 days before its renewal date. Memberships are then randomly assigned at entry to the journey group or to a control group that gets no messages from this flow; auto-renewal runs as normal in the control group.
• Who must not enterAn anniversary recognition belongs to First Purchase Anniversary, not here; it carries no obligation, while this flow counts down to a renewal decision the terms require. A membership whose auto-renewal is already cancelled skips the reminder branch and goes to Cancellation Confirmation. No second flow opens for the same membership term.
• Timing and channelsAuto-renewal on: an information email 30 days out, a cancellation check and push at 7 days, a charge check on the date, a renewed email if paid. Auto-renewal off: a renewal question email, a push 7 days later, WhatsApp 1 to 2 days before the end only where permitted; renewal is rechecked before every touch.
• Exit and handoffRenewal ends the journey, as does a cancellation before the date, after which the membership expires on its end date; queued reminders are cancelled. A cancelled auto-renewal stops the reminders and moves to Cancellation Confirmation, a failed charge to Payment Failure Recovery, and a membership still unrenewed at its end to Lapsed Customer Win-Back.
• Frequency and consentThree touches per term is the ceiling; WhatsApp goes only to members who permit it, push and email under their own consent. A plan change is not a cancellation, the renewal runs on the new plan; never treat a renewal decision as payment received, and send the renewed email only after the charge is confirmed.

1. 1If renewals in the journey group run no higher than in the control group, the messages informed members who would have renewed anyway without changing behavior; opens or clicks do not make up for it. In the auto-renewal branch the notice may raise cancellations; before you call that a loss and trim the notice, look at how complaint and refund tickets moved.
2. 2Everything you measure belongs to this two-branch structure, the 30-day and 7-day checkpoints and this channel order. A membership handed to Cancellation Confirmation, Payment Failure Recovery or Lapsed Customer Win-Back has its later renewal credited to that journey; never count one renewal in two flows.
3. 3Test a small renewal gap per branch: put each group's memberships and renewals into the A/B test significance calculator and check whether the uplift is significant; if it is not, hold the decision until a few more renewal cycles have accumulated.
4. 4A report that counts a plan change as a cancellation, or a renewal decision as a payment, misstates the renewal rate. Send the renewed email only after the charge is confirmed, and keep payment failure, cancellation and simple non-renewal apart instead of merging them into one not-renewed bucket.