SaaS email template

Subscription renewal reminder — give users notice before the charge

Fire subscription.renewal_upcoming with the renewal date and amount. else.events sends a clear renewal notice that reduces charge surprises and payment disputes.

Why renewal reminders reduce payment disputes

Users forget they subscribed annually

Annual subscribers are surprised by renewal charges. A reminder 7–14 days before renewal gives them time to cancel if needed — and reduces disputes.

No reminder is a chargeback risk

Unexpected charges increase chargeback rates. A renewal reminder is both user-friendly and commercially prudent.

Plan and amount not shown in the reminder

A renewal reminder without the plan name and amount charged is not useful for users deciding whether to keep the subscription.

Hardcoded in the billing service

Renewal reminder email logic tied to the billing service means every copy update requires a deployment.

Renewal date, amount and plan from the payload — clear notice in the email

Fire subscription.renewal_upcoming 7–14 days before renewal

Your backend cron job fires the event for each subscription approaching renewal. else.events sends the reminder immediately.

Renewal date, amount and plan in the payload

Include all billing details in the event payload. The template renders a complete renewal notice with no missing information.

Cancel or manage subscription link from the payload

Include a manage_url in the payload. The template renders a calm secondary link to the billing settings.

Managed outside your billing service

Edit copy, update the CTA or add a locale without touching the billing service.

Template variables for the renewal reminder email

  • {{ user.name }}Recipient name
  • {{ data.plan }}Plan being renewed
  • {{ data.amount }}Renewal amount with currency
  • {{ data.renewal_date }}Date the renewal charge will occur
  • {{ data.billing_period }}Billing period (Monthly or Annual)
  • {{ data.manage_url }}Link to billing settings to manage or cancel

Frequently asked questions

How far in advance should I send the renewal reminder?
For annual subscriptions, 14 days before is standard. For monthly subscriptions, 3–7 days before. Your backend cron job controls the timing; else.events sends when it receives the event.
What subject lines work for renewal reminders?
"Your [App] subscription renews on [date]", "Renewal reminder: [Plan] — [amount] on [date]", "[App] Annual plan renews in 7 days". Include the date and amount.
Should I include a way to cancel in the reminder?
Yes. A cancellation or manage-subscription link reduces chargeback risk. Users who want to cancel should be able to do so easily before the renewal — it is better than a disputed charge.
What if the user updates their payment method before renewal?
That is handled by your billing provider. The renewal reminder is a pre-charge notice only — it does not interact with payment method management.

Renewal reminders that reduce disputes and keep users informed

Renewal date, amount, plan and manage link — all from the event payload. Fire 7–14 days before renewal.

  • Reduces chargeback risk with advance notice
  • Renewal amount and date from payload
  • Manage-subscription link included