Goal
Help legitimate users recover access while keeping security messaging clear.
Template Hedgehog
Open navigation
Password reset
Handle account recovery with security-safe copy and a direct reset action that works across clients.
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 immediately after a user requests a password reset.
Layout
Password Reset System
Core included
This workflow is part of Core and remains included in Pro. Use it as a starter production system, then move to Pro when recurring lifecycle, transactional, campaign, and newsletter work needs the full archive.
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.
user.first_name
Optional personalisation in the opener.
auth.reset_url
One-time password reset link.
auth.reset_expiry_minutes
Expiry policy shown in copy.
Variant routes
- Reset link expired: Alternative message pointing users to request a new secure link.
- Suspicious activity warning: Adds account safety notice when request origin appears unusual.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Core archive: MJML source, compiled HTML, preview, and setup guidance for this starter workflow.
- Pro archive: this workflow plus the full recurring workflow set, QA notes, implementation guidance, Studio waitlist priority while Studio is in development, and updates.
Linked production layout
Password Reset System
Password reset email with the reset card, a privacy note, and a lean transactional footer.
Component stack
Header, Password Reset Card, Privacy Note Icon Left, Footer Privacy Light
Source file
password-reset.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
- Some Outlook builds flatten rounded CTA corners, so button copy must stay legible without shape cues.
- Security copy can become too dense if line length is not capped.
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.
Start with this workflow in Core.
Core is enough when the essential starter workflows solve the immediate implementation. Pro is the upgrade when the same source-to-handoff process becomes recurring work across more sends.