Consolidate HVAC Dispatch: ServiceTitan + Twilio 2026

Key Takeaways

• Connecting ServiceTitan, Google Maps, and Twilio into a single dispatch loop eliminates the 3–5 manual handoff steps that delay most HVAC same-day calls.

• Automated zip-code routing assigns tickets to the nearest available technician in seconds, without dispatcher intervention.

• SMS notifications via Twilio keep customers informed at every job stage, reducing inbound "where is my tech?" calls by a significant margin.

• Most HVAC companies that automate dispatch recover the integration cost within 60–90 days through fuel savings and increased daily job completions.

• The integration requires ServiceTitan at the Business or Enterprise tier, a Twilio account with SMS provisioned, and a middleware layer to bridge the two platforms.

Dispatch is the heartbeat of an HVAC operation. Every delay between a customer call and a technician assignment means a longer wait time, a colder or hotter home, and a higher chance that the customer dials a competitor. Yet most HVAC dispatch workflows still rely on a dispatcher staring at a whiteboard, calling technicians manually, and typing confirmation texts one at a time.

That gap between what's possible and what most shops actually run is the opportunity this guide addresses. By wiring ServiceTitan's dispatch board to Google Maps routing data and Twilio's SMS API, you can build a fully automated dispatch loop that assigns, routes, and notifies without a single manual step after the job is booked.

HVAC tech assignments completed in under 2 minutes are achievable once this stack is connected — compared to the 8–15 minutes typical of manual dispatcher workflows, according to the ServiceTitan 2024 Pulse Report.

Average dispatcher time per manual job assignment: 11 minutes according to the ServiceTitan 2024 Pulse Report — automated routing cuts this to under 90 seconds for same-day calls.

Who This Integration Is For

This guide is written for HVAC business owners and operations managers who:

• Run 4 or more trucks and struggle to keep the dispatch board current in real time

• Are on ServiceTitan Business or Enterprise tier (the dispatch API is not available on Starter)

• Already use or are willing to adopt Twilio for SMS

• Process at least 20 jobs per day where routing inefficiency compounds into real revenue loss

Red flags: Skip this integration if your team has fewer than 3 full-time technicians, if you're still running paper job tickets, or if your annual revenue is under $400K — the middleware setup overhead won't pay back quickly at that scale. A simpler solution like Housecall Pro's built-in notifications may serve you better.

The Three-Platform Stack and How It Fits Together

Before wiring anything, understand what each tool does in the dispatch chain:

ServiceTitan is the system of record. It holds your customer accounts, job history, technician schedules, dispatch board, and invoice data. When a customer calls and a CSR books a job, ServiceTitan creates a work order.

Google Maps Platform (specifically the Routes API and Distance Matrix API) provides real-time routing data. Given a technician's current GPS coordinates and a job address, it returns drive time and optimal route — data ServiceTitan's native dispatch board alone does not compute dynamically.

Twilio handles outbound SMS. Once a technician is assigned to a job, Twilio fires a confirmation text to the customer with the tech's name, estimated arrival window, and a tracking link. It also sends technician-facing texts when a new job is pushed to their queue.

The middleware layer — typically a low-code platform like Make (formerly Integromat), Zapier, or a custom Node.js webhook listener — reads events from ServiceTitan's API, queries Google Maps for routing data, selects the optimal technician, updates the dispatch board in ServiceTitan, and triggers Twilio to send the SMS notifications.

Step-by-Step: Building the Automated Dispatch Loop

1. Enable the ServiceTitan API and Create a Credentials Set

Navigate to ServiceTitan's Integrations portal and enable API access for your tenant. Create a client ID and client secret under the "Connected Apps" section. Store these in a secure environment variable manager — never hard-code them in your middleware script.

2. Provision a Twilio Phone Number and SMS-Capable Account

Log into Twilio Console, purchase or verify a local phone number, and confirm your account is SMS-enabled for the states where you operate. Note your Account SID, Auth Token, and the "From" number — all three are required by the middleware.

3. Enable Google Maps Distance Matrix API

In Google Cloud Console, create a project, enable the Distance Matrix API and Routes API, and generate an API key. Set usage quotas to avoid overruns — for a 20-truck operation, a daily limit of 5,000 elements is typically sufficient.

4. Set Up Your Middleware Trigger on New Job Creation

In your middleware platform, create a webhook or polling trigger that fires whenever a new job is created in ServiceTitan with status "Scheduled." The trigger payload should include: job ID, customer address, job type, requested arrival window, and any technician preference the CSR noted.

5. Query Active Technician Locations from ServiceTitan

Using ServiceTitan's Technician Booking API, pull the list of technicians currently clocked in and their last known GPS coordinates (populated automatically when techs use the ServiceTitan mobile app). Filter to only technicians whose current job is within 30 minutes of completion or who are currently unassigned.

6. Run Distance Matrix Queries Against Each Candidate Tech

