Is Your ServiceTitan Dispatch Automation Set Up Right in 2026?

Most ServiceTitan users have the platform running but are not getting the dispatch efficiency it was designed to deliver. The classic sign: a dispatcher is still manually calling or texting technicians to relay job details, customers are not receiving automated on-the-way notifications, and the routing board is organized by manual drag-and-drop rather than availability and proximity logic.

ServiceTitan has the automation capabilities to handle all of this. The gap is configuration, not capability — and the configuration decisions that matter most are not the ones in the getting-started guide.

US home services market: $657 billion in 2025 according to Houzz 2025 Home Services Industry Report, including both remodel and maintenance segments. A market at that scale means even a small improvement in technician utilization — one additional completed job per technician per week — has measurable revenue impact on a 10-tech operation.

This playbook covers the 8 configuration steps that separate a ServiceTitan instance that runs smooth automated dispatch from one where the dispatcher is still doing everything manually. It also covers what to connect above ServiceTitan when native automation hits its ceiling.

Key Takeaways

• ServiceTitan's native dispatch automation covers job alerts, technician notifications, customer on-the-way messages, and basic routing — but requires deliberate configuration to activate each layer.

• The 8 steps below progress from foundational (capacity configuration) to advanced (intelligent routing and escalation logic), and each step depends on the previous one being correct.

• The most common dispatch automation failures trace to three root causes: technician zones not configured, capacity not set by skill code, and customer notification templates left at defaults.

• An orchestration layer above ServiceTitan — connecting it to Twilio, Google Maps, and a scheduling tool — handles the cross-system dispatch scenarios ServiceTitan native automation does not cover.

TL;DR

ServiceTitan dispatch automation is the configuration of automatic job alerts, technician routing logic, customer notification workflows, and escalation rules within ServiceTitan's platform — so that dispatch decisions that currently require a dispatcher's manual intervention happen automatically based on technician availability, skill match, and location.

Who This Is For

This playbook is for service managers, operations directors, and owner-operators at home services businesses:

• HVAC, plumbing, electrical, or multi-trade shops using ServiceTitan as their primary field management platform

• 5–50 field technicians

• Annual revenue between $1M and $20M

Red flags: Skip this if your business runs fewer than 3 technicians or uses ServiceTitan Lite rather than the full platform — dispatch automation in the Lite tier is significantly limited. Also skip if you handle primarily residential new construction rather than service and replacement — the dispatch model is different, and scheduling is driven by project timelines rather than inbound service demand.

Step 1: Configure Technician Capacity and Skill Codes

Dispatch automation is only as good as the capacity data feeding it. If ServiceTitan does not know which technicians are available, which job types they are qualified for, and what their current workload is, routing logic will produce incorrect assignments.

Configure skill codes for each technician that match your job type categories: HVAC installation, HVAC maintenance, plumbing drain service, plumbing water heater, electrical panel, and so on. Skill codes are the primary filter that determines which technicians are eligible for each dispatched job.

Set capacity rules that define how many jobs a technician can run per day by job type. An installation technician may have capacity for 1 job per day; a maintenance technician may handle 4–6. Without capacity rules, ServiceTitan's automation will attempt to schedule a 6-hour installation for a technician who already has a full day of maintenance calls.

Define technician zones using ServiceTitan's zone mapping. Zones define which geographic areas each technician serves primarily. Zone configuration is the first filter in routing logic — before skill and availability are checked, the system identifies which technicians serve the customer's ZIP code.

Step 2: Configure Job Type Templates

Every job type in ServiceTitan should have a template that defines its default duration, required skills, required equipment, and estimated drive time buffer. Without templates, dispatch creates jobs with no duration estimate, which breaks routing logic entirely.

Duration accuracy matters. If a water heater replacement is templated at 2 hours but typically runs 3.5 hours, the scheduling board will double-book the technician's afternoon based on an incorrect assumption. Pull your last 3 months of job data, segment by job type, and set template durations at the 75th percentile of actual duration — not the average.

Required equipment flags prevent dispatching a technician without the parts or tools the job requires. If a job type routinely requires a specific diagnostic tool, add that equipment requirement to the template. ServiceTitan will flag technicians who do not have the required equipment in their inventory record.

Step 3: Activate Technician Job Alerts

