Dynamic rerouting that instantly recalculates routes on every change
A job runs long. A customer cancels. A tech calls in sick. AI Dispatcher detects the change for you. It recalculates the affected routes, updates customer ETAs, and surfaces the change in Dispatch Watch with a recommended fix. Your dispatcher reviews and approves with one tap.
Real-time dispatch software handles the disruptions before you notice them
A dispatch schedule breaks the moment something changes. FieldCamp watches for delays, cancellations, and no-shows in real time, then redistributes jobs across your crew based on proximity, skills, and capacity. No calls. No manual rebuild.
A job takes longer than expected
The 45-minute diagnostic turns into a 3-hour compressor replacement. Tech #4 is now behind on everything. The engine detects the delay once it crosses the configured threshold (default: 15 minutes). It identifies the at-risk downstream jobs and recommends shifting his afternoon appointments to nearby qualified techs. The dispatcher sees the recommendation in Dispatch Watch with reasoning, accepts with one tap, and customer ETAs go out automatically within 60 seconds. The SLA on each remaining job stays intact.
A customer cancels at the last minute
Mrs. Chen canceled her 1 PM appointment at 12:40. That leaves a 45-minute gap in Jake’s route. The Gap Filler agent scans the unassigned-job queue and scores candidates by priority, proximity, skill match, and how well they fit the freed window. The top recommendation lands in Dispatch Watch with the reasoning visible — accept it and Jake’s drive time actually goes down. The new job lands inside the customer’s promised time window.
A tech calls out sick
7 AM. Marcus isn’t coming in. Mark him unavailable on the board and his jobs flow back into the unassigned queue. The dispatch run picks them up and redistributes across the remaining crew based on skills, proximity, and capacity — the same scoring that runs every morning. The dispatcher reviews the new assignments in one place instead of phone-juggling five reassignments. This is workload balancing on autopilot.
An emergency call drops in
Burst pipe at a commercial property. It needs someone within the hour. The solver evaluates insertion points across your crew — proximity, skill match, time-window risk, and capacity — and picks the cheapest disruption. The recommendation: route Danny to the emergency, push two of his non-urgent jobs to tomorrow. Dispatcher confirms with one tap and the emergency dispatch is on the board. Dynamic dispatch handles the chaos so your team does not have to.
A live panel that surfaces what needs attention right now
Dispatch Watch is a live panel that surfaces time-sensitive field work: a tech falling behind, a cancellation gap, a job sitting unassigned too long. It runs in real time and highlights what needs your dispatcher’s attention right now, not after someone notices. Pair it with a dispatch assistant, and those alerts become actions. The agent fills cancellation gaps from the queue, redistributes a late tech’s remaining jobs, or slots an emergency to the nearest qualified tech, then logs exactly what it changed and why.
Fixed schedules vs. real-time dispatch software
One plans routes. The other plans routes, assigns techs, checks skills, respects customer preferences, and adjusts through the day — all in one pass.
Fixed schedules
- Morning plan is the final plan. Changes = manual rebuild.
- New jobs mid-day = call the office, check the board, pick a tech.
- Tech runs long = cascading delays all afternoon.
- Cancellations = empty time slots nobody fills.
- Dispatcher on the phone all day re-juggling.
- Re-routes happen 12+ hours later when next-day plan is built
Real-time dispatch software
- Schedule adjusts as things change, automatically.
- New jobs slotted in based on who’s closest and qualified.
- Delays absorbed across the team, not just one tech’s afternoon.
- Cancellation gaps are filled from the queue or by tightening routes.
- Dispatcher reviews changes, doesn’t rebuild from scratch.
- Re-routes happen in seconds, surfaced for approval in Dispatch Watch
How dynamic rerouting handles an HVAC company’s worst day
Jobs sync overnight. Dispatcher filters and dispatches. Routes appear on the map.
Schedule goes out. 5 techs, 22 jobs. Routes optimized. Everyone gets their board.
Marcus’s furnace install hits a corroded gas line. 90 minutes over. AI Dispatcher moves his 10:30 to Priya, she’s finishing early, two miles away. Dispatcher sees: “Reassigned 10:30 to Priya. Reason: Marcus is running long.”
Mrs. Chen cancels. 45-min gap in Jake’s route. The engine pulls an overnight booking — same neighborhood — and fills the slot. Jake’s day stays full.
Emergency: burst pipe at a restaurant. The system finds Danny (lightest afternoon, right certs), shifts his two non-urgent jobs to tomorrow morning, routes him to the emergency. Dispatcher confirms with one tap. Danny is on-site by 1:45.
24 jobs completed (22 original + 2 slotted in mid-day). No frantic phone chains. One dispatcher managed what used to take two.
↑ The dispatch board at 2 PM — routes adjusted, every tech on track.
Integrations and APIs
ServiceTitan
Pull jobs, customer history, tech skills. Push optimized routes back. Bidirectional sync.
Jobber
Sync job list and client preferences. Optimized schedules write back so techs see updates in their app.
Housecall Pro
Import jobs and availability. Route assignments push back with accurate ETAs.
REST API
Build your own integration. JSON in, optimized schedule out. Full docs available.
Your schedule shouldn’t need a babysitter
Drop in a sample week and watch the agent absorb a cancellation, a late job, and an emergency insert, without rebuilding the board. We’ll walk you through it on a 30-min call.
No credit card required · Live in 30 minutes · Cancel anytimeFrequently Asked Questions
What is dynamic rerouting in field service dispatch?
Dynamic rerouting is real-time route recalculation that triggers the moment a schedule changes — a job runs long, a customer cancels, a tech calls out, or an emergency drops in. FieldCamp’s AI Dispatcher detects the change, reshuffles affected routes across qualified techs based on proximity, skills, and capacity, updates customer ETAs, and surfaces the recommended fix in Dispatch Watch for one-tap approval.
How is dynamic rerouting different from regular route optimization?
Regular route optimization plans the morning route once and locks it in. Dynamic rerouting keeps adjusting through the day — every cancellation, delay, or emergency is absorbed in seconds instead of waiting for tomorrow’s plan. One plans the day; the other runs the day.
Does the AI reassign jobs automatically without my approval?
No. The engine recommends — your dispatcher approves. Every reroute lands in Dispatch Watch with the reasoning visible (why this tech, what changed, who’s impacted). Accept with one tap, or reject. Nothing moves on the board without a human in the loop.
How fast does it react when something changes?
Detection runs continuously. Once a delay crosses the configured threshold (default 15 minutes), or a cancellation/emergency lands, the recommendation surfaces in Dispatch Watch and customer ETAs update within ~60 seconds of approval.
What kind of disruptions does it handle?
Four big ones: (1) jobs running longer than estimated, (2) last-minute customer cancellations, (3) techs calling out sick, (4) emergency calls that need someone within the hour. It also handles smaller stuff — traffic delays, no-shows, parts runs.
Will customers know their ETA changed?
Yes. Once the dispatcher approves the reroute, customer ETAs auto-update and notifications go out — no one on the team has to call 8 customers and explain.
How does it pick which tech gets the reassigned job?
Four-factor scoring: proximity (drive time from current job), skill match (certifications, equipment), capacity (remaining hours, SLA risk on existing jobs), and customer time-window fit. The cheapest disruption wins.
Does it work with ServiceTitan, Jobber, or Housecall Pro?
Yes — bidirectional sync with ServiceTitan, Jobber, and Housecall Pro. Pulls jobs, customer history, and tech skills; pushes optimized
routes and ETAs back so techs see updates in their existing app. REST API available for custom stacks.