Goal
Increase conversion without introducing rushed markup regressions.
Template Hedgehog
Open navigation
Promotion campaign
Run time-bound promotions with a reusable conversion stack that keeps urgency copy clear and controlled.
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 for promotions, offers, and limited-time commercial pushes.
Layout
Trust And Conversion Brief
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.
offer.label
Promotion headline and offer code text.
offer.expiry_utc
Cut-off timestamp used in urgency copy.
offer.redeem_url
Destination for redeeming the promotion.
Variant routes
- Reminder send: Follow-up variation for users who did not click the first campaign email.
- Last-call send: Final-hours variation with shorter copy and stronger urgency treatment.
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
Trust And Conversion Brief
Short conversion email built from approved logos, proof content, and one focused CTA block.
Component stack
Header, Single Image Right, Testimonial / Quote, Primary CTA Button, Footer
Source file
promotion-email.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
- Countdown copy and expiry timestamps must match the timezone used by the ESP scheduler.
- Promotional modules can feel too dense if both product grids and urgency banners are stacked together.
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.