Running behind, from the taps the crew already makes
A lane still On Site past a stop's planned departure reads running ~30 min behind, with the remaining stops' times pushed by the delay; a recipe can text the next customer once.
The crew already taps On my way and I have arrived. On a planned day those taps are enough to know the day is behind: still On Site past a stop’s planned departure, or En Route past a planned arrival, and the lane on the board says running ~30 min behind — the same figure at the top of My Day, and on the plan, where every stop still to come says when it is now expected. The plan itself does not change; the day is late against it. Nothing reads a location: a business that records where the phone was at an arrival gains nothing extra here, and never will.
How far behind counts is yours to set — Running behind after on the Team page’s Routing panel, fifteen minutes until you change it.
Tell the next customer when we’re running behind is a new automation recipe, off until you switch it on. When the delay first passes your threshold, the customer at the next door gets one text — We’re running about 30 minutes behind for your visit today - sorry about that. — through the same consent every other text honors, never an email, and never held until morning, because by morning it would be untrue. A customer is told once per stop per day; a delay that grows does not text again. The run is in the recipe’s history and on the customer’s timeline, and a customer with no number or an opt-out is a skipped run that says so.