QuQi
EMAIL

Renewal reminder sequence

Use when subscriptions are coming up for renewal and you want fewer surprises and fewer cancellations.

renewal-reminder-sequence.md
Download .md
You are a retention email writer. Write a renewal reminder sequence.

Product and plan: {{PRODUCT_AND_PLAN}}
Renewal amount and date logic: {{RENEWAL_TERMS}}
Whether renewal is automatic: {{AUTO_RENEW_YES_NO}}
Notice periods or cancellation terms: {{CANCELLATION_TERMS}}
What the customer has actually got out of the last term, and where I hold that data: {{USAGE_DATA_SOURCE}}

Output a table: Email | Days before renewal | Subject | Preheader | Body | Call to action | Which customers should be excluded

Cover: an early notice, a reminder close to the date, and a confirmation after the charge.

Rules:
- State the amount, the date and whether it is automatic in every email in the sequence. Do not bury them.
- Include the cancellation route plainly. Do not make cancelling harder than renewing.
- Use usage data only if I have said above that I hold it. Otherwise write {{NEEDS_FACT}} where a usage line would go.
- Do not use urgency, discounts or loss framing in the early notice. That is a billing message.
- No em dashes, no gratitude padding, no closing paragraph restating the opening.

Then list the two customer situations that should be pulled out of this flow and handled by a person instead.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

  • {{PRODUCT_AND_PLAN}}
  • {{RENEWAL_TERMS}}
  • {{AUTO_RENEW_YES_NO}}
  • {{CANCELLATION_TERMS}}
  • {{USAGE_DATA_SOURCE}}
  • {{NEEDS_FACT}}

Getting a better result

  1. Clear renewal notices reduce chargebacks and refund requests more than any save offer.
  2. Keep discount save offers out of the pre-renewal emails. They teach customers to threaten cancellation.
  3. Suppress accounts already in a cancellation or support conversation before the sequence sends.