SERVICETITAN ROUTING LIMITS
Short answer: ServiceTitan does not optimize multi-day jobs. Dispatch Pro’s own FAQ states “will not assign multi-technician or multi-day jobs”, and ServiceTitan’s built-in Optimize Technician Route doc adds: “Only scheduled jobs assigned solely to that technician for one day are optimized”. Multi-day work can be booked manually through the project filter but the optimizer itself stays single-tech, single-day. eLogii adds multi-day routing on top of ServiceTitan via REST API.
Dispatch Pro will not assign multi-technician or multi-day jobs.
From help.servicetitan.com, under “What Dispatch Pro will not do”. Verified June 2026.
Three of ServiceTitan’s own published help articles define the limit on multi-day routing in their platform. The wording is consistent across them.
Both Auto Mode and Assist Mode operate within these constraints. Smarter Routing, currently in private preview with general availability in summer 2026, adds a visual map builder but is still scoped to per-technician route optimization – it doesn’t change the single-day scope.
Most residential service-and-replacement work is single-day: a tech goes out, fixes the problem or installs the equipment, leaves. Dispatch Pro is built for that. The work that runs into the limit is concrete.
None of these can be optimized by Dispatch Pro or by Optimize Technician Route in ServiceTitan today.
ServiceTitan does support multi-day work at the booking layer. The project filter lets dispatchers see and manage longer projects, multi-day jobs hold time on the dispatch board, and the platform tracks the relationship between the parent project and its child appointments. What ServiceTitan does not do is optimize across those days.
In practice, the workaround looks like this: a dispatcher creates separate single-day appointments linked to a parent project, assigns technicians by hand, blocks capacity manually, reconciles changes across days outside the optimizer. At single-digit numbers of multi-day jobs per week the workaround is manageable. Past around 100 technicians, the share of work that needs multi-day handling typically scales past what manual scheduling absorbs without dropped ETAs, double-bookings or planner burnout. Reviewers on G2 and Capterra consistently flag such friction at the upper end of ServiceTitan deployments.
eLogii’s optimizer models the day not as a fixed bucket but as a unit that can be repeated. A route can span a single day, multiple consecutive days or a date range; a technician can hold a multi-day route while other technicians stay on single-day routes. Constraints carry across days: capacity, skills, SLA windows, customer-confirmed slots, overnight stops, return-to-depot rules.
Specifics:
The combined deployment leaves ServiceTitan in place as the system of record. The integration runs over both products’ REST APIs.
Most teams complete the integration in 3 to 5 weeks. Typical first wave: the commercial business unit, the multi-day install team or the planned-maintenance program – whichever workflow is leaking the most against Dispatch Pro’s limits today.
30-minute custom simulation with your actual multi-day work, technicians and locations. Projected savings in drive time, planner hours and missed slot fees.
No. ServiceTitan’s Dispatch Pro FAQ states the system “will not assign multi-technician or multi-day jobs.” The built-in Optimize Technician Route help doc adds: “Only scheduled jobs assigned solely to that technician for one day are optimized”, with a cap of 70 jobs per day. Multi-day work can be booked manually through ServiceTitan’s project filter, but the routing optimizer itself stays single-technician, single-day.
No. There is no Dispatch Pro setting that turns on multi-day assignment. The Dispatch Pro FAQ lists “will not assign multi-technician or multi-day jobs” under the heading “What Dispatch Pro will not do”. The Smarter Routing feature, currently in private preview with general availability in summer 2026, adds a visual map builder but is still scoped to per-technician route optimization.
Manual scheduling through the dispatch board and the project filter. Dispatchers create separate single-day appointments linked to a parent project, assign technicians by hand, and reconcile work across days outside the optimizer. The project filter gives visibility into longer projects but doesn’t optimize across the days. At single-digit numbers of multi-day jobs per week the workaround is manageable; past around 100 technicians, the number of multi-day jobs typically scales past what manual scheduling absorbs cleanly.
Through ServiceTitan’s V2 REST API. eLogii reads jobs, customers and depots from ServiceTitan, runs the multi-day optimization (a single technician can hold a route that spans multiple days; overnight stops are modeled; capacity, skill and SLA constraints carry across days), and writes routes and ETAs back to ServiceTitan. ServiceTitan stays the system of record for invoicing, payments and customer comms; the multi-day routing happens in eLogii.
Common examples: commercial HVAC installs that take a small crew two to four days; multi-day plumbing renovations; planned maintenance shutdowns spanning a weekend; pest control treatments with a follow-up two days later; multi-day inspection programs across a campus. None of these are residential single-tech same-day jobs, which is what Dispatch Pro is designed for.
Last updated: June 2026. ServiceTitan limits are taken verbatim from help.servicetitan.com/docs/dispatch-pro-faq and help.servicetitan.com/docs/use-optimize-technician-route. eLogii capabilities documented at elogiiapidocs.apidog.io.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real jobs, depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you plan today. No slides, no generic benchmarks.