ServiceTitan

ServiceTitan is field service management software built for HVAC, plumbing, electrical, and other home service trades, scheduling, dispatch, technician tracking, invoicing, and customer communication in one platform. ProPay sits in front of ServiceTitan and decides what actually needs to reach it, a work order only gets created after triage has already ruled out a no-truck-roll resolution.

What ProPay does with ServiceTitan

ProPay engages the homeowner over SMS to collect model and serial numbers, photos, and symptom detail, then recommends repair, replacement, or call avoidance, before ServiceTitan is involved at all. Where a truck roll is warranted, ProPay passes ServiceTitan an enriched job: a predicted job code and the parts the technician is likely to need.

Before ServiceTitan ever sees a work order, ProPay has already engaged the homeowner over SMS, collecting model and serial numbers, photos, and symptom detail, with 80 to 83 percent of homeowners responding. That triage is what decides whether a job reaches ServiceTitan at all: 7.9 percent of submitted claims are resolved without a truck roll.

As the job moves through ServiceTitan, job records, technician assignments, and invoices, ProPay reads status back to drive automated homeowner and contractor updates over SMS, and validates the resulting invoice against the authorization record before payment releases.

How the ServiceTitan connection works

ServiceTitan’s API is well documented for job and invoice data, which is what ProPay reads and writes against.

Where ServiceTitan doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment. Triage, authorization, and payment can each go live against ServiceTitan independently of one another.

What stays in ServiceTitan

Scheduling, technician dispatch logic, and the contractor’s own invoicing and customer relationship tools stay in ServiceTitan.

What changes is how much of a dispatcher’s day is spent on jobs that never needed a technician. ProPay resolves those before ServiceTitan sees them, so the jobs that do reach ServiceTitan are the ones that actually warranted a truck roll.

Data handling and security

The connection to ServiceTitan runs on a company-specific ProPay instance, one client’s job data and customer records are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.

Every triage recommendation carries a confidence level and the inputs behind it, and is logged. Recommendations outside your configured thresholds route to a person before a job ever reaches ServiceTitan.

Deploying the integration

A dedicated Forward Deployed Engineer builds and maintains the ServiceTitan connection alongside your team, mapping job codes and dispatch fields to how ServiceTitan is configured for your operation.

Frequently asked questions about ProPay and ServiceTitan

Does ProPay replace ServiceTitan?

No. ServiceTitan keeps handling scheduling and dispatch execution; ProPay decides upstream what should reach it and enriches the job before it does.

How does ProPay connect to ServiceTitan?

ServiceTitan’s API is well documented for job and invoice data, which is what ProPay reads and writes against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

Does ProPay reduce truck rolls sent to ServiceTitan?

Yes. Triage resolves 7.9 percent of submitted claims without dispatch, so fewer unnecessary jobs reach ServiceTitan in the first place.