Pass each candidate technician's coordinates and the new job's address to the Google Maps Distance Matrix API. Request both driving distance and estimated travel time in current traffic. Store the results in a ranked list sorted by ascending travel time.

7. Apply Zip-Code Zone and Skill-Set Filters

Before auto-assigning, run two filters: (a) zone filter — if your company uses geographic zones to control overtime eligibility or subcontractor coverage, exclude techs outside the job's zone; (b) skill filter — check the job type against each tech's ServiceTitan skill tags (e.g., "commercial refrigeration," "mini-split certified") and exclude under-qualified candidates.

8. Write the Assignment Back to ServiceTitan Dispatch Board

Call ServiceTitan's Job Update API to assign the selected technician to the job. Update the job's "Assigned Tech" field and set the estimated arrival time using the Google Maps travel time plus a 10-minute buffer.

9. Fire the Customer SMS via Twilio

Once the assignment is confirmed, trigger a Twilio message to the customer's phone number on file in ServiceTitan. Include: tech's first name, estimated arrival window, and a branded tracking URL if you have one configured. Response rate to confirmation texts exceeds 80%, which dramatically reduces inbound status calls to your office.

10. Send the Tech a Job Notification SMS

Simultaneously, send the assigned technician a Twilio text with: customer name, address, job type, any access notes from the CRM record, and a Google Maps deep link to the job site. Techs on the road can tap the link directly — no need to copy-paste an address.

11. Monitor for Re-Dispatch Triggers and Handle Cancellations

Set a webhook on the ServiceTitan job status field to detect cancellations or tech-initiated "cannot arrive" flags. When triggered, the middleware should unassign the tech, re-run the candidate selection, re-assign, and fire a new SMS to the customer with a revised arrival estimate.

12. Log Every Dispatch Event for Operations Review

Write each dispatch event — timestamp, job ID, tech assigned, travel time estimate, actual arrival time (pulled from tech clock-in) — to a Google Sheet or a database table. This log becomes the foundation for weekly dispatch performance reviews and ongoing route optimization.

Platform Comparison: ServiceTitan vs. Verizon Connect vs. Twilio (Standalone)

Where Verizon Connect wins: If your primary pain is vehicle GPS tracking and route efficiency across a large fleet (15+ trucks), Verizon Connect's native telematics outperforms ServiceTitan's mobile-app GPS by a meaningful margin. Some HVAC companies run both — Verizon Connect for fleet visibility and ServiceTitan for job management — bridging them via API.

When NOT to use US Tech Automations: If your dispatch challenge is purely about GPS fleet tracking with no CRM or job-management component, a standalone fleet telematics tool like Verizon Connect may solve 80% of your problem at a fraction of the integration cost. The platform adds the most value when you need to orchestrate across ServiceTitan, routing data, and customer communication in one automated loop — not when the problem is a single-platform gap.

Benchmarks: What to Expect After Go-Live

Home services annual revenue: $600B+ according to the Houzz 2025 Home Services Industry Report — meaning competitive dispatch speed is increasingly a differentiator, not just an efficiency gain.

HVAC fuel cost per wasted drive mile: $0.67 according to the IRS 2025 standard mileage rate — routing inefficiency at 5+ trucks compounds quickly into thousands per month in avoidable fuel spend.

Common Mistakes to Avoid

Skipping the skill-set filter. Auto-assigning the nearest tech regardless of certifications leads to techs showing up to jobs they can't complete, burning drive time with nothing to bill.

Using ServiceTitan's polling API instead of webhooks. Polling on a 5-minute interval introduces 0–5 minutes of latency on every job assignment. Webhooks push events in real time — use them.

Sending SMS without opt-in verification. Twilio requires TCPA-compliant opt-in for marketing messages. Job confirmation texts qualify as transactional under most interpretations, but consult your legal counsel and configure Twilio's opt-out handling regardless. According to the CTIA 2024 Messaging Report, transactional SMS open rates exceed 90% within 3 minutes of delivery — making Twilio notifications the fastest customer-communication channel in field service.

Not accounting for technician travel time buffers. Google Maps travel estimates assume a vehicle capable of highway speeds. Add at least 10 minutes to any estimate to account for parking, tool retrieval, and customer door-to-door time.

Failing to test cancellation and re-dispatch paths. The happy path is easy to build. The cancellation re-dispatch is where most integrations break — test it explicitly before go-live.

Integration Cost and ROI Framework

Building this integration has two cost categories: one-time setup and ongoing platform fees.

One-time setup costs vary by approach:

• Low-code middleware (Make/Zapier): 8–20 hours of configuration, typically $1,500–$4,000 if outsourced

• Custom middleware (Node.js/Python): 40–80 hours of developer time, $6,000–$15,000 if outsourced

• Google Maps API activation: free to set up, usage-based billing (Distance Matrix requests are roughly $0.005 each)

