Onboarding
For activation and lifecycle flows where the block needs to move users to the next step.
Production block
Onboarding-specific footer with preference language tailored to support and activation messaging.
Use in activation, guarantee, or post-purchase flows where support language needs to be clearer than in a general marketing footer.
At the close of the email, where support, legal, and brand trust need to be retained.
To help lifecycle teams guide users towards the next meaningful action.
Preview
Rendered production artefact for workflow review before handoff.

Treat the component as one production section inside a larger message system. It should support the send goal, survive handoff, and remain easy to review before compilation.
For activation and lifecycle flows where the block needs to move users to the next step.
For legal, support, and trust information that needs to survive ESP handoff cleanly.
These relationships help buyers understand the block as part of a send, not as an isolated catalogue item.
Drive first meaningful action and reduce first-week drop-off.
View workflowIncrease paid conversion before trial access lapses.
View workflowGuide a new or returning user to the next activation step.
View workflowKeep account-access copy direct, secure, and easy to verify.
View workflowKeep the checks short and action-oriented. The goal is to help teams decide whether this block is ready to enter a workflow.
A production email usually needs a stack of blocks. These nearby sections are a sensible next choice when assembling a full send.
Light regulatory footer for app or support sends that need policy and legal copy without store links.
Support details plus preference and unsubscribe links for compliant email endings.
Light footer variation for app and digital-product emails with extra trademark or platform-copy space.
Source stays below the preview and workflow context. Copy MJML when assembling a system, or compiled HTML when preparing ESP handoff. Template Hedgehog Pro includes the full offline archive for teams that need the complete system locally.
Block assembly: place this section inside the same <mj-body> as your other production blocks, then stack sections in send order.
Editable source
Section-only MJML for assembling an email from multiple reusable production blocks inside a shared project.
Formatting code preview...Compiled output
Component-only compiled markup for block-level inspection and HTML assembly workflows.
Formatting code preview...