A distinct, tenant-branded 'Congratulations — <project> is complete' email with a link to the customer's portal, sent in place of the routine progress email on the final build stage.
Also called: build finished email · job complete message · final update to the customer
- 1The routine reads the project's task list and identifies the LAST build-type task (permitting, materials and final payment are not build work)
- 2If the completed stage IS that task and the org has the 'Project completed' customer message enabled, the completion email owns the moment
- 3The generic stage update stays quiet in that case — one action, one customer message
- 4The completion claim already guarantees once per stage, so this fires once per project
The last thing a customer heard on a finished build was a routine 'framing is complete'-style notice, which reads as software that did not notice the job ended — a flat finish to the one moment a builder most wants to land well. Completion is its own message, and it fires off the same definition of done the project board uses, so the board and the customer never disagree about whether the build is over.
- No distinct end-of-build moment for the customer
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 →