SaaS email template

Subscription cancelled email — acknowledge the cancellation without burning the bridge

Fire subscription.cancelled with the access end date and a win-back URL. else.events sends a clear, non-aggressive cancellation confirmation that leaves the door open.

Common mistakes with subscription cancellation emails

Aggressive "Are you sure?" tone that feels manipulative

A cancellation confirmation should confirm — not guilt-trip. Emotional pressure in a transactional email damages brand trust.

No mention of when access ends

Users cancel but may have paid for the rest of the month. Not telling them when access ends creates confusion and support tickets.

No win-back path

A cancellation email with no way back is a missed opportunity. A single, calm "You can reactivate anytime" line with a link costs nothing.

Hardcoded in the subscription service

Cancellation email logic buried in the subscription handler makes it hard to update copy, add a locale or change the win-back CTA.

Clear confirmation, access end date, calm win-back link

Access_ends_at from the payload

Include when the user loses access. The template renders "You have access until June 1, 2026" — clear, useful, no confusion.

Calm win-back CTA from the payload

Include a reactivation URL in the payload. The template renders "You can reactivate anytime" as a low-pressure secondary link.

No guilt — just clarity

Template tone is factual: "Your subscription has been cancelled. Here is what happens next." Leave the door open without the emotional pressure.

Managed outside the subscription service

Edit cancellation copy, update the win-back CTA or add a locale without touching the subscription service.

Template variables for the subscription cancelled email

  • {{ user.name }}Recipient name
  • {{ data.plan }}The plan that was cancelled
  • {{ data.access_ends_at }}Date when the user loses access to paid features
  • {{ data.reactivate_url }}Link to reactivate the subscription
  • {{ data.cancelled_at }}Date the cancellation was processed

Frequently asked questions

What subject lines work for subscription cancellation emails?
"Your [App] subscription has been cancelled", "Cancellation confirmed — access until [date]", "We have processed your [App] cancellation". Factual, not emotional.
Should I include a feedback request in the cancellation email?
A short optional feedback link ("Tell us why you cancelled") is acceptable — but do not make it the focus or block the confirmation with it. Keep the email primarily informational.
How do I show the correct access end date?
Include access_ends_at in the subscription.cancelled event payload (typically the end of the current billing period). The template renders it as "Your access ends on [date]".
What if a user wants to reactivate?
Include a reactivate_url in the payload — a deep link to the subscription reactivation flow. The template renders it as a calm secondary CTA button.

Cancellation emails that acknowledge clearly and leave the door open

Access end date, win-back link, no guilt. Managed outside your subscription service.

  • Access end date from payload
  • Calm win-back CTA
  • Edit copy without touching subscription code