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.
SaaS email template
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.
Does it take effect immediately or at the end of the billing period? Users who do not know are surprised when features disappear.
A downgrade confirmation without a clear "these features will no longer be available" section leaves users confused and creates support tickets.
A user who downgrades might reconsider when they see what they lose. A calm "upgrade again anytime" link costs nothing and recovers some churns.
Downgrade email logic in the billing handler means every copy update requires a deployment.
Include when the downgrade takes effect. The template renders "Your plan changes to Basic on June 1, 2026" — clear and no surprises.
Include an array of features the user will lose access to. The template renders a clear list so users know exactly what changes.
Include an upgrade URL in the payload. The template renders a calm "Changed your mind? Upgrade back anytime" secondary CTA.
Edit downgrade copy, update the feature list or add a locale without touching the billing service.
{{ 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 CTAEffective date, feature changes, upgrade link. All from the event payload. No hardcoded billing email.