Two coordinators clear the framing checklist inside the same minute, the homeowner gets "Framing is complete" twice, and rings to ask whether something has gone wrong.

The customer trusts an update that arrives once; a doubled email makes them wonder what went wrong. The send is claimed in one central place before anything leaves, so whichever device gets there first owns it and every other one stands down — two people can tick the same box and the customer still hears once.

Nobody in the company has ever read the email that goes out in their name, so the first time the owner sees it is when a customer forwards it back asking what "dry-in" means.

The owner gets to read, once, the email that goes out in his company's name. One reviewed message per event beats free text typed by a project manager at six in the evening, so the customer always gets the version you were happy with.

The email says the siding is done, and the customer rings anyway to ask what happens next week, because two lines of text was everything they were given.

A customer who taps through finds the photos, the phase list and the payment schedule already there and current. So the email stays two lines and does one job — send them to the page — and the questions that would have been phone calls answer themselves.

The crew finishes the pour and taps done on the phone, the office hears about it on Thursday, and the customer is never told at all.

The crew lead's tap counts the same as the office's, so news doesn't wait for someone at a desk to pass it on. One routine runs every completed stage, so there is no path where the work is marked done and the customer quietly isn't told.

The inspector fails the footings, the crew fixes them the next morning and ticks it off again, and the customer is still looking at a job that says nothing has moved.

A customer whose failed inspection got put right should hear that it's put right. Reopening hands the claim back the moment the box is unticked, so the second finish sends properly — reopen and redo it four times and they hear four times, which is right for work that really was redone.

The notification path throws on a Tuesday afternoon, the guard decides to stay quiet about it, and nobody notices for a month that customers have stopped hearing from you.

An apology for a doubled email is cheap; a customer who heard nothing for three stages is not. So the guard fails open — if it can't tell whether the message went, it sends — and the tick itself is saved before any of this runs.

The homeowner reads that framing is complete, rings the project manager to ask what comes next, and the project manager has not been told either.

The project manager should never learn about a finished stage from the customer. The team alert and the customer's email come off the same event, so the office knows the moment the customer does.

A builder mutes the material-delivery stage, the standard notice fires anyway, and the setting stops being trusted for anything else.

A builder who says "keep this stage quiet" gets quiet, so he trusts the setting. A rule replaces the standard send instead of adding to it — once you write one, you own everything that stage sends, silence included.

You write friendlier wording for one stage, and the customer gets an email in a colour your company has never used, with no logo on it.

The customer always gets an email that looks like your company, whatever wording you choose. Your words ride inside the branded template — less freedom over layout, and no way for a well-meant tweak to go out in somebody else's colours.

Somebody turns notifications down because the office is getting too many, and six weeks later nobody can work out why customers stopped hearing anything.

Turning down the office's alerts should quiet the office, not the job. The customer's update has its own switch beside the other customer messages, and the text is a third switch that stays off until you turn it on — a text lands on a personal phone and costs money.

The building is finished, the crew has gone, and the last word the customer ever gets from you is a form notice about siding.

The last thing a customer hears should feel like an ending, and it is the natural moment to ask for a review. The rule reads the job's own stage list, so a builder who adds a custom stage at the end gets the sign-off on that one instead.

The customer has the dashboard open on their phone while the crew finishes the pour, sees nothing change, and rings the office to ask whether anything happened today.

A customer watching their page sees the phase go green on its own, so there is nothing to ring about. The page re-reads the whole job every few seconds — a short fixed beat rather than an instant push, which is plenty for a page a household opens twice a week.