OnCallClerk Logo
Field service · via webhooks

AI receptionist for ServiceTitan shops

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.

I.What it does

Six things this integration handles for you

Capture every after-hours call

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.

Create customers and booking requests

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.

Route by business unit and job type

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.

Mid-call lookups

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.

Full call context attached

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.

Emergency escalation

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.

II.Setup

Four steps from signed webhook to booking request

01

Turn on webhooks

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.

02

Point them at ServiceTitan

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.

03

Map fields and job types

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.

04

Test end to end

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.

IV.FAQ

Common questions

Is this a native, one-click ServiceTitan integration?

+
No, and we will not pretend otherwise. OnCallClerk connects to ServiceTitan through webhooks and the ServiceTitan API. You point our signed call-event webhooks at your endpoint (directly, or via a tool like Make or Zapier) and map the fields to ServiceTitan objects. Our native, one-click integrations today are Google Calendar, Google Sheets, HubSpot, Slack, Outlook, and Calendly.

What can actually be written into ServiceTitan?

+
Anything the ServiceTitan API supports from your mapping — typically creating or matching a customer and location, opening a booking request or lead, and attaching the call transcript and summary as a note. The exact objects depend on how you wire the webhook payload.

Do I need a developer to set this up?

+
For a clean production setup, someone comfortable with the ServiceTitan API or a workflow tool should map the fields once. After that it runs on its own. If you would rather not build it, our team can help scope the webhook mapping.

Can the agent check ServiceTitan data during the call?

+
Yes, if you expose an endpoint. The agent can make a mid-call request to look up an existing customer or confirm a service area before it commits to anything with the caller.

Why not just have ServiceTitan answer the phone?

+
ServiceTitan manages dispatch, scheduling, and invoicing extremely well, but it is not a 24/7 receptionist. OnCallClerk covers the calls your office cannot — after hours, weekends, and overflow — and feeds the results back into ServiceTitan so nothing lives in two places.

Stop letting after-hours jobs walk

Sign up, wire the webhook into ServiceTitan, and turn every missed call into a booking request your dispatchers can act on in the morning.