ServiceTitan Recurring Service Routes

What recurring routes actually look like

Recurring service routes are a defined cohort of customer accounts visited on a defined cadence by a defined pool of technicians. The optimizer’s job is to balance the cohort across technicians over a planning horizon (a week, a month, a quarter), respecting customer preferences for the same technician, customer-confirmed windows, geography and technician capacity. Common shapes:

• Quarterly preventive maintenance contracts. HVAC PMs, fire system inspections, generator maintenance, water filtration servicing. The cohort is the customer base on contract; the cadence is quarterly; the optimization balances visits across the technician pool to land within contract windows.
• Monthly commercial service agreements. Commercial HVAC service, refrigeration servicing, kitchen extract cleaning. Customer-facing SLA is “we visit you once a month”; the planner’s job is to make that happen efficiently every month.
• Weekly compliance visits. Life safety, legionella testing, weekly pest reapplications. Strict cadence, often regulatory.
• Annual inspection programs. Electrical inspections, gas safety certificates, asbestos surveys. Each customer visited once a year, but the year-long cohort needs to be balanced so technicians aren’t overloaded in any one month.
• Seasonal route programs. Boiler servicing pre-winter, AC startup pre-summer, gutter cleaning in autumn. Bounded windows with a fixed customer cohort.

What recurring routes are not: ad-hoc service-and-replacement calls, which is what ServiceTitan’s core dispatch is built for.

The signal from the FieldRoutes acquisition

The clearest evidence that ServiceTitan’s core platform doesn’t optimize recurring routes is the FieldRoutes acquisition itself. In January 2022, ServiceTitan acquired FieldRoutes (formerly PestRoutes), describing it in their press release as “a leading cloud-based and mobile SaaS provider in the pest control and lawn care industry” covering “advanced route optimization for technicians”. FieldRoutes runs its own routing engine designed specifically for the recurring service windows that dominate pest control and lawn care.

ServiceTitan didn’t fold FieldRoutes into the core dispatch product. It runs as a separate brand at fieldroutes.com, with its own product, pricing and customer base. The acquisition added pest and lawn coverage to ServiceTitan’s portfolio, but the core ServiceTitan dispatch engine still doesn’t treat recurring patterns as a first-class object outside the FieldRoutes brand.

What ServiceTitan’s core platform does for recurring work

ServiceTitan core supports recurring work at the booking layer. Service agreements model contractual recurring service relationships. The planned-maintenance module schedules recurring appointments out into the future. Dispatchers can see and manage the recurring queue on the dispatch board. What it doesn’t do is balance the recurring cohort as an optimization unit. Each individual occurrence lands on the dispatch board as a standalone single-day appointment, and Dispatch Pro optimizes that day’s appointments per technician without seeing the recurring pattern.

The cost of this gap shows up in a few specific ways. Recurring visits get bunched on a single technician when the cohort would be better balanced across the team. The same customer gets different technicians across visits when the SLA prefers continuity. Drive time across the recurring program is higher than necessary because each occurrence is optimized in isolation. Compliance windows get missed when the planner doesn’t have a single view of the full recurring cohort across months.

How eLogii handles recurring service routes

eLogii models recurring service patterns as first-class objects through task and route template groups. The template defines the cadence (weekly, monthly, quarterly, bespoke), the cohort of customer accounts, the preferred technician pool, the geography and the SLA windows. The optimizer balances the recurring cohort across technicians over a planning horizon.

• Task and route template groups. Task templates hold the recurring cadence, customer cohort and constraints. Route templates hold the preferred technician structure. Both are first-class objects in the data model.
• Same-technician preference. Operator-visible rules let planners preserve customer-technician relationships across recurring visits where the SLA prefers continuity.
• Multi-month planning. A single optimization run can target a quarter or a year, balancing the recurring cohort across that horizon. Annual programs don’t need to be re-planned month by month.
• Customer-confirmed windows protected. Recurring visits where the customer has confirmed a specific window stay anchored; optimization works around them.
• Cadence drift handled. If a customer reschedules a recurring visit, the next occurrence shifts accordingly without breaking the program-level cadence.
• REST callable. The full recurring-pattern optimization runs through eLogii’s REST API, so the program can be re-planned programmatically when the cohort changes.

How the integration sits with ServiceTitan

ServiceTitan continues to hold service agreements, customer relationships and invoicing for the recurring program. eLogii holds the recurring-route optimization model and writes individual occurrences back as scheduled appointments.

1. Read. Service agreements, recurring appointment patterns, customer records, technicians and skills sync from ServiceTitan’s V2 REST API. The recurring cadence and the customer cohort come from ServiceTitan’s service agreements; the optimization model is built in eLogii.
2. Optimize. eLogii runs the recurring-pattern optimization across the planning horizon, balancing the cohort across technicians, honoring same-tech preferences and customer-confirmed windows.
3. Write back. Individual occurrences are written back to ServiceTitan as scheduled appointments against the right technician on the right date. ServiceTitan holds the service agreement; the routing decisions sit in eLogii.
4. Technician experience unchanged. Each technician opens the field app they already use, sees the recurring visit on their schedule. Completion writes back to ServiceTitan for invoicing.

Most teams complete the integration in 3 to 5 weeks. Common first wave: the largest recurring service program – commercial PMs, fire safety contracts, weekly compliance – whichever the dispatcher spends the most time juggling today.

Frequently asked questions

Does ServiceTitan optimize recurring service routes?

Not in the core platform. ServiceTitan can book recurring appointments through service agreements and the planned-maintenance module, but the routing optimizer doesn’t model the recurring pattern as a first-class object. Each occurrence is optimized as a separate single-day appointment. The signal is that ServiceTitan acquired FieldRoutes in January 2022 specifically to handle pest control and lawn care recurring routes, where this gap was load-bearing.

Why did ServiceTitan buy FieldRoutes?

In ServiceTitan’s own acquisition press release (January 2022), they describe FieldRoutes as covering “advanced route optimization for technicians” in pest control and lawn care. FieldRoutes’ routing engine is designed for recurring service windows. ServiceTitan’s core dispatch product wasn’t built for that workload, so they acquired the specialist. FieldRoutes now runs as a separate ServiceTitan brand at fieldroutes.com for pest and lawn customers.

What kinds of recurring service programs need this?

Quarterly preventive maintenance contracts (HVAC, fire systems, generators); monthly commercial service agreements; weekly compliance visits (life safety, pest reapplications, water testing); annual inspection programs (asbestos, electrical, gas safety); seasonal route programs (boiler servicing, AC startup). Each one is a defined recurring cadence with a cohort of customer accounts that need to be balanced across technicians over a planning horizon.

How does eLogii handle recurring routes on top of ServiceTitan?

Through ServiceTitan’s V2 REST API. eLogii models recurring service patterns via task and route template groups: weekly, monthly, quarterly or bespoke cadences are first-class objects. The optimizer balances recurring work across technicians over a planning horizon (single day, a date range, or a full month), respecting same-technician preferences, customer-confirmed windows and route templates. Routes are written back to ServiceTitan as appointments against the right technicians on the right dates.

Should I just use FieldRoutes if I run pest control?

For pest control and lawn care specifically, FieldRoutes is ServiceTitan’s purpose-built product and is the natural choice. For pest operations whose routing problem outgrows FieldRoutes’ built-in optimizer (multi-depot, multi-day, constraint-heavy planning), eLogii can layer on top of FieldRoutes via REST API as the routing depth layer. For recurring service programs outside pest and lawn (HVAC PMs, fire safety, electrical compliance, commercial service agreements), eLogii works directly on top of ServiceTitan’s core platform.