When the day breaks, the schedule should tell the truth.
A running-long job should be visible before it becomes three unexplained no-shows. This story follows a dispatcher through a conflict, qualified reassignment, human-approved update, and day-end closeout.
Dispatcher or office manager · plumbing or HVAC · the first job runs long and the next customer is waiting
What happens today
Today the change travels by text and memory. The dispatcher knows the conflict but the field and customer receive different versions of the plan.
Why it matters
The risk is an unqualified assignment, a false promised time, and unfinished work silently becoming tomorrow's problem.
Where this starts
One active job is running long, a later job needs attention, and the business has configured eligibility and assignment rules.
The workflow
- 1The dispatcher opens the board and sees the running-long exception beside the affected appointment.
- 2The dispatcher confirms the real field status and records the reason rather than treating the delay as invisible.
- 3The board filters qualified alternatives; the dispatcher selects an eligible technician or keeps the work as an owned exception.
- 4A customer update can be drafted, but the designated person approves the message before it is released.
- 5The field role refreshes the permitted route, and day-end review assigns any unfinished work a next date, owner, and reason.
Where a person decides
The dispatcher chooses the operational response; a person approves any customer promise; a manager owns any qualification override the policy permits.
If it does not go to plan
If no eligible alternative exists, the work escalates under the business's own on-call policy and the conflict stays visible. Nothing bypasses configured rules or claims calendar synchronization.
Where this ends
The schedule contains either a truthful reassignment or a named exception; day-end has no ownerless unfinished item.
What you can see
Seeded dispatch board, qualification state, customer-message approval state, field route refresh, and day-end queue.
Why that is useful
The dispatcher works one operating board instead of reconciling texts, calls, and a whiteboard.
What this does not claim. No two-way Google or Outlook calendar sync, hardware telematics, automatic customer promise, or real-time location claim is made.
Workflow reviewed 2026-08-13