Get A Demo

You're viewing eLogii for Field Service. Distribution business? Switch to Distribution →

← Back to eLogii vs ServiceTitan

SERVICETITAN ROUTING LIMITS

ServiceTitan Multi-Day Routing

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 FAQ
No
“Will not assign multi-technician or multi-day jobs”. Verbatim from ServiceTitan’s published help center.
Optimize Technician Route
1 day
Single-tech, single-day only. Cap of 70 jobs per day. From ServiceTitan’s own help doc.
eLogii multi-day
1 day – 1 month
Plan a single day or an entire month in one run. Overnight stops and cross-day constraints modeled directly.
Integration
REST
eLogii reads from ServiceTitan’s V2 REST API, optimizes, writes routes and ETAs back. ServiceTitan stays the system of record.
From ServiceTitan’s Dispatch Pro FAQ

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.

What ServiceTitan documents about multi-day jobs

Three of ServiceTitan’s own published help articles define the limit on multi-day routing in their platform. The wording is consistent across them.

  • Dispatch Pro FAQ. Under the heading “What Dispatch Pro will not do”, the FAQ lists: “Assign multi-technician or multi-day jobs.” This is the ML-driven Dispatch Pro add-on, not a base feature.
  • Optimize Technician Route. The built-in (non-Pro) optimizer states: “Only scheduled jobs assigned solely to that technician for one day are optimized.” The same article adds: “You can optimize up to 70 jobs each day.”
  • Dispatch Pro overview. Reinforces that Dispatch Pro is “most effective for Residential Service and Replacement business types” (HVAC, plumbing, electrical), the operation shape where single-day jobs are the dominant workload.

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.

What multi-day jobs actually look like in the trades

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.

  • Commercial HVAC installs. A new rooftop unit at a small commercial site can take a lead technician plus one helper two to four days. The job is the same job, on the same site, with the same crew, across multiple days.
  • Planned maintenance shutdowns. Boiler or chiller PMs at a school, hospital or factory are often scheduled across a weekend or a holiday window. Two technicians, three days, hard start and end constraints.
  • Multi-day plumbing renovations. Bathroom rip-out and re-fit, kitchen re-pipe, sewer-line replacement – jobs that cross days by their nature.
  • Pest control multi-visit treatments. Initial treatment plus a follow-up two to seven days later as a single bookable program, with the same technician carrying the work where possible.
  • Multi-day inspection programs. Property condition surveys, life safety inspections across a campus, asbestos surveys – a defined set of stops that needs to complete across N days with capacity rolled across them.

None of these can be optimized by Dispatch Pro or by Optimize Technician Route in ServiceTitan today.

The workaround in ServiceTitan and where it breaks

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.

How eLogii handles multi-day routing

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:

  • Plan span. A single optimization run can target one day or up to a month. The same run produces routes for short single-day work and long multi-day work side by side.
  • Mixed driver days. Multi-day drivers and single-day drivers sit in the same plan. The optimizer assigns multi-day work to the right technicians without dragging single-day capacity into it.
  • Overnight stops. Drivers staying overnight are modeled directly. The plan reflects where the driver is at the end of each day, not just at the end of the run.
  • Cross-day constraints. A customer-confirmed window on day two protects against an over-optimization on day one. Skill requirements that need the same technician on day one and day three are enforceable.
  • REST callable. The optimizer is exposed through eLogii’s REST API, so multi-day plans can be triggered, locked, re-optimized or partially regenerated programmatically.

How the integration sits with ServiceTitan

The combined deployment leaves ServiceTitan in place as the system of record. The integration runs over both products’ REST APIs.

  1. Read from ServiceTitan. eLogii reads jobs, customers, technicians, locations and active projects from ServiceTitan’s V2 REST API. OAuth 2.0 Client Credentials grant; integration environment sandbox available for testing.
  2. Optimize in eLogii. The multi-day run produces routes with start times, end times, overnight stops and cross-day constraints honored. Planner reviews in eLogii’s dispatch desk or accepts an Auto run.
  3. Write back to ServiceTitan. Routes and ETAs are written back to ServiceTitan as appointment updates against the existing project. Completion data flows back to ServiceTitan for invoicing, payments and customer comms.
  4. Technician experience unchanged. The technician opens whichever field app they already use. The routing underneath gets the multi-day treatment.

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.

See multi-day routing on your real ServiceTitan jobs

30-minute custom simulation with your actual multi-day work, technicians and locations. Projected savings in drive time, planner hours and missed slot fees.

Book A Simulation

Frequently asked questions

Does ServiceTitan do multi-day route optimization?

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.

Can Dispatch Pro be configured to handle multi-day jobs?

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.

What is the workaround for multi-day jobs in ServiceTitan?

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.

How does eLogii add multi-day routing on top of ServiceTitan?

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.

What kinds of jobs need multi-day routing?

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

Run the numbers on your own routes

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.

What you’ll walk away with
  • Projected drive-time & mileage savingsModeled on a representative sample of your real routes
  • SLA & on-time impact estimateWhere the engine could take pressure off your planners today
  • Planner-hours & call-center load forecastHow much manual work eLogii would remove from your team
  • Implementation & integration shapeConcrete answer on what a 3–5 week rollout looks like, with or without keeping your FSM
30 minutes Your historical data No commitment