Why put VICIdial next to ServiceTitan?
Home-services companies put VICIdial next to ServiceTitan because ServiceTitan runs the jobs, while outbound campaigns and busy-season overflow need a dialer that keeps a room of CSRs talking.
ServiceTitan is the system of record for many HVAC, plumbing, electrical and roofing companies: customers, service addresses, jobs, technicians and invoices. VICIdial, the open-source predictive dialer built on Asterisk, covers volume calling. Typical campaigns are unsold estimates, memberships about to expire, seasonal tune-ups and past customers who have gone quiet, plus inbound overflow after hours. VICIfast is managed VICIdial hosting and has built ServiceTitan integrations before. The trade-specific setup is on VICIdial for home services, and the broader patterns on VICIdial CRM integration.
How do ServiceTitan's records line up with a VICIdial lead?
A VICIdial lead is one phone number with a name and address, while ServiceTitan spreads the same household across several records:
- Customer - the person or business who pays, with contact details such as phone numbers and email.
- Location - a service address. One customer can have several, and work is booked against a location rather than the customer.
- Job - the work itself, with a job type, a business unit, a marketing campaign and one or more appointments.
- Booking - a request your CSRs or dispatchers review before it becomes a job.
- Membership and estimate - the records behind most outbound lists: memberships close to renewal and estimates nobody accepted.
That split matters at both ends. A list built from estimates has to bring the right location's address into VICIdial, so calling hours follow the right time zone, and a booked call has to land on the right location when it goes back.
Should a booked call create a ServiceTitan job or a booking?
A booking is the safer first step for most companies, because a person in dispatch confirms capacity before a technician is committed.
Creating jobs directly is possible, but the integration then has to choose the job type, business unit, campaign and an arrival window the board can actually meet, and get each one right on every call. That is more to build and more to test, so it is quoted higher. A sensible path is to start with bookings, then move simple, high-volume work such as tune-ups to direct jobs once the data has earned your trust.
What can VICIdial do before any ServiceTitan code?
VICIdial can run a ServiceTitan campaign today from an exported list, with no integration at all.
Export the customers or estimates you want to call from a ServiceTitan report, load the file with the lead loader, and let CSRs book in ServiceTitan by hand. If the export includes the ServiceTitan customer ID, VICIdial's campaign web form can open that customer's page as each call connects, for CSRs already signed in to ServiceTitan in the same browser. The Dispo Call URL can tell another system about each outcome, and the non-agent API accepts leads from scripts. That covers a first season. It stops covering it when CSRs retype bookings, numbers from different locations clash, or a do-not-call request made on the phone never reaches ServiceTitan.
What goes into a ServiceTitan build, and what sets the fee?
A ServiceTitan build is fixed-fee, and the fee follows how much of the booking decision the integration takes over.
API access to ServiceTitan has to be approved for your account, so it is worth requesting before the build is scheduled. After that, the fee is shaped by:
- Bookings only, or full jobs with job types, business units and campaign attribution.
- How many business units and trades the dispositions have to cover.
- Which lists come from ServiceTitan automatically: memberships, estimates or past customers.
- Matching inbound callers by phone number across customers and locations.
On the published ranges, sending booked calls to ServiceTitan as bookings is the simple-webhook kind of job at $1,500-$3,000. Pulling lists from ServiceTitan and sending outcomes back is two-way sync at $5,000-$12,000. If you want call data beside job revenue in your own data warehouse, the event stream and BI pipeline is listed at $10,000-$30,000. Most builds take 1-3 weeks and complex ones 4-6, each tested against a test setup on your side, and a 30-day warranty covers our code after go-live. The terms are on custom integrations.
Where VICIfast is not the right fit
If your CSRs only answer inbound calls inside ServiceTitan's own phone setup and you run no outbound campaigns, VICIdial adds a second system for little gain. We work remotely and never on site. VICIfast is not affiliated with or endorsed by ServiceTitan; the integration is built on ServiceTitan's API for your account.
Where to start
Plan it before your busy season, not in the middle of it. Bring the campaign you want to run first and how bookings should land to a discovery call. Seasonal floors can resize the server up for summer and back down after. To try the dialer side now, start a free trial. Sales-led teams on Salesforce should read the VICIdial Salesforce integration page.