Goal
Reassure buyers and reduce immediate post-purchase support requests.
Template Hedgehog
Open navigation
Upgrade confirmation
Confirm plan change and next account capabilities without introducing billing ambiguity.
Workflow assembly
Trigger to production output
01
Trigger
Real send event
02
Workflow
Message journey
03
Layout
Complete structure
04
Components
Reusable blocks
05
Production output
Workflow structure
Sent when a user upgrades to a paid plan.
Layout
Upgrade Confirmation System
Pro archive
This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.
Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.
What the production package needs.
A workflow is useful when the implementation contract is visible before anyone starts editing markup.
account.new_plan_name
Name of the upgraded plan.
billing.next_invoice_date
Next billing date shown for transparency.
account.dashboard_url
Destination for post-upgrade setup.
Variant routes
- Seat expansion confirmation: Alternative copy when upgrade is capacity-only.
- Payment pending: Fallback for delayed settlement states.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Full MJML source for this workflow
- Compiled HTML output ready for ESP upload
- Variant-ready workflow pack files
- Versioned workflow updates inside Template Hedgehog Pro
Linked production layout
Upgrade Confirmation System
Upgrade confirmation email that confirms the plan change, reinforces product value, and keeps the app close to hand.
Component stack
Header Centred, Upgrade Confirmation Card, App Download Strip, Footer App Legal
Source file
upgrade-confirmation.mjml
QA and handoff.
The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.
QA risks to review
- Plan naming differences between billing and product systems can create copy mismatches.
- Locale-specific dates must be formatted consistently with account settings.
Handoff steps
- Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
- Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
- Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.
Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.
Use this workflow inside Pro.
Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.