eLogii + ServiceTitan: When to Add eLogii to ServiceTitan

Where each platform leads

ServiceTitan and eLogii sit in different layers of the same stack. ServiceTitan is the operating system for the trade business. eLogii is the routing and optimization engine that sits underneath the dispatch board.

The combined deployment pattern is straightforward: ServiceTitan stays the system of record for jobs, customers, invoicing and payments. eLogii reads jobs and depots from ServiceTitan over the V2 REST API, runs the optimization across the routing horizons ServiceTitan’s Dispatch Pro doesn’t cover, writes routes and ETAs back. The technician opens the field app they already use; the routing underneath gets deeper. ServiceTitan keeps the workflows it’s good at; eLogii handles the rest of the routing problem in parallel.

What ServiceTitan does well, what eLogii adds

This is not a head-to-head comparison – the two products solve different problems and run in different layers of the stack. Keep ServiceTitan for what it’s built for; add eLogii for what comes next. The tables below cite ServiceTitan’s own help docs verbatim where they document a routing limit.

What ServiceTitan’s routing covers

What eLogii layers on top

Sources: ServiceTitan’s own help center (Dispatch Pro FAQ, Optimize Technician Route, Dispatch Pro overview); eLogii optimization engines. Verified June 2026.

CSR call handling vs slot booking co-pilot – how they work together

One area that gets conflated: ServiceTitan’s CSR booking workflow and eLogii’s slot booking co-pilot are different surfaces solving adjacent problems. ServiceTitan’s CSR workflow is the call-handling layer (caller-ID lookup, scripts, capacity warnings, lead attribution). eLogii’s slot booking co-pilot is the route-aware availability calculation (given the current optimized plan, which slots can actually be offered without breaking routes). In a combined deployment, ServiceTitan’s CSR fields the call, queries eLogii’s slot availability over the REST API, and confirms a slot back to the customer that’s already optimization-aware.

Field execution & customer experience

API surface & developer experience

Sources: eLogii API documentation, ServiceTitan Developer Portal and ServiceTitan rate-limit docs. Verified June 2026.

Scale, security & commercial

Sources: ServiceTitan FY2026 10-K and Q3 FY2026 earnings; Gartner Peer Insights; Capterra and G2 reviews. Verified June 2026.

Route optimization, in detail

This is where ServiceTitan and eLogii diverge most sharply, and where the difference is best evidenced by ServiceTitan’s own documentation rather than competing marketing claims. The relevant product surface inside ServiceTitan is three distinct things: the built-in Optimize Technician Route tool, the Dispatch Pro ML-driven add-on, and Smarter Routing (in private preview, GA summer 2026).

ServiceTitan’s routing scope, as ServiceTitan describes it

Three published limits, taken directly from ServiceTitan’s help center, define the routing surface:

• Single-technician, single-day for built-in optimization. The Optimize Technician Route help doc states: “Only scheduled jobs assigned solely to that technician for one day are optimized.” The same doc adds: “You can optimize up to 70 jobs each day.”
• Residential focus for Dispatch Pro. The Dispatch Pro overview states it is “most effective for Residential Service and Replacement businesses... HVAC, plumbing, electrical, and more.”
• No multi-day, no multi-tech for Dispatch Pro. The Dispatch Pro FAQ states the system “will not assign multi-technician or multi-day jobs.” It also will not assign technicians on on-call shifts, time-off shifts or non-job events, cannot read scheduling info from notes, and only works with managed technicians.

The Dispatch Pro optimization horizon is three days into the future, with the dispatch board reshuffled every 10 minutes during business hours and every hour outside business hours. Two modes are documented: Auto Mode (auto-assigns) and Assist Mode (suggests for dispatcher approval). Third-party reviewers note that Auto Mode’s 10-minute reshuffle cycle can “over-optimize”, moving jobs away from customer-confirmed arrival times. Smarter Routing, currently in private preview with general availability scheduled for summer 2026, adds a visual map builder for more granular control over technician routes. The fact that ServiceTitan acquired FieldRoutes in January 2022 specifically to handle pest control and lawn care recurring-route optimization is itself an acknowledgement that recurring multi-stop optimization is not what their core Dispatch Pro engine was designed to do.