ServiceTitan's technician mobile app can automatically push job details to a technician's phone when a job is dispatched to them. This should be active for every technician, but many installations leave it in manual notification mode — requiring the dispatcher to call or text the technician separately.

In ServiceTitan Admin → Dispatch → Notification Settings, configure:

• Dispatch notification: Push notification to the ServiceTitan mobile app when a job is assigned

• Customer info inclusion: Customer name, address, job type, and notes included in the notification

• Travel time estimate: Google Maps travel time from the technician's current location to the job site

Activating automatic job alerts eliminates the dispatcher's manual notification step for every dispatched job. For a dispatcher handling 25–40 daily dispatches, this is the single highest-value configuration change in the entire playbook.

According to ServiceTitan 2024 Pulse Report, technicians receiving automated job alerts via the mobile app report 22% lower "dispatch confusion" incidents — missed jobs, wrong address, incorrect job scope — compared to technicians receiving manual phone or text dispatch.

Step 4: Configure Customer On-the-Way Notifications

Customer no-contact is the second leading cause of missed service appointments in home services. A customer who does not know the technician is en route leaves for an errand, the technician arrives to an empty house, and the job is rescheduled — at a cost of $180–$300 in technician time and fuel.

ServiceTitan can automatically send a customer text message when a technician is dispatched and a second message when the technician is within a defined radius of the customer's address (typically 15–20 minutes away).

Configure the dispatch notification template in ServiceTitan Customer Notifications. Include the technician's name, a photo if available, an estimated arrival window, and a contact number. Personalized on-the-way messages with the technician's name increase customer satisfaction scores measurably.

Configure the arriving soon trigger based on either a fixed time before the job window (e.g., 30 minutes before the start of the 2-hour arrival window) or a radius trigger from the customer's address. The radius trigger is more accurate but requires GPS tracking enabled on the technician's device.

According to ANGI 2024 Annual Report, 74% of homeowners cite real-time technician arrival communication as a top-3 factor in service satisfaction ratings. Shops with automated on-the-way messages average 4.6/5.0 customer ratings versus 3.9/5.0 for shops relying on customer-initiated status inquiry.

Automated on-the-way texts lift service ratings from 3.9 to 4.6 out of 5.

Step 5: Set Up Routing Rules and Priority Logic

ServiceTitan's dispatch board supports routing rules that automatically suggest technician assignments based on zone, skill, availability, and priority. Without routing rules, the board shows all available technicians equally, and the dispatcher makes every assignment decision manually.

Configure zone-priority routing: For each job type, define whether the zone match or the skill match takes priority. For emergency HVAC calls in summer, skill takes priority over zone (you want a qualified tech, not the nearest tech). For routine maintenance, zone takes priority to minimize drive time.

Set priority modifiers for job types that should jump to the top of the routing queue: emergency calls, VIP accounts, and warranty callbacks. Priority jobs should sort above standard calls in the dispatch board automatically.

Configure capacity-respecting suggestions: ServiceTitan's AI-assisted dispatch suggestions factor in current technician workload when offering assignment recommendations. This is on by default in most configurations but requires the capacity rules from Step 1 to be accurate.

Step 6: Connect Twilio for Two-Way Customer Messaging

ServiceTitan's native customer notification capabilities cover outbound messages well but are limited for two-way conversational messaging. Customers who reply to a "your technician is on the way" text get no response unless a dispatcher actively monitors and replies.

Twilio integration adds two-way SMS capability that routes customer replies to the appropriate dispatcher queue with the job record attached. When a customer texts back "Can you call me when you're 10 minutes away?", the reply surfaces in the dispatcher's queue with the job context — no manual lookup required.

US Tech Automations connects ServiceTitan to Twilio at the orchestration layer, so inbound customer replies trigger a lookup against the open job record and route the message to the dispatching team's interface with full context. The same connection handles automated follow-up messages for job completion, review requests, and seasonal maintenance reminders — see for the Twilio messaging pattern applicable to home services platforms.

The platform's agentic dispatch workflows can be configured to route specific message types automatically — a customer texting "ETA?" while a job is in-progress gets an automated reply with the technician's current GPS location and estimated arrival, without dispatcher involvement.

Step 7: Build Escalation Logic for Missed Windows and No-Shows

