Password reset emails — secure, branded, no marketing bloat

A password reset request is a security event, not a marketing opportunity. Send a clean, branded email with the reset link — from a single event, no extra infrastructure.

What goes wrong with password reset emails

Generic templates damage trust

A plain-text password reset email without branding, a proper subject line or a clear CTA makes users hesitate to click.

Reset tokens often end up hardcoded in templates

The reset URL gets assembled in application code and injected into a hardcoded template — no version control, no easy updates.

Expiry information is missing or wrong

Users who receive a reset email need to know when the link expires. Forgetting this leads to support tickets.

Multi-locale reset emails are a separate problem

Sending a German-language password reset email to German users requires either separate templates or custom locale logic.

Fire the reset event. else.events delivers the branded email.

Reset token and URL in the event payload

Generate the token and URL in your backend, include them in the event payload. The template renders the CTA link — no hardcoding.

Expiry rendered from payload

Include expires_in_minutes in the payload. The template renders it as human-readable text.

Locale-aware out of the box

Include a locale in the event. Rules route to the correct language template for the reset email.

Edit template without deployment

Update subject line, branding or body copy in the else.events UI. No commit, no deploy.

// password reset event

Clean reset event — token and expiry in the payload

{
  "type": "user.password_reset_requested",
  "locale": "en",
  "user": { "email": "user@example.com", "name": "Alex" },
  "data": {
    "reset_url": "https://app.example.com/reset?token=abc123",
    "expires_in_minutes": 30
  }
}

else.events matches the rule for user.password_reset_requested, renders the branded reset template with the personalised reset_url and expiry, and delivers through your provider.

Frequently asked questions

How do I include the reset link securely?
Generate the reset token and full URL in your backend. Include the URL in the event payload data field. The template renders it — the token never appears in else.events configuration.
Can I show the expiry time in the email?
Yes. Include expires_in_minutes or a formatted expiry timestamp in the event payload. The template variable renders it as human-readable text.
What if the user requests multiple resets in quick succession?
Your backend should invalidate previous tokens before issuing a new one. else.events sends an email for every event it receives — deduplication is handled in your application.
Can the password reset email match my app's branding?
Yes. Manage the reset email template in the else.events UI with your brand colours, logo and typography — without touching your codebase.

Branded password reset emails — from one event, no extra infrastructure

Fire user.password_reset_requested. else.events handles the rest.

  • Free during public beta
  • Reset token rendered from payload
  • Locale-aware out of the box