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.
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.
A plain-text password reset email without branding, a proper subject line or a clear CTA makes users hesitate to click.
The reset URL gets assembled in application code and injected into a hardcoded template — no version control, no easy updates.
Users who receive a reset email need to know when the link expires. Forgetting this leads to support tickets.
Sending a German-language password reset email to German users requires either separate templates or custom locale logic.
Generate the token and URL in your backend, include them in the event payload. The template renders the CTA link — no hardcoding.
Include expires_in_minutes in the payload. The template renders it as human-readable text.
Include a locale in the event. Rules route to the correct language template for the reset email.
Update subject line, branding or body copy in the else.events UI. No commit, no deploy.
// password reset event
{
"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.
Fire user.password_reset_requested. else.events handles the rest.