ServiceTitan Dispatch Pro Limitations

The six documented limits, with sources

ServiceTitan publishes each Dispatch Pro and Optimize Technician Route constraint in their public help center. The six load-bearing limits, with the verbatim wording, source URL and operational impact:

1. No multi-technician or multi-day jobs

Source: Dispatch Pro FAQ, under “What Dispatch Pro will not do”.
Wording: “Assign multi-technician or multi-day jobs.”
What it means: Commercial install crews (lead tech plus helpers), multi-day commercial HVAC installs, planned-maintenance shutdowns spanning a weekend, multi-day plumbing renovations are all outside the optimizer’s scope. Dispatchers manage these manually. More on multi-day routing → · More on multi-technician jobs →

2. No on-call, time-off, or non-job event assignment

Source: Dispatch Pro FAQ.
Wording: “Assign a job to a technician who is on an on-call shift, a time-off shift, or has a non-job event.”
What it means: Emergency callouts during on-call shifts have to be assigned manually; the optimizer won’t suggest the on-call tech as a candidate. Same for technicians with non-job events like training, vehicle maintenance or admin time blocked on the calendar.

3. Arrival windows required, not inferred from notes

Source: Dispatch Pro FAQ.
Wording: “Place a job on the Dispatch Board before or after its arrival window or business hours.” And separately: Dispatch Pro “cannot read scheduling information from notes”.
What it means: Customer time preferences captured informally by the CSR (“customer prefers mornings”, “not before 10am”) get ignored by the optimizer unless they’re translated into formal arrival window configurations. Without an arrival window, Dispatch Pro treats any time within business hours as acceptable.

4. Managed technicians only

Source: Dispatch Pro overview.
Wording: “Dispatch Pro only works with managed technicians.”
What it means: Technicians configured outside the “managed” setup – irregular shifts, contractor relationships, special-case assignments – fall outside Dispatch Pro’s scope. The dispatch board still shows them; the optimizer just doesn’t auto-assign to them.

5. 70 jobs per day cap on Optimize Technician Route

Source: Optimize Technician Route help doc.
Wording: “You can optimize up to 70 jobs each day.”
What it means: Per technician, per day. For most residential trade workloads the cap is above the practical ceiling; for high-density routes (pest reapplications, urban delivery, last-mile field service) the cap becomes a real constraint that has to be planned around manually.

6. Residential Service and Replacement focus

Source: Dispatch Pro overview.
Wording: “Dispatch Pro is most effective for Residential Service and Replacement business types”, with examples given as “HVAC, plumbing, electrical, and more.”
What it means: The optimizer is tuned for the residential single-tech, single-day workload. Commercial work, distribution-style routes and recurring service programs sit outside the design target. More on recurring routes → · More on multi-depot routing →

Operating mechanics that matter

Two behaviors of Dispatch Pro are documented but worth flagging because they show up in customer reviews as friction points.

• 10-minute reshuffle cycle. Auto Mode reshuffles the Dispatch Board every 10 minutes during business hours and every hour outside business hours. Optimizes up to three days into the future. Third-party reviewers consistently flag that the 10-minute cycle can “over-optimize”, moving customer-confirmed arrival times for marginal route improvements. The newer “Protect Today’s Schedule” setting partially addresses this by letting dispatchers freeze the current day; Auto Mode still reshuffles future days.
• Auto Mode vs Assist Mode. Auto Mode auto-assigns; Assist Mode generates suggested optimizations for dispatcher review and approval. Most production deployments at scale run Assist Mode because over-optimization risk in Auto Mode is hard to absorb when CSRs have already confirmed arrival times with customers.

Smarter Routing is in private preview with general availability in summer 2026. ServiceTitan’s public materials describe it as adding a visual map builder for technician routes “to cut drive time and maximize jobs per day”. The scope appears to remain per-technician route optimization – the multi-day, multi-tech and multi-depot limits above don’t look targeted by Smarter Routing’s announced scope.

What eLogii covers, in one place

eLogii sits on top of ServiceTitan via the V2 REST API. For each documented Dispatch Pro limit, the eLogii equivalent is:

• Multi-day routes. Routes can span any horizon from a single day to a full month. Overnight stops and cross-day constraints modeled directly. Detail →
• Multi-technician crews. Jobs can require N technicians with specific skills, certifications and capacity. Crew composition rules. Lead-plus-helpers as a single optimization unit. Detail →
• Multi-depot routing. Single optimization run across multiple depots, branches or home start locations. Cross-depot assignment as an optimization decision. Detail →
• Recurring service patterns. Weekly, monthly, quarterly or bespoke cadences as first-class objects. Same-technician preferences. Multi-month planning horizons. Detail →
• No per-day job cap. The optimizer scales linearly with stop volume. High-density routes are first-class.
• Rule-based exception handling. Customer-confirmed slots are protected; over-optimization is bounded by operator-visible rules.
• Two engines, six configurable modes. Default and Advanced engines, three assignment modes plus three load-balancing modes. All callable via REST.

Frequently asked questions

What are the documented limitations of ServiceTitan Dispatch Pro?

From ServiceTitan’s own help center: Dispatch Pro will not assign multi-technician or multi-day jobs; it will not assign technicians on on-call shifts, time-off shifts or non-job events; it will not place a job before or after its arrival window or business hours; it only works with managed technicians; it cannot read scheduling information from notes. The built-in Optimize Technician Route caps at 70 jobs per day per technician and is single-tech, single-day only. Dispatch Pro is documented as “most effective for Residential Service and Replacement business types” (HVAC, plumbing, electrical).

What does the 70 jobs per day cap apply to?

ServiceTitan’s Optimize Technician Route help doc states: “You can optimize up to 70 jobs each day.” This is per technician, per day. The cap applies to the built-in (non-Pro) route optimizer. For most residential trade workloads the cap is well above the practical ceiling; for very high-density routes (urban delivery, pest control multi-stop visits, last-mile field service) the cap becomes a real constraint.

Why does Dispatch Pro require arrival windows?

The Dispatch Pro FAQ states the system “cannot read scheduling information from notes” and will not place a job before or after its formal arrival window or business hours. Arrival windows have to be explicitly configured on each job. If a job is booked without an arrival window, Dispatch Pro assumes any time within business hours is acceptable, which can produce assignments that don’t match customer expectations captured informally in the dispatcher’s notes.

What does “managed technicians only” mean?

Dispatch Pro only optimizes assignment for technicians configured as “managed” in ServiceTitan, which requires specific business unit, skillset and shift configurations. Technicians on irregular shifts, contractor relationships outside the managed roster, or special-case assignments fall outside Dispatch Pro’s scope. The dispatch board still shows them; Dispatch Pro just doesn’t auto-assign to them.

How does eLogii cover what Dispatch Pro doesn’t?

eLogii reads from ServiceTitan’s V2 REST API and runs the optimization layer that handles what Dispatch Pro explicitly doesn’t: multi-day routing (route spans across days with overnight stops), multi-technician crew jobs (lead-plus-helpers as a single optimization unit), multi-depot routing (cross-depot assignment as an optimization decision), recurring service patterns (weekly/monthly/quarterly cadences as first-class objects), rule-based re-optimization, no per-day stop cap. Routes are written back to ServiceTitan as appointments against the right technicians.