How it works
How AI booking works with Jobber and Housecall Pro
The short answer
Receva reads availability from Jobber or Housecall Pro, filters it by each technician's working hours, offers the caller real open slots, and writes the confirmed job back during the call. The slot is re-checked at the moment of booking, so two callers cannot take the same one. Both are available from the Pro plan.
Key takeaways
- The booking is written during the call, not queued for someone to confirm afterwards.
- Availability is filtered by each technician's working hours, not just your opening hours.
- The slot is re-checked at the moment of booking, which is what stops a double-booking rather than a promise not to.
- If the field service system is unreachable, the call is still answered and booking falls back to the calendar and then to the internal calendar.
- ServiceTitan is built and being readied for release. It is not switchable today, so do not buy on it.
1. What happens, in order
A homeowner calls. Between "hello" and a job in your field service system, this is the sequence:
- Answer and qualify. Receva runs the four H.O.M.E. gates: is the home in your service area, are we speaking to the owner or someone who can decide, what is the actual service need, is this an emergency.
- Resolve the address. The caller's address is geocoded and checked against your coverage — postal codes and drawn polygons, with branch overlap rules if you run more than one location. This is a hard gate. Outside it, no slot is ever offered.
- Match the job to your catalog. The need has to correspond to a service you actually offer, from the catalog loaded for your trade.
- Fetch availability. Open slots come from the connected system, filtered by the working hours of the technicians who can do that work.
- Offer real slots. The caller is offered times that exist, not a request form.
- Re-check and write. The chosen slot is verified as still free, then the job is created in Jobber or Housecall Pro with the customer, address, service and notes from the call.
- Confirm on the call. The caller hangs up with an appointment, not a promise that someone will ring back.
Step 6 is the one that separates this from a message-taking product. It is also the one most likely to be glossed over in a demo, which is why it is the first question on the buyer's checklist.
2. Where availability actually comes from
Three layers, in order of precedence. This matters because it determines what happens when one of them is unavailable.
- Your field service system — Jobber or Housecall Pro, when connected. This is the authority when it is reachable, because it is where your team already works.
- Your calendar — Google Calendar or Outlook, available on every plan. Used when no field service system is connected, and as the fallback when one is connected but not answering.
- The internal calendar — always present. Receva works standalone, so nothing has to be connected for booking to function at all.
Whatever the source, availability is then filtered by each technician's working hours. A technician who does not work Fridays does not get offered on Fridays, which is a distinction any system working only from business opening hours cannot make.
3. What gets written back
The job that appears in your system carries what was captured on the call: the customer, the service address, the service matched from your catalog, the requested time, the urgency, and notes from the conversation.
On the customer record, Receva looks for an existing customer before creating a new one, matching on the number the call came from. A repeat caller attaches to the record already there rather than starting a second one — duplicate customers are one of the fastest ways to make a field service system worse, and creating them would be a poor trade for a slightly simpler integration.
Alongside the job in your system, the call itself is kept in your Receva dashboard with its recording, transcript, qualification result and the reasoning behind each decision. Those stay in Receva rather than being pushed into your field service system, which keeps your job records readable.
4. How double-bookings are prevented
A booking flow that reads availability at the start of a call and writes at the end has a window in the middle. On a four-minute call in a busy week, that window is long enough for someone else to take the slot — through your own office, another call, or a technician moving a job on their phone.
Receva re-checks the slot at the moment of booking rather than trusting the read from earlier in the call. If it has gone, the caller is offered the next available time instead of the conflict being written. The caller hears a small hesitation. Your schedule stays correct.
This is the mechanism, and mechanisms are what you should ask any vendor for. "It will not double-book" is a claim. "It re-checks at write time" is something you can verify.
5. What happens when something breaks
OAuth tokens expire, providers have incidents, and someone eventually revokes an authorisation by accident. The design question is whether your phone stops working when that happens. It should not.
- The integration is unreachable. The call is answered as normal and availability falls back to the calendar, then to the internal calendar. Bookings continue.
- Anything booked during the outage syncs when the connection returns.
- You get an alert. Integration health is monitored, and reconnecting is a one-click reauthorisation from Settings.
- Availability cannot be established at all. The call is not answered with a guess. Receva does not offer a slot it cannot verify, and the caller is captured as a lead for follow-up instead.
That last one is worth stating plainly, because the alternative — booking optimistically and reconciling later — produces exactly the double-booking this is all meant to prevent.
This section describes designed behaviour, not a measured uptime figure. We do not publish an availability percentage for these integrations because we have not established one with a methodology we would stand behind, and the providers' own uptime is not ours to quote.
6. Connecting it
Connecting Jobber or Housecall Pro is a one-click authorisation from Settings, and it can be revoked the same way. Jobber and Housecall Pro sync is available on the Pro plan and above. Google Calendar and Outlook are on every plan.
Two things worth knowing before you connect:
- Map your technicians. Each Receva technician links to the corresponding person in your field service system, which is what makes per-technician availability work.
- Connecting later is fine. If you start standalone on the internal calendar and add a field service system afterwards, you do not redo your setup. When you connect, Receva can bring your open future appointments across so both systems agree from day one.
On what is not supported: ServiceTitan is built and being readied for release, but it is not something you can turn on today — do not buy on the strength of it. There is no HubSpot integration and none planned. Both of those are in writing here for the same reason they are in the FAQ: a self-serve product with no salesperson has to catch its own bad fits.
7. Frequently asked questions
Can AI book appointments directly in Jobber?
Yes. Receva reads availability from Jobber, filters it by each technician's working hours, offers the caller real open slots and writes the confirmed appointment back to Jobber during the call. Jobber sync is available on the Pro plan and above; calendar sync with Google and Outlook is on every plan.
Does it work with Housecall Pro too?
Yes, from the Pro plan, using the same read-availability and write-booking flow as Jobber. The connection is authorised from Settings and can be revoked the same way. Where a provider's API behaves differently, the behaviour you see is the same: real slots offered, confirmed job written back.
What happens if my field service system is unreachable when a call comes in?
The call is still answered. Availability falls back to the connected calendar, and then to the internal calendar, so a caller is never turned away because a token expired. You get an alert, and anything booked while the integration was down syncs when it reconnects.
Will it create duplicate customers in my system?
It looks for an existing customer before creating a new one, matching on the phone number the call came from. A repeat caller attaches to the record already there rather than starting a second one. If nothing matches, a new customer is created with the details captured on the call.
Do I need a field service system to use Receva?
No. Receva works standalone with an internal calendar behind the booking, so leads, calls, appointments and follow-ups all live in your dashboard. If you add Jobber or Housecall Pro later, connecting it does not require redoing your setup.
Do you integrate with ServiceTitan?
Not yet. ServiceTitan support is built and being readied for release, but it is not something you can turn on today, so do not buy on the strength of it. Today the supported systems are Google Calendar and Outlook on every plan, and Jobber and Housecall Pro from Pro. There is no HubSpot integration.
Connect it and watch a job appear
Authorise Jobber or Housecall Pro from Settings, place a test call, and watch the appointment land in the system your team already uses. 30 days or 60 call minutes free, whichever runs out first.
Start free trial