eLogii’s routing scope

eLogii’s optimizer is built around two engines and six configurable modes, all callable via REST and exposed to the planner as controls they can see and adjust.

• Two engines. The Default engine optimizes 100 tasks in under 10 seconds for high-throughput daily planning. The Advanced engine takes more factors into account and is the choice for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Three assignment modes. Optimize Everything (creates fresh routes including all assignments), Add to Routes, Keep Existing Assignments (incorporates new tasks into existing routes while preserving driver assignments), and Add to Routes, Keep Existing Assignments and ETAs (inserts new tasks into available slots without modifying existing stop sequences or ETAs).
• Three load-balancing modes. Most Efficient Routes (fewest vehicles), Balance the Minimum Number of Routes (across load, time, distance or job count), and Use All Vehicles / Finish as Soon as Possible (maximise speed).

Beyond the modes, eLogii ships the operational surface ServiceTitan does not lead on: multi-day and long-haul routing (“plan a single day or an entire month in one run”), multi-depot (“route across multiple depots, branches, or home start locations in a single run”), recurring patterns via task and route template groups (weekly, monthly, quarterly, bespoke cadences modeled directly, not bolted on), multi-technician crew jobs with skills and capacity constraints, and rule-based re-optimization the operator can see and steer.

What this means in practice

Under around 100 in the field, ServiceTitan plus Dispatch Pro typically covers the routing problem well: residential single-tech, single-day work with a three-day forward horizon. Above that, the work breaks the model. A commercial install that takes two technicians and three days; a recurring quarterly program with a few thousand stops to balance; a regional team running across multiple service centers. The load-bearing line in Dispatch Pro’s own FAQ – “will not assign multi-technician or multi-day jobs” – is what rules those out. eLogii layers on top via REST API to handle them, leaving ServiceTitan in place for everything else.

The 100-tech threshold

Below it, ServiceTitan plus Dispatch Pro is usually the right tool full stop. Above it, eLogii starts to earn its keep. Two things drive the inflection.

• Headcount. Under around 100 technicians, residential single-tech/single-day work is the dominant workload and Dispatch Pro fits it well. Above it, the share of work that breaks the single-day, single-tech model grows fast enough that Dispatch Pro’s documented limits start to show up on the dispatch board every week, not as edge cases.
• Mix. When the work isn’t all residential single-tech – a commercial install book, a regional crew structure, a recurring service program – the optimizer needs to model jobs that span days, crews and depots. Dispatch Pro doesn’t.

The integration sits over both products’ REST APIs. ServiceTitan’s V2 API has separate transactional and data-export endpoints with documented OAuth 2.0 auth and a dedicated integration environment for testing. eLogii’s REST API exposes the optimizer directly with a full-parity sandbox. There’s no licensing hand-off, no marketplace listing required, no waiting on a roadmap; the technical pieces are all already in place on both sides.

Dispatcher tooling depth

ServiceTitan’s dispatch board (Map 2.0, plus Dispatch Pro’s ML-driven Auto/Assist modes) is built for residential CSR-to-tech workflows: incoming call, capacity check, assignment, on-the-way SMS, arrival confirmation. eLogii adds a deeper dispatch-desk and customer experience surface on top, for the moment dispatcher tooling itself becomes the bottleneck rather than the call-handling layer:

• Slot booking co-pilot. When ServiceTitan’s CSR is offering a customer a time window, eLogii’s slot availability returns only slots that already fit the current optimized plan. Cuts failed visits ~35%.
• Customer-driven rescheduling. Around 70% of reschedule requests handled without coordinator involvement. The customer picks a slot that already fits the plan and the route re-optimizes.
• Embedded tracking content. NPS surveys, safety briefings, access codes, pest treatment instructions, pushed onto the tracking page itself rather than handed off to a separate channel.
• Multi-brand tracking. Three brands run from one dispatch desk, each with its own logo, colors and layout.
• Map-native dispatch ops. Drag-and-drop reassignment with automatic ETA recalc on both routes; polygon, freehand and rectangle map selection; bulk actions on hundreds of stops; Gantt-style route timeline alongside the map; 13 historical segments refreshed overnight.
• Rule-based exception handling. Reroute a no-access visit to the nearest technician with the right skill, but don’t move any customer-confirmed slots in the next 90 minutes. Visible to the planner, not buried in a black-box optimizer.
• Workflow analytics. Average time per step, skip rates, error patterns, completion data. Where the technician hours actually went, not just where the routes went.

