The Your stages category is generated from the tenant's real stage list. Each card renders the customer progress email for that stage with the builder's heading and body overrides substituted, states who receives it, and flags stages that are silent or still inheriting the org-wide notification settings.
Also called: stage update email · what does the customer get when a stage finishes
- 1Stage rows and their effective notification settings are read from the stages API.
- 2Placeholders like {stage} and {project} are substituted with the stage name and a sample project.
- 3Recipients are rendered as a readable list; unresolved states read 'Uses your org-wide Notifications settings'.
- 4Cards hand off to the stage editor for the exact stage being viewed.
Stage notifications are configured in one screen and experienced in another. Synthesising a card per stage closes that loop: the builder sees the actual sentence a customer will read when Framing is marked complete, on their brand, before it ever sends.
- Per-stage email copy could only be verified by completing a stage.
- Silent stages were indistinguishable from configured ones.
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 →