SaaS email template

Plan downgrade email — confirm clearly, show what changes, leave the door open

Fire subscription.plan_downgraded with the effective date and features that change. else.events sends a factual confirmation that reduces confusion and keeps the relationship.

Common mistakes with plan downgrade emails

No clarity on when the downgrade takes effect

Does it take effect immediately or at the end of the billing period? Users who do not know are surprised when features disappear.

No list of features that will be lost

A downgrade confirmation without a clear "these features will no longer be available" section leaves users confused and creates support tickets.

No upgrade-back path

A user who downgrades might reconsider when they see what they lose. A calm "upgrade again anytime" link costs nothing and recovers some churns.

Hardcoded in the billing service

Downgrade email logic in the billing handler means every copy update requires a deployment.

Effective date, feature changes and upgrade link — all from the payload

effective_at from the payload

Include when the downgrade takes effect. The template renders "Your plan changes to Basic on June 1, 2026" — clear and no surprises.

Features that change — from the payload

Include an array of features the user will lose access to. The template renders a clear list so users know exactly what changes.

Upgrade link in the email

Include an upgrade URL in the payload. The template renders a calm "Changed your mind? Upgrade back anytime" secondary CTA.

Managed outside your billing service

Edit downgrade copy, update the feature list or add a locale without touching the billing service.

Template variables for the plan downgraded email

  • {{ user.name }}Recipient name
  • {{ data.previous_plan }}Plan the user was on before the downgrade
  • {{ data.new_plan }}Plan the user is downgrading to
  • {{ data.effective_at }}Date the downgrade takes effect
  • {{ data.features_changing }}Array of features that will no longer be available
  • {{ data.upgrade_url }}Link to upgrade back — shown as a secondary CTA

Frequently asked questions

What subject lines work for plan downgrade emails?
"Your [App] plan has been changed to Basic", "Downgrade confirmed — here is what changes on [date]", "Your [App] plan change is scheduled for [date]". Include the effective date.
Should the downgrade take effect immediately or at end of billing period?
This is a product decision, not an email decision. Whatever your backend determines, include the effective_at date in the event payload so the email is accurate.
Can I suppress the downgrade email for plan changes triggered by admins?
Yes — your backend controls whether to fire the subscription.plan_downgraded event. If admin-initiated downgrades should not notify the user, do not fire the event for those cases.
What if the user wants to upgrade back immediately?
Include an upgrade_url in the payload. The template renders it as a secondary CTA. Users who reconsider immediately can act right from the email.

Downgrade confirmations that reduce confusion

Effective date, feature changes, upgrade link. All from the event payload. No hardcoded billing email.

  • Effective date shown clearly
  • Features-changing list from payload
  • Calm upgrade-back CTA in the email