Brymec lifted productivity 30% and routing efficiency 20% on eLogii. ATS Building Products improved deliveries per route by ~98%. Porcelanosa runs eLogii with 95%+ ETA accuracy on daily distribution. These are exactly the operational outcomes a CSR-centric dispatch board isn’t designed to produce, because that’s not the problem it was built for.

Running eLogii alongside ServiceTitan, FieldRoutes and the wider stack

At scale, the stack typically looks like this: an FSM for field execution and paperwork (ServiceTitan, FieldRoutes, Simpro, Joblogic, Salesforce Field Service, MS Dynamics 365 Field Service), an ERP for finance, inventory and customer master data (SAP, NetSuite, MS Dynamics 365 BC, Sage, Acumatica), telematics for the vehicles (Samsara, Geotab, TomTom), and a routing/optimization layer underneath the dispatch board.

eLogii is built for that shape. It plugs into ServiceTitan, FieldRoutes or whichever FSM you already run as the routing depth layer, leaving CSR workflow, pricebook, payments, marketing automation and accounting where they already are. The technician opens the FSM’s field app on site; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into the FSM. The most common patterns:

• ServiceTitan + eLogii. ServiceTitan owns residential CSR, dispatch board, pricebook, payments, marketing. eLogii owns the commercial-distribution business unit or multi-depot field service business, including multi-day and recurring routing ServiceTitan’s Dispatch Pro explicitly doesn’t cover. Integration via the two products’ REST APIs.
• FieldRoutes + eLogii. If your pest control or lawn care operation runs on FieldRoutes and the recurring-window optimizer doesn’t reach the multi-depot, multi-day or constraint-heavy planning you need, eLogii adds that layer via REST API on top.
• Simpro / Salesforce FS / MS D365 FS + eLogii. The FSM owns commercial field service operations, eLogii owns the advanced routing across crews and depots. Pre-built Simpro integration; Salesforce, MS D365 and ServiceNow via the REST API.

What makes the stack pattern straightforward:

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Zones, Schedules, Forms and Optimization, designed for clean integration into a wider stack.
• Full-parity sandbox at api-sandbox.elogii.com so integration work can run in parallel with the existing FSM/ERP rollout.
• Webhooks with live driver GPS and ETA stream push real-time state back to your FSM, dispatcher view or customer-facing app. No polling, no cron jobs, no stale data.
• Bulk operations. POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• FSM, ERP and telematics independent. Customers running FieldRoutes, Simpro, Salesforce FS or MS D365 FS use eLogii for advanced routing alongside the FSM they already chose.

ServiceTitan itself provides a V2 REST API with OAuth 2.0 Client Credentials, an integration environment at api-integration.servicetitan.io and a 60-call/sec rate limit, with transactional and data-export endpoints across Jobs, Projects, Invoices, Payroll, Pricebook, CRM, Dispatch and Inventory. The two APIs combine cleanly: eLogii calls ServiceTitan to read jobs and write completion back; ServiceTitan calls eLogii to push new jobs into the optimization layer.

API surface, side by side

Both companies publish a REST API and a sandbox environment. ServiceTitan’s API is substantially broader because the product is broader; eLogii’s API is deeper specifically in routing, optimization and field execution.

