About this agent
Ships in the FieldCamp agent marketplace — because the schedule built across last week never reflects what this morning actually looks like.
Schedules are built piecemeal — a booking Tuesday, a reshuffle Thursday, an emergency wedged in Friday — and the result on Monday morning is a day that's technically scheduled and practically scrambled: two trips to the same side of town, a tight window after a long drive, the priority job sitting third.
The optimizer reads the day fresh at 6 AM, when it's still cheap to change. It proposes the tighter version: reordered stops, adjusted timings, priorities surfaced — with the reasoning per change. Your dispatcher reviews it with coffee and applies what makes sense; ten minutes of robot homework, human judgment on top.
What it actually does
Trigger: Daily at 6 AM
- 1
Runs before the day starts
schedule_6am6 AM, every day — after overnight changes, before the trucks load.
- 2
Reads today as it actually is
read_days_scheduleEvery visit, window, territory, and assignment — including what changed overnight.
- 3
Finds the scramble
find_inefficienciesBacktracks, tight windows after long drives, priority work buried mid-day.
- 4
Proposes the tighter day
propose_planReordered stops and timing changes, each with its reasoning — applied only by your dispatcher.
What you get
A 6 AM proposal for a tighter day — reasoning per change, dispatcher judgment on top.
A run, as you’d see it
Agent runs land on a timeline — what fired, what the agent found, and the action waiting for a human. This is that screen.
Morning plan ready
Today · 23 visits · 6 techs
Details
Found
2 backtracks · 1 buried priority
Summary
Swapping Marcus's stops 2 and 4 removes a crosstown backtrack (−38 min drive). The Riverside priority job sits third on Dre's run — recommend first. One tight window flagged: 11 AM install after a 50-minute drive.
Proposes only — your dispatcher applies. Schedule authority stays human; the agent does the 6 AM arithmetic.
By trade
Same agent, configured to how your vertical actually works.
Emergency capacity stays protected per territory in the proposed plan.
Crew-based routing — the proposal moves crews and their equipment together.
Questions, answered
Does it move jobs on its own?
No. It proposes; your dispatcher applies. Every suggested change carries its reasoning so the review takes minutes, and what gets applied is always a human call.
How is this different from the AI Dispatcher?
The AI Dispatcher is FieldCamp's full assignment engine. This template is its lightweight morning ritual — a daily review-and-propose pass on the schedule you already have. Many shops start here and graduate.
What does it optimize for?
Less drive time, sane windows, priorities first — in that order by default, tunable during setup if your shop weighs things differently.