The short answer
As soon as you expect to miss the agreed arrival window, give one dispatcher ownership of the update. Keep the original promise, check a credible new estimate, and send one reviewed message to the right contact through an approved channel. If there is no reliable ETA, say so and give a specific time for the next update. A calendar edit or queued notification does not prove the customer knows about the delay.
Keep four times separate: the internal start time, the customer's promised window, the revised estimate and the next update time. This workflow begins before arrival. If the technician has already reached the site and cannot enter, use the separate no-access visit record.
Check what the customer was actually promised
Jobber's arrival-window documentation distinguishes the customer window from the start time shown on the calendar. Windows are configured on the job and apply to its visits. Updating an existing job can involve all visits or incomplete visits, so check the scope before editing the schedule. Do not change a whole job's window merely to communicate one delayed arrival. Existing or custom templates may omit the window; inspect the effective visit information and actual message.
Housecall Pro's window guide allows defaults and job or estimate overrides, with the window beginning at the scheduled start. The text preview reflects the window when texting is configured. Neither product's window definition is a measured travel-time result.
A practical dispatch sequence
- Identify the likely miss. Compare current information with the promised window. Record the reason in neutral terms without unnecessary customer or employee details.
- Choose the next update owner. One dispatcher checks availability and owns the follow-up. A solo operator can use the same record on paper.
- Check the estimate. Offer a revised window only when it has a credible basis. Otherwise record ETA unknown and choose a real next update time that someone can honor.
- Review one message. Check recipient, channel, original window, new estimate or update time, and callback contact. Send through the approved channel when safe; never text while driving.
- Separate send from response. Record queued, sent and customer acknowledgment independently. If the proposed time does not work, offer actual available choices and wait for agreement.
- Reconcile the schedule and notifications. Keep the first promise and later changes distinguishable. Check whether automatic messages could still show an old or contradictory window. Do not silently move the appointment or assume the customer accepted a new slot.
Housecall Pro's notification guide says schedule-time and dispatch changes can trigger updated notices. Its On My Way button sends SMS, not email, and the Notify customer choice matters. A state change remains separate from message receipt. Inspect the relevant job rather than repeatedly clicking buttons or switching off notifications globally.
Copy the dispatch handoff
Use this blank sheet for one occurrence. Store real identifiers in your authorized system; do not include access codes or private customer information in a public example.
| Item | Observed or agreed value | Owner / next check |
|---|---|---|
| Internal visit ID and start time | ____________ | ____________ |
| Original promised window and time zone | ____________ | ____________ |
| Reason for likely miss, minimal detail | ____________ | ____________ |
| Named update owner | ____________ | ____________ |
| Revised estimate and confidence, or ETA unknown | ____________ | ____________ |
| Next update by date and time | ____________ | ____________ |
| Verified recipient and approved channel | ____________ | ____________ |
| Queued and sent timestamps separately | ____________ | ____________ |
| Response and accepted next step | ____________ | ____________ |
| Automated notification check | ____________ | ____________ |
| Closure and unresolved follow-up | ____________ | ____________ |
Three messages for three honest states
A credible revised window
Hello [name], we expect to miss the arrival window of [original window]. Our current estimate is [revised window]. Please tell [office contact] if that does not work for you. [Owner] will update you again by [time] if the estimate changes.
No reliable ETA yet
Hello [name], our technician is delayed and we do not yet have a reliable arrival estimate for [visit]. [Owner] will contact you by [specific time] with the next update. Please contact [office channel] if your availability has changed.
A new appointment proposed
Hello [name], the revised arrival time does not fit your availability. We can offer [real available option]. Would that work for you? This is a proposal; we will confirm the new appointment after you agree.
These are original templates for manual review, not a claim that every product automatically sends late notices. Housecall Pro's SMS customization guide requires texting setup and registration and uses shared templates. Keep customer-specific details out of global literal text and inspect variables and preview.
Use On My Way when departure is real
Jobber's On My Way guide describes choosing estimated minutes, a choice retained for the next send, and a preview with callback information. This is a selected estimate, not live GPS tracking. Check the saved minutes, recipient and callback number before sending when actually leaving. Availability depends on plan and supported region; do not assume every account can use it.
A late update and an On My Way message can serve different moments. The first acknowledges the missed promise; the second describes an actual departure. Review both so they do not contradict each other.
A fictional delay and three proposed checks
DEMO-VISIT-29 originally has a 10:00 to 12:00 window in Europe/Paris. At 10:40, dispatch learns that arrival is likely to be late. A 12:30 to 13:00 estimate is proposed after checking availability, but it is not a recorded outcome or an accepted reschedule. The office preserves the first window, asks whether the proposal works and owns the next update.
| Case | What the protocol should show | Actual result |
|---|---|---|
| Ordinary delay | Original window retained, checked revised estimate and one owner for the update. | ____________ |
| ETA unknown | No invented arrival time; named owner and specific next update time. | ____________ |
| Customer cannot accept new time | Proposal remains pending until an available option is agreed. | ____________ |
For wider routing questions, see the route software guide. The Jobber and Housecall Pro reviews cover broader product decisions. A running-late message does not need a new integration or a software purchase.
Editorial record
Who reviewed this page and what happens next.
Commercial relationships cannot change the evidence state, fit statement, caveats, or conclusion.
- Research and review
- Andre Ribeiro
- Published
- Last material review
- Next scheduled review
- Evidence scope
- Jobber and Housecall Pro official window and notification documentation reviewed 29 September 2026, including primary-source research handoff. Original dispatch worksheet, message drafts and unexecuted synthetic cases.
- Evidence state
- Documentation-informed original protocol only. No account test, customer message, delivery outcome, payment or schedule change was performed. Worksheets and synthetic cases have blank results.
Testing methodologyEditorial standardsCorrections and update log