Dispatch automation without escalation logic handles the easy cases perfectly and drops the hard ones. The hard cases: a technician runs late and will miss an appointment window, a technician does not check in on arrival, a job runs significantly over the estimated duration and impacts the afternoon schedule.

Configure late alerts that fire when a job start time passes without a technician check-in. The alert should go to the dispatcher with the job record and the technician's GPS location. A 15-minute threshold is standard — enough buffer for minor delays, early enough to allow proactive customer communication.

Configure duration overrun alerts when a job's actual time exceeds 120% of the estimated duration. When a water heater installation that was estimated at 2.5 hours hits the 3-hour mark without a completion check-in, the dispatcher receives an alert with the downstream jobs on that technician's board so they can proactively reschedule.

Configure no-start escalation for jobs that have not been started within 30 minutes of the appointment window opening. This catches technicians who missed the dispatch notification or had a vehicle issue without communicating it.

US Tech Automations handles the cross-system escalation that ServiceTitan cannot: when a late alert fires, the orchestration layer automatically sends the customer a revised ETA message via Twilio, creates a dispatcher task in ServiceTitan, and — if the delay exceeds a threshold — flags the job for potential same-day reschedule. The dispatcher receives a prepared message and a recommended action, not just an alert.

Step 8: Configure Post-Job Automation and Review Requests

The job closes in ServiceTitan. The technician marks complete, the invoice generates. What happens next should be automatic: customer receipt delivery, review request, next appointment scheduling for maintenance accounts, and quality callback for premium service tier customers.

Configure job complete triggers that fire on status change to "completed" in ServiceTitan:

• Customer receipt: Invoice summary emailed within 5 minutes of job close

• Review request: Text message asking for a Google review, sent 2 hours after job close (not immediately — customers should have time to settle before being asked)

• Maintenance reminder: For customers on an annual maintenance plan, schedule the next appointment automatically based on the plan interval

Configure quality callback scheduling for new customers and high-value jobs. A callback scheduled 48 hours after job close, assigned to the service manager or CSR, ensures first-impression jobs do not fall through the cracks.

See for the review collection workflow that connects the ServiceTitan job-complete event to a structured review request sequence.

Worked Example: A 12-Tech HVAC Shop During Summer Peak

Consider a 12-technician HVAC shop in a major metro market processing 45–60 service calls per day during July peak season. Without the 8-step configuration, 2 dispatchers spend 7 hours each day managing technician notifications, answering customer "where is my tech?" calls, and manually rescheduling downstream jobs when a late job pushes the afternoon schedule. With the configuration complete, when a job.dispatched event fires in ServiceTitan for a no-cool service call at 9:47 AM, the technician receives an instant app notification with customer address, job notes, and the job.type_id for HVAC maintenance, the customer receives a "Your tech is on the way, arriving 10:15–11:15 AM" text, and the routing board auto-confirms that the technician's 12:30 PM job is buffered by 45 minutes. When that same tech's no-cool call runs long at the 90-minute mark, the overrun alert fires automatically: the customer with the 12:30 PM appointment receives a revised window text, the dispatcher sees a pre-populated rescheduling option, and the technician's afternoon board updates with the new schedule — all without a dispatcher phone call.

Comparison: ServiceTitan vs. Twilio vs. Google Maps in the Dispatch Stack

ServiceTitan is the system of record for the dispatch workflow — no tool replaces it. Twilio adds the two-way messaging layer ServiceTitan native cannot handle. Google Maps provides real-time route optimization for arrival time estimates. The orchestration layer connects all three, handles escalation logic, and manages the exception cases that each platform's native automation drops.

When NOT to Use US Tech Automations

If your shop processes fewer than 20 dispatches per day and your dispatching function is handled by one person who is also your office manager, the native ServiceTitan configuration described in Steps 1–8 above is sufficient without adding an orchestration layer. Complete the 8 steps in ServiceTitan first — most shops achieve 60–70% of their available dispatch efficiency gain from the native configuration alone.

The orchestration layer adds value when: you run multiple service lines (HVAC + plumbing + electrical) with different routing rules and customer communication templates, your dispatcher volume exceeds what one person can manage during peak season, or you need two-way customer messaging integrated into the dispatch workflow rather than managed as a separate channel.

Benchmarks: Dispatch Efficiency by Configuration Level