eLogii API

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Customers, Zones, Forms, Schedules and Optimization. Full reference.
• Authentication: ApiKey header, generated in Dashboard > Configuration > API Keys. Simple to integrate, no OAuth round-trip required for machine-to-machine.
• Sandbox: api-sandbox.elogii.com, full parity with production at api-35.elogii.com.
• Bulk operations: POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• Optimization callable via REST: all six modes available programmatically; planners can lock specific routes, manually reorder stops, or re-run with new constraints.
• Seven webhook event types, including Driver/Task Tracking Update with live GPS stream and Route ETAs Update. No polling, no cron jobs.
• Custom fields end-to-end through driver app, webhooks and reporting.
• FSM, ERP and telematics independent via REST API, including SAP, Oracle NetSuite, MS Dynamics 365 Business Central, Sage, Acumatica, IFS, Infor, ServiceTitan, FieldRoutes, Salesforce Field Service, Simpro, Joblogic, Samsara and Geotab.

ServiceTitan API

• V2 REST at api.servicetitan.io with a developer portal at developer.servicetitan.io. Substantially broader API surface than eLogii because the product is substantially broader.
• Authentication: OAuth 2.0 Client Credentials grant. App key + tenant key model. Token endpoint at auth-integration.servicetitan.io/connect/token for sandbox, separate production endpoint.
• Sandbox: integration environment at api-integration.servicetitan.io, separate from production.
• Modules: Jobs, Projects, Invoices, Payroll, Pricebook, CRM, Dispatch, Inventory, Reporting, Payroll, Memberships, plus separate Data Export endpoints under /export for high-volume sync.
• Rate limits: 60 calls/sec per app per tenant by default; Reporting APIs limited to 5 of the same report per minute per tenant.
• Webhooks on job, customer, invoice and project lifecycle events; live-GPS event coverage is product-feature-driven and varies.
• What’s not externally callable: Dispatch Pro’s ML orchestration runs as an internal product surface; the optimization engine itself is not exposed as a public REST endpoint.

For an integration team, the typical pattern when both products are in the stack: ServiceTitan owns the system-of-record for jobs, customers, invoicing and payments; eLogii reads jobs/customers/depots from ServiceTitan over the V2 REST API, runs optimization, writes routes and ETAs back; ServiceTitan’s field app or eLogii’s driver app shows the route to the technician depending on which business unit owns the work; completion writes back to ServiceTitan for invoicing.

Pricing and time to live

eLogii runs alongside ServiceTitan; it doesn’t replace what you’re paying ServiceTitan today. The question is what eLogii adds on top, and what it costs to add it.

eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined ServiceTitan + eLogii rollouts complete in 3 to 5 weeks including the integration.

ServiceTitan does not publish pricing. Third-party review aggregators (FieldCamp, Research.com, OneCrew) report typical pricing in the $250 to $500 per technician per month range for the base platform, with Pro add-ons (Dispatch Pro, Marketing Pro, Voice Agent Pro, Contact Center Pro, Pricebook Pro, Fleet Pro, Scheduling Pro, Field Pro) charged on top. Third-party reviewers consistently report 6 to 12 month full rollouts. None of this changes when eLogii is added; eLogii is layered on top.

When eLogii on top of ServiceTitan starts to pay off

Adding eLogii alongside ServiceTitan

Three steps for operations whose routing problem has outgrown what ServiceTitan’s Dispatch Pro is built to handle, and who want to keep ServiceTitan for CSR, pricebook, payments and marketing while adding eLogii for advanced routing on top.

Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.

Deep dives on each documented Dispatch Pro limit

Each of these takes one of ServiceTitan’s documented routing limits, cites the source verbatim, and explains what it means in practice and how eLogii covers the gap.

Frequently asked questions

Is eLogii a ServiceTitan alternative or a complement?

Complement, in almost every case. ServiceTitan owns the trade business workflow: CSR call handling, dispatch board, pricebook, payments, marketing automation. eLogii adds routing depth on top once the operation grows past around 100 in the field, where Dispatch Pro hits its own documented limits. The integration runs over ServiceTitan’s V2 REST API and eLogii’s REST API with a full-parity sandbox – the technical pieces are already in place on both sides.

At what scale does adding eLogii on top of ServiceTitan make sense?

