AI receptionist integration: ServiceTitan, Housecall Pro, Jobber
What an AI receptionist can and can't write into ServiceTitan, Housecall Pro and Jobber, the plan each needs, and why mine stops at the inbox, not the board.
An AI receptionist integrates with ServiceTitan, Housecall Pro or Jobber at one of three levels: a text to your phone, a lead written into the software's inbox, or a job booked onto the board. The first works with anything. All three platforms accept the second through their APIs, on the right plan. Only their own built-in agents do the third, and that's the level I don't build. Here's what each needs, costs, and breaks.
I'm a plumber who builds phone and follow-up systems for trade businesses. My first live build is a plumbing company going live in October 2026, and it hands off by text. So this is written from the vendors' own help pages, checked in September 2026, and from the builds I'd do, not from a year of production data. Where a claim is the vendor's, I say so.
Integration means three different things, and vendors blur them
When a salesperson says "we integrate with ServiceTitan", ask which of these three they mean. I call it the three-level test.
Level one: the text. The receptionist answers, asks what the job is, where it is and how urgent, and texts you. Nothing touches your software. Someone types it in later. This works with every platform ever made, which is why every vendor can claim it.
Level two: the inbox. The receptionist writes the call into your software as a lead, a request or a booking. It lands in a queue a person looks at. Nobody retypes anything, and nothing is promised to the customer until a human accepts it. This needs API access, which some plans include and others charge for.
Level three: the board. The receptionist checks capacity, picks a slot and books the job onto a technician's day. That needs live availability, job types, skills and drive times, so the only agents that do it well are the ones the platform vendors built themselves.
Mine stops at level two. The short version of why: a caller can tell a machine where the water is coming from. They can't tell it which van to send.
What each platform lets an outside receptionist write
Here's what the three vendors' own help pages say. Table first, then the parts that matter.
| Platform | API access | What an outside receptionist can write | Where it lands |
|---|---|---|---|
| ServiceTitan | Admin permissions plus an app in the developer portal; no fee on the help page | Customer, location, booking, lead | Bookings tab, and the unassigned column of the dispatch board |
| Housecall Pro | Max plan only ($329 a month, or $299 billed annually) | Customer, lead | API Leads channel in Job inbox |
| Jobber | An app built in the Developer Center; marketplace apps on every plan | Client, request, quote, job | Requests |
ServiceTitan. Access runs through the developer portal, and an administrator has to switch on two permissions, "Generate API Application Key" and "Manage API Application Access", before anyone can create an app. You test against an integration environment, a clone of your production data, before the phone line touches the real thing. The help page mentions no fee; ask your account manager rather than assume. A call filed through the API becomes a booking against a booking provider, ServiceTitan's label for where it came from. ServiceTitan's bookings page says a booking "populates on the Bookings tab of the Call Booking screen", also shows in the unassigned column of the job tray on the dispatch board, and waits there until someone accepts it into a job or dismisses it. The same page says a web booking's job type "is set to unknown by default and should be reclassified after following up with the customer." That sentence is the whole argument for level two. ServiceTitan doesn't trust a form to pick the job type either.
Housecall Pro. The API is available only on the Max plan, only an admin can generate a key, and Housecall Pro says it doesn't provide support for API builds, so the work is on you or your developer. The useful piece is API Leads: a call sent through the API shows in its own API Leads channel in Job inbox, and you convert it to a job or an estimate like any other message. That's a clean level two. On Basic or Essentials it doesn't exist, and Max is $329 a month, or $299 billed annually, with eight users.
Jobber. The API is GraphQL behind OAuth, built through Jobber's Developer Center, and an app built for one business skips the public app store review. What a receptionist writes is a request, the same object your website form creates, so it shows up where your office already looks. Jobber's pricing page lists marketplace apps on every plan and an expert-led API tour on Plus only. I couldn't find a line tying custom API access to a plan, so ask.
Why my receptionist stops at the inbox
Three reasons, and none of them is that the code is hard.
First, the caller doesn't know the job type. "My water heater's making a noise" could be a flush, a valve or a replacement, and the difference is a thirty-minute slot or half a day. ServiceTitan files web bookings as unknown for this reason, and I'd file a phone call the same way.
Second, the board is where you say no. Not worth the drive, not our kind of work, that customer again. A booking in the inbox costs the dispatcher ten seconds to accept or dismiss. A wrong job on a technician's day costs an afternoon to unpick, plus a customer who was promised Tuesday.
Third, accountability. With a booking in the inbox there's a person between the call and the promise. With a job on the board, the promise is made by software at nine at night, and you explain it in the morning. The plumbers post has the rest of my scope argument. Catch, qualify, hand off.
Level three exists and it works for some shops. It's just not something a third party should bolt on from outside, which is where the vendors have the advantage.
The vendors' own agents book to the board, and sometimes that's the right buy
Each platform now sells its own AI receptionist, and each does level three because it sits inside the data. If you're already on the platform, price it before you price me.
ServiceTitan AI Virtual Agent. A Pro product. ServiceTitan's page says it will "book straight to the dispatch board with a real-time, unified knowledge of technician availability", knows whether the caller is an existing customer or a member, and transfers to a person when it needs to. It quotes a 70% booking rate overall and 90% capacity adjusted, ServiceTitan's own figures across its own customers, and says setup takes 20 minutes. No price on the page.
Housecall Pro CSR AI. Listed on the pricing page as an add-on outside every plan, including Max, with no figure. The product page says it answers "across calls, chats, and texts (in Alpha)", schedules jobs from your schedule and service preferences, and when a caller wants a person it takes their details and sends the call to a number you choose. It also claims pros using it earn over twice the revenue on average, a comparison of Housecall Pro's own customers, not a controlled test.
Jobber Receptionist. Launched on 18 August 2025, and the launch release said it had already handled more than 200,000 conversations for participating businesses. Jobber's help article says it answers calls and texts around the clock, books through your Online Booking form, submits requests through your request form, escalates on trigger keywords, and "if it encounters something it doesn't know, it can direct the client to contact you directly." It's included with unlimited use on Plus. On Core, Connect and Grow it's $29 a month for 30 conversations, then $0.79 a conversation.
Here's my honest read. If you're on Jobber Plus, you already own a receptionist. Turn it on this week, forward the phone after four rings, and watch it handle your real calls before you spend a dollar with anyone, including me. If you're on ServiceTitan with a CSR team and a full board, the Virtual Agent inside your data will book better than anything built from outside. Where I fit is the shop that wants the call caught and qualified in its own words, wants a person to make the promise, or runs software with no agent of its own.
Zapier and Make: what the connectors actually do
Most "integrates with everything" claims mean a Zap. Here's what the connectors can write, from the app pages.
ServiceTitan's Zapier app is the fullest: Create Booking, Create Lead, Create Customer and Create Job are all there. But ServiceTitan's own help page says Zapier "is not officially supported by ServiceTitan and is made available on an 'as is' basis and without warranty at users' own will and risk." You need the Works or Legacy package, an administrator to fill in a registration form, and about two business days before it's switched on. Fine for a marketing form. For the phone line that pays the mortgage, "as is" is a sentence I'd read twice.
Housecall Pro's Zapier app has two triggers, New Scheduled Job and New Completed Job, and one write action: Create Customer. It can't create a lead or a job. A Zap gets the caller's name into your customer list and leaves the job for someone to type. That's level one with extra steps. API Leads is the real level two, and it needs Max either way.
Jobber's Zapier app can Create Request, Create Client, Find or Create Client, Create Quote and Create Job. Find or Create matters more than it sounds. The second call from Mrs Jones with a different spelling is how duplicate records are born, and a connector that looks before it creates saves the office a merge a week.
If you're in the UK on Commusoft, Tradify or BigChange, I haven't built against those and won't pretend I have. Ask the vendor the three-level question and treat "we integrate with everything" as a no until they show you where the call lands in your software.
The maths: what level two saves, and what it costs to unlock
Say your receptionist catches 25 calls a week and someone in the office retypes each one. Call it three minutes a call for the name, address, phone and notes. That's 75 minutes a week, about 65 hours a year, and at $25 an hour (about £19) it's roughly $1,600 a year of typing that a level two build removes. It also removes the typo in the phone number, which is the expensive one.
Now the other side. If you're on Housecall Pro Essentials, level two means moving to Max, and the difference is $140 a month on monthly billing, $1,680 a year, before anyone builds anything. The API costs about what it saves, and the honest answer is level one: a good text, a fast callback, and the office types it in. If you're already on Max, or on ServiceTitan where the help page lists no separate API fee, the maths flips and level two is the obvious build.
The right level isn't a technical choice. It's your plan, your call volume and who's typing. Put your numbers through the calculator for the missed-call side, and do the sum above for the typing side.
What AI can't do here, and what to do this week
It can't tell the job type from the caller's description, and neither can your best CSR from the first sentence. It can't see the drive time between the last job and this one unless it lives inside the platform. It can't tell whether this is the same Mrs Jones or a new one at the same address. And it can't decide whether the job is worth taking. Those four are why the inbox exists.
This week, in order:
- Find the queue where a web form lands. Bookings tab in ServiceTitan, Job inbox in Housecall Pro, Requests in Jobber. That's where a level two receptionist writes to. If nobody checks it daily, fix that before you buy anything.
- Check your plan. Housecall Pro Basic or Essentials means level one until you're on Max. Jobber Plus means you already own a receptionist.
- Ask any vendor, including me, the three-level question, and ask for a screenshot of where the call lands in your software.
- Count seven days of calls the office retypes from voicemail, texts or a notepad. Multiply by three minutes. That's the typing you'd save.
- Write the hand-off rule: who accepts bookings, how fast, and what happens to the ones nobody has touched by five o'clock.
If you want a second opinion on which level fits your plan and call count, book a growth call. Thirty minutes, free, and if the answer is "turn on the receptionist you already pay for", that's what I'll say. What I'd build for a plumbing business is on the plumbers page, and what a build costs is in the cost post.
Questions people ask
Does an AI receptionist integrate with ServiceTitan?
Yes, at two levels. Any receptionist can text you the call summary, and one built against ServiceTitan's API can file the call as a booking, which lands on the Bookings tab of the Call Booking screen and in the unassigned column of the dispatch board for a person to accept or dismiss. Booking straight onto a technician's day is what ServiceTitan's own AI Virtual Agent does, and it's the level I don't build.
Can an AI receptionist create jobs in Housecall Pro?
Through the API it can send a lead into the API Leads channel of your Job inbox, where you convert it to a job or an estimate. That needs the Max plan, and only an admin can generate the key. Zapier's Housecall Pro app can only create a customer, not a lead or a job, so a Zap alone leaves you retyping. Housecall Pro's own CSR AI add-on is the route that books directly.
Does Jobber have its own AI receptionist?
Yes. Jobber launched Receptionist in August 2025. It answers calls and texts, submits requests through your request form and can book through your Online Booking form. It's included with unlimited use on the Plus plan and is a $29 a month add-on with 30 conversations on the other plans, then $0.79 a conversation. If you're on Plus, try it before you pay anyone else.
Can I connect an AI receptionist to ServiceTitan with Zapier?
You can, with caveats. ServiceTitan's Zapier app has Create Booking, Create Lead and Create Customer actions, but ServiceTitan says the Zapier integration is not officially supported and is used at your own risk. You need the Works or Legacy package, an administrator to register, and about two business days for approval. For a phone line I'd rather have a direct API build with an owner who answers when it breaks.
Why don't you let the receptionist book straight onto the dispatch board?
Because the caller can't tell it the job type, the crew or the drive time, and the board is where those decisions live. ServiceTitan files a web booking with the job type set to unknown for the same reason. A booking in the inbox costs your dispatcher ten seconds to accept. A wrong job on a technician's day costs an afternoon. When the vendor's own agent has the live capacity data, that's a different product, and I say so.
Sources
- 1.ServiceTitan Help: Get started with API dev portal V2 · Updated 27 May 2026; administrators enable 'Generate API Application Key' and 'Manage API Application Access'; integration environment is a clone of production; endpoints listed as Jobs, Projects, Invoices, Payroll, Pricebook and more; no fee mentioned
- 2.ServiceTitan Help: Manage bookings · Updated 11 July 2026; a booking populates on the Bookings tab of the Call Booking screen and in the Unassigned column of the Job Tray on the Dispatch Board; accept to book into a job or dismiss; web booking job type set to unknown by default
- 3.ServiceTitan Help: ServiceTitan Zapier integration · Zapier 'is not officially supported by ServiceTitan and is made available on an as is basis'; needs Client ID and Secret Key, a registration form, an administrator, and the Works or Legacy package; about 2 business days
- 4.ServiceTitan: AI Virtual Agent · 'Book straight to the dispatch board with a real-time, unified knowledge of technician availability'; knows existing customers and members; transfers to a person; 70% booking rate overall, 90% capacity adjusted; 20 minutes to implement; a Pro product; no price on the page
- 5.Zapier: ServiceTitan integrations · Triggers include New Booking (for a booking provider), New Call, New Lead; write actions include Create Booking, Create Customer, Create Job, Create Lead
- 6.Prismatic: ServiceTitan connector · CRM actions include Create Booking by Provider, Create Customer, Create Location, Create Job, Create Appointment
- 7.Housecall Pro Help Center: API overview · 8 July 2026; 'API is available only to Pros on a MAX plan'; only Admin users can generate API keys; no dedicated support for API implementations; not every feature is available to build an integration
- 8.Housecall Pro Help Center: API Leads in Job Inbox · 13 July 2026; 'All leads from the API show in the API Leads channel in Job inbox'; convert to a job or estimate; Max plan only
- 9.Housecall Pro: Pricing · Basic $79 a month ($59 annual), Essentials $189 ($149), Max $329 ($299) with 8 users; Open API access on Max only; CSR AI listed as a separate add-on with no figure
- 10.Housecall Pro: CSR AI · 'answers across calls, chats, and texts (in Alpha)'; schedules jobs from your schedule and service preferences; when a caller wants a person it gathers details and sends the call to a number you choose; vendor claim that pros with CSR AI earn over 2x more revenue on average
- 11.Zapier: Housecall Pro integrations · Triggers: New Completed Job, New Scheduled Job; the only write action is Create Customer
- 12.Jobber Help Center: Receptionist, powered by Jobber AI · Updated 9 July 2026; included on the Plus plan with unlimited usage; add-on $29 a month with 30 conversations, $0.79 per additional conversation; books through the Online Booking form, submits requests via the request form, escalates on trigger keywords; forward calls after a number of rings
- 13.Jobber press release: Jobber launches AI-powered Receptionist · Toronto, 18 August 2025; 'Receptionist has handled more than 200,000 conversations on behalf of participating businesses'; included with Plus, add-on for Grow
- 14.Jobber: Pricing · Core, Connect, Grow, Plus; Receptionist add-on on Core, Connect and Grow, included on Plus; 'Connect 100+ tools through the app marketplace' on every plan; 'API Tour with API Access' listed on Plus
- 15.Jobber Help Center: Developer Center · Updated 11 September 2024; GraphQL API behind OAuth; apps built for a single client don't need public app store review; 2FA required to submit an app
- 16.Zapier: Jobber integrations · Write actions: Create Client, Find or Create Client, Create Request, Create Quote, Create Job, Add Note to Request; trigger New Request Created

Written by Ivar André Knutsen
I build and run AI systems, internal tools and workflow automation. You work directly with me from the first conversation through implementation and support. About Ivar
Want this looked at in your business?
We look at where you want the business to go, what is slowing you down and where AI could make a useful difference. You get a clear recommendation: a tool to try, a focused automation, a broader system or a closer look at the process. Any build is scoped and quoted before work starts. Free, no obligation.
Single automations are quoted on the call: a setup fee plus a monthly retainer to run them. Full systems start at $4,500, fixed scope, fixed price.
Book a free 30-minute call