Notification emails that are useful without opening the app

Each notification email carries the event label, a tone matched to its severity, an at-a-glance card of the facts, and a single button into the record — sent from the account's own sender.

What it is

The subject is prefixed with the event label. Severity drives the chip's tone; official-record events carry the certification seal and read as success. The details card is built from the junction's explicit facts where they exist, otherwise from an allowlisted mapping of the event's structured data.

Also called: alert email · email notification layout · branded notification email

See it
Notification emails that are useful without opening the app
Area
Operations
Group
Notifications
System
Notifications
Solves
2 named problems
01Internal and staff mail renders through the shared platform-branded composer, per the internal-versus-customer branding rule.
02Explicit facts beat the generic key map: 'the junction knows what matters here better than a generic key map does'.
03Mail routes through the org's own connected sender so internal notifications also come from the sub-account's domain — no shared platform sender — with a fallback for orgs that have not connected one.
A rendered notification email: event chip, title, body, facts card, one CTA button. emailLayout.ts. Sample data — no customer information appears here.
How it works
  1. 1Internal and staff mail renders through the shared platform-branded composer, per the internal-versus-customer branding rule.
  2. 2Explicit facts beat the generic key map: 'the junction knows what matters here better than a generic key map does'.
  3. 3Mail routes through the org's own connected sender so internal notifications also come from the sub-account's domain — no shared platform sender — with a fallback for orgs that have not connected one.
  4. 4Every send is logged back into the notifications table with its status and any error.
Why we built it

Migration 223 records the emptiness this fixed: the email 'printed a paragraph where it had a context card sitting empty beside it'. Sending from the org's own domain rather than a shared address protects deliverability and keeps the message recognisable to the recipient.

The problem
  • Prose-only emails with an empty context column
  • Shared-sender deliverability
Sound familiar?
What you get
Enough detail to act without opening the app
Every send recorded with its outcome

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →