SaaS email template

Product notification email — right action, right person, right moment

Fire notification.created with the notification type and relevant context. else.events routes to the right notification template and delivers instantly.

Common mistakes with product notification emails

Notification email looks nothing like the product

Inconsistent branding in notification emails makes users second-guess authenticity.

No deep link to the relevant object

"You have a new comment" with no link to the comment is useless. Users open the app and spend 30 seconds finding what they were notified about.

Sent to users who turned off email notifications

Firing notification emails regardless of user preference creates unsubscribe churn.

No locale support

Notification emails in one language only miss users who set a different locale.

Notification type, deep link and user preference — from the payload

Deep link to the relevant object from the payload

Include the link to the comment, task or project in the event payload. The template renders a "View comment" CTA button that goes directly there.

Notification type in the payload for routing

Rules match on notification_type to route to different notification templates — comment, mention, status change, alert.

Preference check in your backend before firing

Your backend checks user notification preferences before firing the event. else.events handles the email for every event it receives.

Locale from the payload

Include the recipient's locale. The right language notification template is selected automatically.

Template variables for the product notification email

  • {{ user.name }}Recipient name
  • {{ data.notification_type }}Type of notification — comment, mention, status_change, alert
  • {{ data.actor_name }}Name of the person who triggered the notification
  • {{ data.subject }}Notification subject (e.g. "new comment on Project X")
  • {{ data.action_url }}Deep link to the relevant object in the app
  • {{ data.preview }}Short preview text of the notification content

Frequently asked questions

What subject lines work for product notification emails?
"Alex commented on Project X", "You were mentioned in [Doc name]", "Status changed: Task Y is now Done". Specific, actionable, not generic.
How do I route different notification types to different templates?
Include notification_type in the event payload. Create rules matching notification_type = comment, notification_type = mention, etc. Each routes to a tailored notification template.
How do I handle users who turned off email notifications?
Your backend checks user notification preferences before firing the notification.created event. Do not fire it for users who opted out.
Can I batch multiple notifications into a single email?
Not natively per event — else.events sends one email per event. For batched notifications, fire a digest.daily or digest.weekly event with an array of notification items in the payload.

Notification emails that are actually useful

Deep link to the relevant object, notification type from the payload, locale routing.

  • Deep link to the relevant object
  • Notification type routing via rules
  • Preference check in your backend before firing