Roughly past 100 in the field. Under that, ServiceTitan plus Dispatch Pro typically covers the routing problem well: residential single-tech, single-day work with a three-day forward horizon. Above it, the share of work that doesn’t fit the single-tech/single-day model grows fast enough to show up on the dispatch board every week. ServiceTitan’s own FAQ states Dispatch Pro “will not assign multi-technician or multi-day jobs” – that’s the load-bearing line. eLogii layers on to handle what falls outside it.

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 projects can be booked manually through the project filter, but the optimizer itself stays single-technician, single-day. eLogii covers the rest via REST API.

What’s the difference between ServiceTitan’s CSR booking workflow and eLogii’s slot booking co-pilot?

They solve adjacent problems. ServiceTitan’s CSR booking workflow is the call-handling layer: caller-ID lookup to customer record, scripts and prompts, lead qualification, capacity warnings, marketing attribution, drop into the dispatch board. eLogii’s slot booking co-pilot is the route-aware availability calculation: given the current optimized plan, which slots can actually be offered to a customer without breaking optimized routes. In a combined deployment, ServiceTitan’s CSR fields the call and queries eLogii’s slot availability via REST API, then confirms a slot back to the customer that’s already optimization-aware. The CSR layer stays in ServiceTitan; the optimization-aware slot calculation runs in eLogii.

How does eLogii integrate with ServiceTitan?

Through both products’ REST APIs. ServiceTitan’s V2 API uses OAuth 2.0 Client Credentials with a developer portal at developer.servicetitan.io and an integration environment sandbox. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook events including live driver GPS. Typical pattern: eLogii reads jobs, customers and depots from ServiceTitan, runs the optimization, writes routes and ETAs back. Completion writes back to ServiceTitan for invoicing. The technician keeps using whichever field app they already use.

What is FieldRoutes and how does it relate?

FieldRoutes is a pest control and lawn care field service management product acquired by ServiceTitan in January 2022. It runs under the FieldRoutes brand at fieldroutes.com and ships its own routing engine designed for recurring pest control service windows. For pest control operations that need optimization depth beyond what FieldRoutes’ built-in routing reaches – multi-depot, multi-day, constraint-heavy planning – eLogii can layer on top via REST API on the same pattern described above for ServiceTitan’s core platform.

How does pricing compare?

ServiceTitan does not publish pricing; multiple third-party reviews put it at roughly $250 to $500 per technician per month for the base platform, with Pro add-ons (Dispatch Pro, Marketing Pro, Contact Center Pro, Voice Agent Pro, Fleet Pro, Pricebook Pro, Scheduling Pro, Field Pro) charged on top. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from $3,000 per month. eLogii runs alongside ServiceTitan; it doesn’t replace what you’re paying ServiceTitan today. Customers typically report 3 to 4× return on investment within 6 months on eLogii.

What are the most-cited issues with ServiceTitan?

ServiceTitan has a strong Gartner Peer Insights rating (4.8/5) and is widely praised for platform depth, dashboards and the dispatch board. The most consistently cited issues across G2, Capterra, Software Advice and BBB are: long implementation timelines (6 to 12 months for full rollout), high total cost when Pro add-ons stack on top of base per-technician pricing, slow support response, QuickBooks integration reliability and over-complicated inventory tracking. Dispatch Pro specifically gets criticised for over-optimization on its 10-minute reshuffle cycle, with jobs moving away from customer-confirmed arrival times.

How long does adding eLogii to a ServiceTitan stack take?

Typically 3 to 5 weeks from kickoff to a phased go-live, including the ServiceTitan integration. eLogii’s V2 ServiceTitan integration reads jobs, customers and depots over the REST API; routes, ETAs and completion data flow back. Most teams start with one business unit (often the commercial or multi-depot arm where Dispatch Pro’s limits matter most), validate against historical data, then expand. Heatleys evaluated 20 platforms and went live fast on eLogii, citing how quickly drivers could be onboarded.

Is eLogii enterprise-grade?

Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo Pest Management (400 technicians, Tyro Group), Bristow & Sutor (200+ enforcement agents, 200,000+ case visits routed annually), Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.