Four categories — Customer-facing, Your stages, Team & internal, and Platform — each listing the emails that exist, with subject lines and full renderings. Stage cards are synthesised per tenant from the stages the builder has actually defined, including any wording they wrote for that stage and who it goes to.
Also called: see every email · what emails does this send · email catalog · email templates
- 1The catalogue is built client-side from the resolved brand, so there is no server round-trip per email and previews are always current.
- 2Stage cards read the tenant's stage rows and their effective notification settings, showing recipients as a readable list (Customer, Owner, PM, Crew lead, Project team, N named) or 'Silent — nobody is notified'.
- 3A card marks itself customised when the builder has overridden the subject, heading or body for that stage.
- 4Device switching renders each email at desktop, tablet and mobile widths.
Automated email is the part of the product a customer sees most and the builder sees least. Rendering the whole catalogue on the tenant's own brand answers both 'what does this system send on my behalf' and 'does it look like us' without sending anything. Stage cards are synthesised rather than registered because the set of stages is per-tenant and changes whenever the builder edits their setup.
- There was no inventory of platform-sent email.
- Per-stage customer wording could not be checked without completing a stage.
- Nobody could tell which stages were silent.
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 →