• Twilio SMS: roughly $0.0079 per outbound message in the US

Ongoing costs include Twilio per-message fees (typically $30–$150/month for a 20-truck operation) and middleware platform subscriptions ($20–$100/month for Make or Zapier at typical HVAC volumes).

ROI calculation: If adding 1 additional completed job per technician per day at an average ticket value of $350 on a 5-truck operation, the incremental monthly revenue is approximately $350 × 5 techs × 20 working days = $35,000/month in addressable upside. Even capturing 10–15% of that through tighter dispatch translates to $3,500–$5,250/month — well above the integration cost.

HVAC lead-to-job conversion rates are a critical benchmark for measuring dispatch effectiveness, according to the ServiceTitan 2024 Pulse Report, which tracks conversion by response time — with faster assignment correlating directly to higher booking capture.

Where US Tech Automations Fits In This Stack

US Tech Automations is not ServiceTitan, Twilio, or Google Maps — it is the orchestration layer that connects them. For HVAC operations that want the dispatch automation described in this guide without building custom middleware from scratch, US Tech Automations configures the integration workflow, maps your ServiceTitan fields to the Google Maps queries and Twilio triggers, and monitors the automation for failures.

The practical advantage: instead of managing API credentials, webhook endpoints, and error-handling logic internally, your team gets a configured, monitored workflow that a non-technical dispatcher can operate. When a Twilio error occurs or a ServiceTitan API rate limit is hit, the system alerts your team and retries automatically.

See the full automation catalog and pricing at ustechautomations.com.

Glossary

Dispatch board: The visual schedule in ServiceTitan (or similar FSM software) showing which technicians are assigned to which jobs across the current day.

Distance Matrix API: A Google Maps Platform API that returns travel time and distance between one or more origins and destinations, factoring in real-time traffic.

Webhook: An HTTP callback that fires in real time when a specified event occurs in a source system — used here to trigger the dispatch middleware when a new ServiceTitan job is created.

TCPA: Telephone Consumer Protection Act — the US federal law governing commercial text messages. Transactional messages (job confirmations) carry fewer restrictions than marketing messages.

Middleware: Software that sits between two platforms and translates data between them. Examples: Make, Zapier, or a custom API bridge.

Technician GPS coordinates: In ServiceTitan, populated in real time when the technician is actively using the ServiceTitan mobile app and has location permissions enabled.

FAQs

Does ServiceTitan have a native auto-dispatch feature?

ServiceTitan's dispatch board supports manual drag-and-drop assignment and some smart scheduling suggestions, but it does not natively auto-assign tickets to the nearest available technician using real-time GPS data. Achieving that behavior requires the API integration described in this guide.

Is Twilio compliant for sending job confirmation texts to customers?

Yes, job confirmation and status update texts are generally classified as transactional messages under TCPA, which carry lighter regulatory requirements than marketing texts. You still need to maintain opt-out handling and should consult counsel for your specific use case, but Twilio provides built-in opt-out management through its Messaging Service feature.

What happens if the assigned technician cancels mid-route?

If you build the re-dispatch webhook described in Step 11, the system detects the cancellation event from ServiceTitan, unassigns the tech, re-queries available candidates, assigns the next best option, and sends the customer an updated SMS — all without dispatcher intervention. Build and test this path before go-live.

How does the integration handle multiple jobs booking simultaneously?

The middleware should process job assignment events in a queue with a short lock on technician availability (2–3 seconds) to prevent double-assignment. Make and Zapier handle this with sequential processing by default; custom middleware needs explicit concurrency handling.

How long does this integration take to build?

Using a low-code middleware platform like Make, an experienced integration builder can configure the core dispatch loop in 2–3 days. Add 1–2 days for testing, error handling, and the cancellation re-dispatch path. Custom middleware development takes 2–4 weeks depending on team experience.

Can smaller HVAC companies with fewer than 5 trucks benefit from this?

Smaller shops can benefit from the customer SMS notifications with less middleware complexity — simply trigger Twilio on job booking without the auto-routing layer. The full routing automation typically pays back fastest for operations completing 20+ jobs per day.

What's the biggest risk of building this integration?

The most common failure point is relying on ServiceTitan's polling API instead of webhooks, which introduces dispatch latency. The second most common is not testing the cancellation and re-dispatch paths, which can leave customers waiting without updates. According to the ANGI 2024 Annual Report, homeowners cite timely communication as a top factor in service provider ratings — making the notification reliability part of the integration just as important as the routing accuracy.

Related Resources

• How to set up ServiceTitan dispatch step by step

• Automate HVAC call booking with AI in 7 steps

• How field service teams reduce drive time between jobs

• Automate same-day callout dispatch for electrical

• Home services two-way customer text updates with Jobber and Twilio

Ready to connect ServiceTitan, Google Maps, and Twilio without building the middleware yourself? See the pricing and workflow options at US Tech Automations.