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.
SaaS email template
Fire subscription.plan_upgraded with the new plan, unlocked features and next billing date. else.events sends a confirmation that reinforces the upgrade decision.
A "you have upgraded to Pro" email with no feature list misses the chance to reinforce the value of the upgrade decision.
Users want to know when they will be charged and how much. Not including this creates billing uncertainty.
An upgrade confirmation should feel like a handshake, not a party. Clear, useful information reinforces confidence.
Upgrade email logic in the billing handler means every copy update requires a deployment.
Include the previous plan, the new plan and the list of newly unlocked features. The template renders a clear "what changed" section.
Include next_billing_date and amount in the payload. The template renders billing clarity so users know exactly when they will be charged.
Include a link to the first new feature the user should try. Drives immediate post-upgrade activation.
Edit upgrade 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 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 firstNew plan, unlocked features, next billing date. All from the event payload.