SaaS email template

Plan upgrade confirmation — celebrate the upgrade and show what is now available

Fire subscription.plan_upgraded with the new plan, unlocked features and next billing date. else.events sends a confirmation that reinforces the upgrade decision.

Why upgrade confirmation emails underperform

No mention of what is now available

A "you have upgraded to Pro" email with no feature list misses the chance to reinforce the value of the upgrade decision.

Missing next billing date

Users want to know when they will be charged and how much. Not including this creates billing uncertainty.

Generic "congratulations" tone

An upgrade confirmation should feel like a handshake, not a party. Clear, useful information reinforces confidence.

Hardcoded in the billing service

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

New plan, unlocked features, next billing — all from the payload

New plan and unlocked features in the payload

Include the previous plan, the new plan and the list of newly unlocked features. The template renders a clear "what changed" section.

Next billing date and amount from the payload

Include next_billing_date and amount in the payload. The template renders billing clarity so users know exactly when they will be charged.

CTA to the feature that matters most

Include a link to the first new feature the user should try. Drives immediate post-upgrade activation.

Managed outside your billing service

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

Template variables for the plan upgraded email

  • {{ user.name }}Recipient name
  • {{ data.previous_plan }}Plan the user was on before the upgrade
  • {{ data.new_plan }}Plan the user upgraded to
  • {{ data.unlocked_features }}Array of newly available features
  • {{ data.next_billing_date }}Next charge date for the new plan
  • {{ data.amount }}Amount that will be charged on the next billing date
  • {{ data.feature_cta_url }}Link to the most relevant new feature to explore first

Frequently asked questions

What subject lines work for plan upgrade emails?
"You are now on [App] Pro — here is what changed", "Upgrade confirmed: welcome to [Plan]", "Your [App] plan has been upgraded". Include the plan name.
Should I include pricing in the upgrade confirmation?
Yes — include the next billing date and amount. Users who just upgraded want clarity on when they will be charged. It also reduces support questions.
How do I include the list of newly unlocked features?
Include an unlocked_features array in the event payload. Your template iterates over it to render each feature name. Keep the list short — the three most important features are enough.
Can I send different upgrade confirmations for different plan tiers?
Yes. Create rules matching data.new_plan = Pro and data.new_plan = Premium. Each routes to a different upgrade confirmation template with tier-specific feature highlights.

Upgrade confirmations that reinforce the decision

New plan, unlocked features, next billing date. All from the event payload.

  • Unlocked features from payload
  • Next billing date shown clearly
  • CTA to the most relevant new feature