ServiceTitan Multi-Technician Dispatch

What ServiceTitan documents about multi-technician jobs

The Dispatch Pro FAQ is the load-bearing source. The exact wording from ServiceTitan’s own published help center, under the heading “What Dispatch Pro will not do”, is: “Assign multi-technician or multi-day jobs.” That single sentence covers both crew dispatch and multi-day routing in one constraint.

Two related ServiceTitan articles reinforce the scope:

• Dispatch Pro overview describes Dispatch Pro as “most effective for Residential Service and Replacement business types” (HVAC, plumbing, electrical) – the operation shape where one tech per job is the dominant workload.
• Optimize Technician Route (the built-in, non-Pro optimizer) is described as routing “scheduled jobs assigned solely to that technician for one day”. One technician, one day. Crews are not in scope.

Smarter Routing is in private preview with general availability in summer 2026. ServiceTitan’s public materials describe it as a visual map builder for technician routes. There is no announced multi-technician or crew capability in that scope either.

What multi-technician jobs actually look like

Crew work is concentrated in commercial trade operations, complex repairs and safety-required jobs. The shape is consistent: more than one technician needs to be at the same site at the same time, doing complementary work, treated as a single bookable unit.

• Commercial HVAC install crews. A new rooftop unit or chiller install commonly runs lead-tech plus one or two helpers. The crew arrives together, works together, leaves together. Booking three separate appointments and hoping they overlap doesn’t model the job.
• Rooftop and rigging work. Anything requiring a crane, lift or two-person safety pair has to dispatch a crew together by code, not just by preference.
• Cross-trade specialist pairings. An HVAC repair that needs an electrician to make a panel change, a plumbing job that needs a tile setter to close it out – two specialists, same site, sequenced work.
• Confined-space and hazardous environments. Two-person rule by safety policy, regardless of the technical work being done.
• Training and mentoring runs. Junior tech shadowing a senior on a billable job for capability ramp. Both must be assigned to the same appointment, with capacity adjusted for the shadow time.

None of these dispatch correctly through Dispatch Pro as a single unit.

The workaround in ServiceTitan and where it breaks

The standard ServiceTitan workaround for crew jobs is to book the lead technician’s appointment as the “real” job and add helpers either as separate appointments at the same time slot or as notes on the job. Dispatchers hold the crew composition in their heads or in a spreadsheet outside the platform. When the lead tech’s schedule changes, the dispatcher manually moves the helpers’ appointments to match.

At a handful of crew jobs per week the workaround is manageable. At a commercial-heavy operation running 20+ crew jobs per week across multiple technicians, the manual coordination becomes a meaningful share of dispatcher time. Customer-facing ETAs drift when the lead tech’s appointment is rescheduled by the optimizer and the helpers aren’t carried with it. Capacity gets double-counted when a helper shows up on the dispatch board as if they’re free. The friction is real but doesn’t hurt under around 100 technicians; past it, the cost is concrete.

How eLogii handles multi-technician dispatch

eLogii treats a job’s technician requirement as a constraint, not a fixed assumption. A job can require one technician, two technicians or N technicians, each with specific skills, certifications and capacity. The optimizer treats the crew as a single bookable unit and routes all required technicians to the same site at the same time.

• Skill and certification stacking. A job can require “1 master electrician + 1 helper with lift certification”. The optimizer finds the combination that satisfies the requirement without violating other constraints.
• Crew composition rules. Operator-visible rules let planners specify pairings: “always send the lead tech who quoted the job”, “trainee assignments must include a senior tech”, “two-person rule for hazardous sites”.
• Per-tech start and end. Helpers can come from a different depot or home location than the lead. The optimizer doesn’t require the crew to start the day together.
• Capacity correctly counted. A two-tech job blocks both technicians’ capacity for the right duration. No double-counting, no phantom availability.
• Reschedule together. When the job moves, the whole crew moves. ETAs, customer notifications and depot returns stay coherent.

How the integration sits with ServiceTitan

ServiceTitan remains the system of record. eLogii reads from ServiceTitan’s V2 REST API, runs the multi-resource optimization, writes appointments back to ServiceTitan against the right technicians.

1. Read. Jobs, customer records, technicians, skills, certifications and locations sync from ServiceTitan. Crew-requiring job types are flagged in ServiceTitan job types or via a custom field.
2. Optimize. eLogii runs the multi-resource assignment, respecting skill constraints, certification requirements, capacity, depots and SLA windows. Crew composition rules apply.
3. Write back. Each technician’s appointment is written back to ServiceTitan as a separate appointment record linked to the same job ID. Capacity and ETAs reflect the crew.
4. Technician experience unchanged. Each technician opens the field app they already use, sees their part of the crew job. Completion writes back to ServiceTitan for invoicing.

Most teams complete the integration in 3 to 5 weeks. Common first wave: the commercial install crew, the heavy-repair team or the planned-maintenance program – whichever has the most crew jobs today.

Frequently asked questions

Does ServiceTitan support multi-technician jobs in Dispatch Pro?

No. ServiceTitan’s Dispatch Pro FAQ states the system “will not assign multi-technician or multi-day jobs.” The optimizer is built for one technician per job. Crew work can be booked manually through the dispatch board (book the lead tech, add helpers as separate appointments or via notes), but the optimization itself only sees one technician per job.

Can ServiceTitan dispatch a lead technician plus helpers?

Manually, yes. Optimized, no. ServiceTitan’s dispatch board can hold multiple appointments at the same site at the same time, and dispatchers can pin a lead tech and add helpers. What Dispatch Pro will not do is route the crew together as a single optimization unit.

What kinds of jobs need multi-technician routing?

Common examples: commercial HVAC installs that need a lead tech plus one or two helpers; rooftop unit changeouts with rigging; complex repairs where two specialists are needed (e.g. electrician plus HVAC); safety-required pairings (working in confined spaces, lift work, hazardous environments); training scenarios where a senior tech mentors a junior. None of these are residential single-tech same-day jobs, which is what Dispatch Pro is designed for.

How does eLogii handle multi-technician dispatch on top of ServiceTitan?

Through ServiceTitan’s V2 REST API. eLogii reads jobs, customers, technicians and skills from ServiceTitan, runs the multi-resource optimization (each job can require N technicians with specific skill, capacity and certification constraints), and writes appointments back to ServiceTitan against the right technicians. ServiceTitan stays the system of record for invoicing, payments and customer comms; the crew composition and routing happens in eLogii.

Does Smarter Routing add multi-technician support?

No. Smarter Routing is in private preview with general availability scheduled for summer 2026 and adds a visual map builder for technician routes. It is still scoped to per-technician route optimization. ServiceTitan has not announced multi-technician or crew dispatch as part of Smarter Routing’s scope.