Field service
On requestServiceTitan shops are larger, with call centres, dispatchers, and their own rules for what a lead is. A receptionist that writes into it has to match those rules, so this is scoped with the shop, not switched on.
On request. Not live. No ServiceTitan adapter exists yet. This page describes what we would scope with a shop, not something you can turn on.
The same shape as our other field-service connections: after a call ends, the caller, the address, and the job details land in ServiceTitan as a record your office can work. Which record is a scoping decision. Some offices want a booking for a CSR to convert. Others want a job.
ServiceTitan grants API access per tenant. Scoping starts with what your tenant allows, who owns the credentials, and which business unit and job type a phone lead belongs to.
Assign a technician or move a job on the dispatch board. Those stay with your dispatchers. A guess at your configuration is not something to ship.
Nothing is written for a call you answer. For a call the receptionist takes, a build would write after the call ends, as our other connections do.
The same write at any hour, so the overnight call is a record waiting for the morning dispatcher.
What scoping would cover. There is nothing to connect today.
Booking or job, business unit, job type, campaign.
Who registers the app and who holds the credentials.
Adapter work is scoped and quoted at setup. We test against a sandbox or a quiet period before live calls.
Not yet. There is no adapter. It is a custom build we scope with a shop that needs it.
Use Cal.com or Calendly for bookings and take the text to your on-call number. Your office keys the call into ServiceTitan.
It is quoted at setup, per shop. It is not a hidden charge after you are live.
