ServiceTitan runs your dispatch, scheduling, and invoicing — but it does not answer the phone after hours. OnCallClerk picks up every call, qualifies the caller, and pushes a clean customer and booking request into ServiceTitan through webhooks and the ServiceTitan API.
How this connects, honestly: This is a webhook and API integration, not a one-click native connector. OnCallClerk fires signed call events that you map into the ServiceTitan API — directly, or through a workflow tool. Our native, one-click integrations today are Google Calendar, Google Sheets, HubSpot, Slack, Outlook, and Calendly.
ServiceTitan runs your dispatch board, but it does not answer the phone at 9pm. OnCallClerk picks up, qualifies the caller, and hands you a structured record ready to push into ServiceTitan.
Using the ServiceTitan API, the call payload can create or match a customer and open a booking request or lead with the job type, address, and problem description filled in.
Map what the caller asked for to the right business unit and job type so the request lands in the correct queue instead of a generic inbox.
The agent can call your endpoint mid-conversation to check whether a caller is an existing customer or confirm a service area before promising anything.
Every pushed record carries the transcript, recording link, and an AI summary, so a CSR opening it in ServiceTitan sees exactly what the caller wanted.
For true emergencies — no heat, active leak — the agent can text or call your on-call tech immediately while still creating the ServiceTitan record for the paper trail.
In your dashboard, enable outbound webhooks for the events you care about — call.completed, lead.captured, booking.created — each a signed POST with the full structured call payload.
Route those webhooks into the ServiceTitan API through your own endpoint, a workflow tool like Make or Zapier, or a small middleware that maps fields to ServiceTitan objects.
Decide how captured data maps to ServiceTitan customers, locations, business units, and job types, and which calls should create a booking versus just a note.
Place a test call, watch the webhook fire, and confirm the customer and booking request appear in ServiceTitan with the right routing. Adjust the mapping and retry.
Full payloads and event types are in the REST API & webhook reference. Prefer a lightweight setup? Capture leads to Google Sheets first and sync into ServiceTitan on your schedule.
The shops that get the most from this are the ones where every missed call is a four-figure job walking to a competitor.
No-heat and no-cool calls captured overnight and pushed in as urgent booking requests.
Read moreActive-leak emergencies escalated to the on-call tech while the record lands in ServiceTitan.
Read moreService calls qualified and routed to the right business unit and job type.
Read moreOverflow when your CSRs are already on the line, so no caller hits hold music forever.
Read moreNights, weekends, and holidays covered without paying an answering service per minute.
Read moreAny ServiceTitan trade where same-day capture beats a callback tomorrow.
Read moreSign up, wire the webhook into ServiceTitan, and turn every missed call into a booking request your dispatchers can act on in the morning.