---
title: "Dynamic Rerouting"
url: "https://fieldcamp.ai/ai-dispatcher/dynamic-rerouting/"
date: "2026-05-06T05:18:59+00:00"
modified: "2026-07-10T14:21:20+00:00"
type: "WebPage"
resource: "https://fieldcamp.ai/ai-dispatcher/dynamic-rerouting/"
timestamp: "2026-07-10T14:21:20+00:00"
author:
  name: "ai-boss"
  url: "https://cms.fieldcamp.ai"
word_count: 1328
reading_time: "7 min read"
summary: "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…"
description: "Dynamic rerouting recalculates affected routes the second something changes. Delays, cancellations, no-shows handled automatically. Book a demo."
keywords: "Dynamic Rerouting"
language: "en"
schema_type: "WebPage"
---

# Dynamic Rerouting

_Published: May 6, 2026_  
_Author: ai-boss_  

![Dynamic Rerouting Feature Image](https://cms.fieldcamp.ai/wp-content/uploads/2026/05/ChatGPT-Image-May-14-2026-05_17_06-PM-1024x769.png)

> 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…

#  <svg fill="none" height="14" stroke="#E8935A" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="14" xmlns="http://www.w3.org/2000/svg"><polygon points="13 2 3 14 12 14 11 22 21 10 12 10 13 2"></polygon></svg> DYNAMIC REROUTING
Watch what changes when the schedule re-optimizes itself — AI vs. a manual board on the same jobs:

## Dynamic rerouting that instantly recalculates routes on every change

A job runs long. A customer cancels. A tech calls in sick. [AI Dispatcher](https://fieldcamp.ai/ai-dispatcher/) detects the change for you. It recalculates the affected routes, updates customer ETAs, and surfaces the change in [Dispatch Watch](https://docs.fieldcamp.ai/ai-dispatcher/live-dispatch-map-timeline) with a recommended fix. Your [dispatcher reviews and approves](https://docs.fieldcamp.ai/ai-dispatcher/accepting-or-rejecting-ai-dispatch-suggestions) with one tap.<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>

[Get a Free Demo <gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>](https://calendly.com/jeel-fieldcamp/30min)![FieldCamp AI Dispatcher schedule view showing Amelia Ward (HVAC Installation, 8.0h available) with two assigned jobs — Orin Williams at 9:00–10:00 AM and Peter Jackson at 11:30 AM–12:00 PM — and 2 unassigned jobs (Daxon Reid, Job 21 – 60m at 500 Business Park; Liora Winslow, Job 22 – 40m at 640 Business Park, New York) awaiting dispatch.](https://cms.fieldcamp.ai/wp-content/uploads/2026/04/01-1024x622.png)01

### A job takes longer than expected<gwmw style="display:none;"></gwmw>

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](https://docs.fieldcamp.ai/ai-dispatcher/handle-late-jobs-and-cancellations) 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](https://fieldcamp.ai/ai-dispatcher/sla-aware-scheduling/) on each remaining job stays intact.<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>

02

### A customer cancels at the last minute

[Mrs. Chen canceled her 1 PM appointment at 12:40.](https://fieldcamp.ai/ai-dispatcher/same-day-reschedule/) That leaves a 45-minute gap in Jake’s route. The [Gap Filler agent](https://docs.fieldcamp.ai/ai-dispatcher/dispatch-assistants-agents) 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](https://fieldcamp.ai/ai-dispatcher/time-window-optimization/).

![FieldCamp AI Dispatcher interface showing the Dispatch Assistants panel with a Dispatch Watch card indicating no urgent field work pending, alongside a recent activity counter showing 10 completed actions across the workspace.](https://cms.fieldcamp.ai/wp-content/uploads/2026/04/02-1024x622.png)![FieldCamp AI Dispatcher before-and-after view showing Jake Morrison's schedule. Before: a cancelled 1:00–2:00 pm slot for Mrs. Chen leaves a 45-minute gap. After AI rerouted: Peter Jackson from the queue fills the slot at the same neighborhood, 5-minute drive away.](https://cms.fieldcamp.ai/wp-content/uploads/2026/04/03-1024x622.png)03

### 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](https://fieldcamp.ai/ai-dispatcher/workload-balancing/) on autopilot.<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>

04

### An emergency call drops in

Burst pipe at a commercial property. It needs someone within the hour. The [solver evaluates insertion points](https://docs.fieldcamp.ai/ai-dispatcher/how-ai-dispatcher-works-under-the-hood) 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](https://fieldcamp.ai/ai-dispatcher/emergency-job-handling/) is on the board. Dynamic dispatch handles the chaos so your team does not have to.

<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>

![FieldCamp AI Dispatcher dashboard showing Marcus Johnson called out with 5 jobs needing reassignment. AI redistributes all 5 jobs to Carlos Martinez and Susan Williams based on proximity, skill match, and available capacity, with each reassignment reason shown.](https://cms.fieldcamp.ai/wp-content/uploads/2026/04/04-1024x622.png)![FieldCamp AI Dispatcher before-and-after view showing Jake Morrison's afternoon schedule. After an emergency burst pipe call at Greenfield Commercial, AI inserts the urgent job at 1:15–2:45 pm and moves two low-priority jobs (Sana Khan and Darling Quarter Offices) to Wednesday, keeping medium-priority Raj Mehta on schedule.](https://cms.fieldcamp.ai/wp-content/uploads/2026/04/05-1024x622.png)05

### A live panel that surfaces what needs attention right now<gwmw style="display:none;"></gwmw>

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

### 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<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>

Real-time dispatch software

### 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<gwmw style="display:none;"></gwmw>

7:00 AMSchedule is plannedSchedule goes out. 5 techs, 22 jobs. Routes optimized. Everyone gets their board.

9:15 AMEmergency AlertMarcus’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.”

11:40 AMNew job comes inMrs. 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.

1:10 PMAnother EmergencyEmergency: 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.

EODProductive Day24 jobs completed (22 original + 2 slotted in mid-day). No frantic phone chains. One dispatcher managed what used to take two.

     <svg fill="none" height="12" stroke="#aaa" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="12" xmlns="http://www.w3.org/2000/svg"><circle cx="11" cy="11" r="8"></circle></svg> dispatcher.fieldcamp.ai/   <video autoplay="" loop="" muted="" playsinline="" src="https://cms.fieldcamp.ai/wp-content/uploads/2026/04/dynamic-reroute-1.mp4"></video> ↑ The dispatch board at 2 PM — routes adjusted, every tech on track.

#### ServiceTitan

Pull jobs, customer history, tech skills. Push optimized routes back. [Bidirectional sync](https://docs.fieldcamp.ai/ai-dispatcher/connecting-fieldcamp-to-dispatcher).

#### Jobber

Sync job list and client preferences. Optimized schedules write back so techs see updates in their app.

#### Housecall Pro<gwmw style="display:none;"></gwmw>

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.

READY?

## Your schedule shouldn’t need a babysitter<gwmw style="display:none;"></gwmw>

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.<gwmw style="display:none;"></gwmw>

[Book a Demo<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>](https://calendly.com/jeel-fieldcamp/30min)No credit card required · Live in 30 minutes · Cancel anytime

## Frequently Asked Questions<gwmw style="display:none;"></gwmw>

**What is dynamic rerouting in field service dispatch?<gwmw style="display:none;"></gwmw>**

[Dynamic rerouting is real-time route recalculation that triggers the moment a schedule changes](https://fieldcamp.ai/ai-dispatcher/dynamic-rerouting/) — 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.<gwmw style="display:none;"></gwmw>

**How is dynamic rerouting different from regular route optimization?<gwmw style="display:none;"></gwmw>**

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?<gwmw style="display:none;"></gwmw>**

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.<gwmw style="display:none;"></gwmw>

**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.<gwmw style="display:none;"></gwmw>

**What kind of disruptions does it handle?<gwmw style="display:none;"></gwmw>**

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?<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>**

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.<gwmw style="display: none; background-color: transparent;"></gwmw><gwmw style="display: none; background-color: transparent;"></gwmw>

**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.<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>

**Does it work with ServiceTitan, Jobber, or Housecall Pro?<gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw><gwmw style="display:none;"></gwmw>**

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.

<gwmw style="display:none;"></gwmw>


---

_View the original post at: [https://fieldcamp.ai/ai-dispatcher/dynamic-rerouting/](https://fieldcamp.ai/ai-dispatcher/dynamic-rerouting/)_  
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_  
_Generated: 2026-07-10 14:21:21 UTC_  
