What does the agent read and write in Jobber?
| When | Direction | What moves | How |
|---|---|---|---|
| Caller asks for a time | Reads from Jobber | Open times for the date the caller wants. | Custom function 1. Your endpoint queries the Jobber API and returns the open times as JSON. |
| Caller picks a time | Writes to Jobber | Name, phone, service address, a short problem description and the chosen time. | Custom function 2. Your endpoint creates the booking request in Jobber. |
| Call ends | Optional write | Call summary, full transcript, outcome and recording link. | Post-call webhook to an HTTPS endpoint you choose. |
| Always | Stays in Leadlock | The recording and the full transcript of every call. | Call logs in the Leadlock app. |
The fields are the ones you define in each function's JSON schema, so they match how the business takes a job. The agent tells the caller the request is in and the office will confirm it.
How do you set it up?
-
Get Jobber API access
Jobber's API is GraphQL and apps sign in with OAuth 2.0. Create the app for the one business in Jobber's developer center.
-
Stand up an endpoint
A small service you control. It holds the Jobber tokens and exposes two routes: check open times, and create the booking request.
-
Create two custom functions
In Leadlock, create each function with its name, description, parameter schema and your endpoint URL, then attach both to the agent.
-
Add the prompt rules
Always check open times before offering one. After booking, say the request is in and the office will confirm.
-
Test, then go live
The function test sends a real request to your endpoint, so a booking test creates a real request in Jobber. Clear it, then point the phone number at the agent.
How long does it take? The Leadlock side is minutes: a self-serve agent is live in about 5 minutes, and creating and attaching the two functions is a handful of API calls. The endpoint that talks to Jobber is the real work and depends on how the business schedules. We scope it on a call. The same pattern, written out with the real schemas, is in the ServiceTitan booking recipe.
When is Jobber's own AI Receptionist enough?
Jobber sells its own AI Receptionist, which books into Jobber with no integration work. If one business needs inbound calls answered and booked into Jobber and nothing else, start there.
Leadlock fits when you need more than that: outbound and speed-to-lead callbacks, a choice of OpenAI Realtime, Gemini Live or Grok per agent, a sub-account for each location or brand, or one agent that also works in GoHighLevel.