Does the AI Actually Book the Job in Jobber or Housecall Pro, or Just Take a Message?
Cactus writes a real job into Jobber and Housecall Pro during the call. Not a message, not an email you re-key at 7:30 Monday morning: a job record with the customer attached, the service address on it, a job type selected, and a time slot on your calendar. Jobber and Housecall Pro are the two native integrations today. If you run something else, the honest answer is that you are buying a relay or a message, not a written job, and you should know that before you sign.
Vendors use the word "integrates" for all of it, so the word on its own tells you nothing.
What is the difference between a booked job, a relayed lead, and a message?
Three different products get sold under one word. They do not produce the same Monday morning.
Native job creation. The agent holds a direct connection into your CRM. It reads your calendar, finds or creates the customer, and writes a job. You open the app and the work is already on the board.
Relay through Zapier or a webhook. The agent captures the call, then pushes the data into a Zap you built and you maintain. Something gets created, usually a lead, a request, or a contact, and often not on the calendar. If a field name changes or the monthly task limit is reached, the Zap stops running, and the alert goes to whoever built it rather than to the caller waiting on you.
Message only. You get a text or an email with a call summary. A human types it in.
Ask every vendor, us included, which of those three you are buying, on your specific CRM, and get the answer in writing.
What does each vendor's own site say about writing a job into Jobber or Housecall Pro?
Every cell below is what the vendor publishes on its own site, with the page linked. Where a vendor does not document a path, the cell says so rather than guessing.
| Vendor | Jobber | Housecall Pro | Source read August 4, 2026 |
|---|---|---|---|
| Cactus | Native. The job is created during the call. | Native. The job is created during the call. | Cactus product documentation |
| Smith.ai | Books through your Jobber Online Booking link. Smith.ai's setup doc says the booking will "create, schedule, and assign a job into your calendar automatically." | Connects with your Housecall Pro API key, creates or updates the client record, and books service calls through your Housecall Pro online scheduling link. | Jobber setup doc, Housecall Pro page |
| Rosie | Zapier. Rosie's own post says to "connect Rosie to popular home services CRMs like Housecall Pro, Jobber, and Service Titan using our Zapier integration." | Zapier, same sentence. | Rosie home services post |
| Goodcall | Goodcall's Jobber page says it "can access real-time information from Jobber via API" and "can handle appointment bookings and scheduling." The page does not state that a job record is written into Jobber. | Goodcall's Housecall Pro page says it "can integrate with Housecall Pro via API" and that customers can book appointments. The page does not state that a job record is written into Housecall Pro. | Goodcall Jobber page, Goodcall Housecall Pro page |
| Avoca | Avoca's Jobber page says its AI CSR "answers calls 24/7, books jobs directly into Jobber, handles objections, and routes emergencies." | Avoca's Housecall Pro page carries the same sentence with Housecall Pro in place of Jobber. | Avoca Jobber page, Avoca Housecall Pro page |
| Jobber AI Receptionist | Runs inside Jobber. Jobber's page says it is "ready from day one using your Jobber data, including your company profile, request forms, and booking settings." | Not applicable. The product lives inside Jobber. | Jobber AI Receptionist page |
| Housecall Pro CSR AI | Not applicable. The product lives inside Housecall Pro. | Runs inside Housecall Pro. The page says it will "book jobs instantly as calls and chats come in." | Housecall Pro CSR AI page |
Integration details read from each vendor's own product and documentation pages on August 4, 2026. Vendors change these pages without notice, so check the live page before you decide anything on it.
The point of the table is not the scorecard. It is that "integrates" covers at least four different mechanisms in seven rows: a native write, a booking link handed to a receptionist, an API read, and a Zap. Those produce four different results at 9:40 PM on a Thursday. Ask which one you are buying.
What does Cactus write into the job, step by step?
Here is the sequence on a booking call, in order:
- Availability lookup. The agent reads the calendar in your CRM before it offers a time, so it offers slots you can actually staff. It does not promise a window and reconcile it later.
- Customer match or create. It searches your existing customers by phone number first. On a match, the job attaches to that customer's history instead of spawning a duplicate. With no match, it creates the customer with name, phone, and email if the caller gives one.
- Job type selection. It maps what the caller described to a job type you defined during setup. "No hot water and there is water around the tank" becomes your water heater diagnostic, not a blank service call your dispatcher has to interpret.
- Service address and access notes. It captures the address, repeats it back, and writes the operational details into the job: gate code, dog in the yard, unit number, park in the alley, tenant will let you in, call 20 minutes out.
- Confirmation text to the caller. The caller gets a text with your company name, the date, and the arrival window while still on the phone. That is how you find out on the spot that a digit was misheard, instead of at the door.
Confirm all five on your own account during setup. How your shop has job types, arrival windows, and calendars configured changes what any agent can write.
Which fields do not get written, and who still has to touch them?
This is the part that tends to get left out, so here it is plainly. A booking agent does not write:
- Price, estimate lines, or parts. No line items, no material costs. Your tech or your office builds the estimate.
- Deposits or a card on file. Payment stays a human step.
- Tech assignment by skill. It fills the slot. If you dispatch by who is certified on that equipment, a human still makes that call.
- Membership, warranty, or equipment history verification. It can note what the caller claims. It does not audit it.
- Photos, permits, or documents. Anything requiring an upload is yours.
- Custom fields specific to your shop. Job costing tags, internal codes, and anything unusual get written only if they were mapped during setup.
- Multi-day, crew, or commercial jobs. Those should be transferred to a human, not booked.
What does it cost you when the AI only takes a message?
Run it with your own numbers. Two inputs, both yours to replace:
| Input | Placeholder used here | Why it matters |
|---|---|---|
| Records you re-key per month | 40 | After-hours and overflow calls that arrive as a message |
| Desk time per record | 3 minutes | Open the CRM, search the customer, create the record, type the address and notes, pick a slot |
Three minutes is the average handle time used across this site, applied here as the placeholder for keying one record. Swap in what it actually takes your office.
40 records x 3 minutes = 120 minutes, about 2 hours a month of re-typing.
That is the small number, and it is not the reason to care. The real number is the gap. A message taken at 9:40 PM Thursday and keyed at 7:30 AM Friday sat for roughly 10 hours. Over a weekend it is closer to three days. The homeowner did not wait. They called the next company while your message sat in a text thread. You did not lose three minutes, you lost the job, and it never shows up in any report because the call was answered. That is why the metric that matters is cost per booked job, not calls answered. The volume behind that gap is covered in after-hours calls in home service.
Cactus reports that a plumbing and HVAC company in Utah booked about $150,000 in confirmed revenue in four months, and that about 58 percent of those captured leads came in after hours. Cactus reports that a roofing company in North Carolina collected about $299,000 in ten weeks. Both are results Cactus reports for individual customers, not audited figures and not an average across customers. The 58 percent figure describes that one Utah company's captured leads and nothing broader. Ask to speak to a reference before you weigh any of it.
Should you use Housecall Pro's CSR AI or Jobber's built-in receptionist instead?
Sometimes, yes. If every call you take is residential, for trades already configured in that one system, you have exactly one system of record, you do not need Spanish, and you do not want another vendor in the stack, the built-in add-on is a reasonable answer. Use it. We would rather tell you that than sell you a second tool you do not need.
Here is what each publishes about price:
| Built-in option | What the vendor publishes about price | Page read August 4, 2026 |
|---|---|---|
| Jobber AI Receptionist | "Available as an add-on to any plan, and is included at no additional cost with the Plus plan." No dollar figure is published on the page below. | getjobber.com AI Receptionist page |
| Housecall Pro CSR AI | Sold separately from the Housecall Pro platform. No dollar figure is published on the page below. | housecallpro.com CSR AI page |
Competitor prices read from each vendor's public pricing page on August 4, 2026.
Two things to check before you commit.
The handoff. Housecall Pro's CSR AI page says the product "will gather the caller's information and send the call to a number of your choice." What the person answering that number sees or hears when the call lands is not documented on the vendor site as of August 4, 2026. That matters more than the booking flow. On a $400 drain call, a caller repeating the address to a second person is an irritation. On a no-heat call at 11 PM with an already unhappy homeowner, it is where you lose them. So demo the transfer, not the booking, and ask what the human receives in the first three seconds. Ask the same of us. This matters most on the calls that cannot wait, which is a different problem from booking and is covered in how AI answering triages emergency calls.
The coverage boundary. A built-in receptionist covers the phone line attached to that platform. If you run two brands, take commercial work, or field leads from sources that do not live in that CRM, it covers part of your phone, not all of it. Same for spam and robocalls, which should be screened before they ever create a record, a point we get into in answering service billing and spam calls.
If you are earlier than this and still deciding whether an AI should be on your phone at all, start with what an AI receptionist does for a contractor.
FAQ
Does Cactus book directly into Jobber? Yes. Jobber and Housecall Pro are the two native integrations today. On the call, the agent checks your availability, matches or creates the customer, and writes the job with the service address, job type, and access notes.
Does Cactus integrate natively with ServiceTitan or FieldPulse? Not natively today. Jobber and Housecall Pro are the native ones. If you run ServiceTitan or FieldPulse, ask us what the current path is rather than assuming a logo on a page means a job gets written.
Will it create a duplicate customer if someone calls from a different number? It can. Matching runs on phone number first, so a call from a spouse's cell on an existing account can create a second customer record that you merge later. Ask about the matching rule during setup.
What happens when there is no slot available? A correctly configured agent does not invent one. It offers the next real opening, and on the call types you flag as emergencies it transfers to your on-call person instead of booking. Ask to see both behaviors in the demo.
Do I still have to check the jobs it books? For the first week or two, yes, and you should want to. Once you have watched a dozen bookings land with the right customer, address, and job type, you stop checking. Anyone who tells you to trust it blind on day one has not run a dispatch board.
The next step
Book a demo at go.oncactus.com/book-a-demo and bring a real call from last week, including the messy one. Watch the job get written into your own Jobber or Housecall Pro, and make us demo the transfer to a human, not just the booking.
Cactus answers every call 24/7 in English and Spanish, qualifies the caller, and writes the job into Jobber or Housecall Pro. Setup takes 48 to 72 hours, no contract, $999 per month.