According to the PHCC (Plumbing-Heating-Cooling Contractors Association) 2024 Business Performance Survey, top-quartile HVAC and plumbing shops complete an average of 6.8 jobs per technician per day versus 4.2 for bottom-quartile shops — a 62% throughput difference largely attributable to dispatch efficiency.

Top-quartile shops complete 6.8 jobs per tech per day vs. 4.2 for bottom-quartile.

According to BLS 2024 Occupational Employment Statistics, HVAC technicians earn a median of $57,300 annually — making technician idle time from missed dispatches or miscommunication a direct labor cost, not just a service quality issue.

Step-by-Step Configuration Timeline

Most shops ask how long each step takes in practice. The following benchmarks reflect a 12-technician HVAC shop with existing ServiceTitan data (technician records, job history, zone definitions already populated).

Full 8-step configuration completes in 3–5 days for a shop with clean existing data.

ROI by Automation Tier

The business case for each configuration tier is clearest when presented against specific KPIs. The table below reflects aggregated outcomes from home services shops with 8–20 technicians.

Steps 1–4 reduce dispatcher workload by 28–40 hours per month — the highest-density ROI tier.

Frequently Asked Questions

Does ServiceTitan dispatch automation work for on-call emergency jobs?

Yes, but emergency jobs require separate routing configuration. Emergency calls should route outside of zone restrictions to the nearest available technician with the required skill, bypassing the standard zone-priority logic. Configure a separate job type for emergency calls with skill-first routing and an overriding priority level.

How do we handle jobs that require two technicians?

ServiceTitan supports crew-based scheduling where a job can be assigned to a primary technician and one or more secondary technicians. Configure the crew requirement in the job type template; routing logic will identify crew availability rather than individual technician availability.

Can the escalation alerts reach us on mobile if we are not at a desk?

Yes. ServiceTitan's mobile app supports push notifications for dispatcher alerts. For SMS-based escalation, a Twilio integration can route alerts to any phone number — including the service manager's personal cell for after-hours escalations.

How long does the full 8-step configuration take to complete?

A focused configuration effort with experienced ServiceTitan support takes 3–5 business days for an established shop with existing technician, zone, and job type data. New ServiceTitan users should plan 2–3 weeks to configure the platform and gather the historical data needed to set accurate job duration templates.

Does the automated routing handle GPS-based technician tracking?

Yes. ServiceTitan's dispatch board displays real-time technician GPS locations from the mobile app. The route optimization features in ServiceTitan use GPS position to calculate arrival time estimates and can dynamically re-sort the technician's job queue based on current location.

Can we use these automations for recurring maintenance agreement customers?

Absolutely — recurring maintenance is one of the highest-ROI automation use cases in ServiceTitan. Configure maintenance plan jobs to schedule automatically based on plan renewal date and equipment service interval, assign to the zone-appropriate technician, and trigger the customer notification sequence on dispatch. See for the companion membership renewal automation.

What is the biggest mistake shops make when setting up dispatch automation?

Configuring routing rules before setting accurate job duration templates. Routing logic that assumes a job takes 1.5 hours when it consistently runs 3 hours will produce a perfectly optimized schedule that falls apart by 11 AM every day. Duration accuracy is the foundation everything else depends on.

Getting Started

The fastest path to dispatch automation value is starting with Step 1 (capacity configuration) and Step 3 (technician job alerts) — these two changes alone typically eliminate 40–50% of a dispatcher's daily manual notification workload and reduce scheduling conflicts by setting accurate capacity limits.

Work through Steps 4 and 5 in the same week (customer on-the-way notifications and routing rules) and you will have the core dispatch automation running within 5–7 days of starting.

Steps 6–8 (Twilio two-way messaging, escalation logic, post-job automation) are the layer that turns a competent dispatch operation into a largely self-managing one — and where the orchestration layer above ServiceTitan adds value that native configuration cannot.

US Tech Automations has pre-built workflow templates for the Twilio and Google Maps integrations described in Steps 6 and 8, configured specifically for ServiceTitan environments. The setup takes 2–3 weeks and delivers a tested escalation and messaging workflow without requiring custom development.

See the home services automation pricing options and review which plan covers the cross-platform dispatch orchestration your shop needs.

See also: for the emergency dispatch routing workflow, and for the CRM update automation that runs parallel to the dispatch layer.