Why my AI receptionist doesn't book HVAC appointments

On a hot day the board is supposed to say no

The third decision is whether to take the slot at all. This is where HVAC differs from every other trade I write about.

You hold capacity back on purpose. ServiceTitan's own worked example does it twice. It takes two hours off base capacity "to reserve one technician for emergencies", then two more "since it is really hot". The same page says office staff can adjust capacity "to deliberately overbook or reserve capacity", and that on-call shifts are emergency-only and don't count towards available hours. That's a dispatcher looking at the forecast and deciding Thursday is not a normal day.

Now put a receptionist on the phone at nine the night before. It sees open slots. It doesn't see why they're open. If your maintenance agreement promises members priority, those held hours belong to the member who rings at seven tomorrow with no cooling. An AI that fills them first come, first served has spent a promise you already sold.

Even the vendor with the most data keeps a person in the chair. In auto mode, Dispatch Pro reshuffles the dispatch board every 10 minutes during business hours. The same page says it "still needs dispatchers to oversee it" and "never overrides a human decision". A board that moves every ten minutes is a hard thing to make promises about from outside.

ServiceTitan sells its own AI Virtual Agent, and it does book. Its page quotes a 70% booking rate overall and 90% "capacity adjusted", without defining the second number. I read the gap as calls that came in when the board had no room. That's my reading, not theirs. The same page says you "customize job types and dispatch fees to alert the AI Virtual Agent to what it can, and can't book." The agent that sits inside the data ships with a can't-book list.

So write yours: the calls the AI may book, and the calls it catches and hands over.

The four-yes test: when an AI can book the job

I use four questions. The AI books a call type only if all four are yes.

1. Same length every time? You know the duration before anyone sees the unit.
2. Any tech? Everyone on that calendar is trained and certified to do it.
3. Live board? The agent reads your real schedule and your capacity rules, not a copy of a calendar.
4. A day out? The slot is far enough away that a person can move it before it becomes a broken promise.

Here's how HVAC calls score on the first two.

Call	Same length?	Any tech?	What the AI does
Seasonal tune-up	Yes	Usually	Books it, if tests three and four pass
Confirm or move an existing visit	Yes	Already assigned	Handles it
No cool, no heat	No	No	Catches, qualifies, hands off
Replacement estimate	No	No	Hands off, and you ring back first
Commercial or refrigeration	No	No	Hands off

The yes rows match what the vendors built their agents for. ServiceTitan's page lists booking maintenance jobs as recurring services under the member profile, plus confirming and rescheduling existing appointments. Known length, known customer.

My honest read, by setup. On ServiceTitan, the built-in agent is the one that can pass test three. Let it book the yes rows, put no-cool on the can't-book list for the weeks the forecast is ugly, and ask your account manager whether it respects the hours you hold back. On Jobber, put only the services that pass tests one and two on the booking form, and use the earliest availability setting so nobody books themselves in for this afternoon. Receptionist books through that form, so I'd expect the same settings to apply. Test it. If you run two vans off a shared calendar and a whiteboard, nothing passes test three. Hand off every call. That's the shop I build for.

UK readers: if you're a sole trader fitting splits and heat pumps, you are the dispatch board. Test two is always yes. Test three is never yes, because the board is in your head, and it changed when this morning's job turned up a seized fan motor. Hand off, and ring back from the van.

What a wrong slot costs, worked out

Owners ask whether handing off loses the job. Sometimes it does. So run both sides.

Say the phone books 20 no-cool calls a week in July, each into a one-hour slot. Say one in five turns out to be something else: a part you don't carry, a system that needs replacing, a job the tech who arrived can't do. That's four wrong slots a week. Each one costs a second visit, a bumped customer behind it and a phone call to apologise. Call it an hour and a half of tech time. Four of those is six hours a week. If your billable hour is $150 (about £115), that's $900 a week, in the one month you can't spare it.

Now the hand-off. The same 20 calls reach the person at the board as a text: what's happening, the address, the age of the system if the caller knows it, member or not, anyone vulnerable in the house. Say each callback takes three minutes, because the questions are already answered. That's an hour a week. One hour of callbacks against six hours of van time.

The catch is the callback. A hand-off nobody picks up is just a slower voicemail. If you can't ring back inside ten minutes on a hot day, fix that first. The three-line summer phone is how I'd set that clock. For what each missed call is worth, the calculator runs it with your own numbers.

What AI can't do here

It can't see that the two o'clock is running long. It can't tell a capacitor from a compressor down the phone, and neither can you, not for certain. It can't know the tech with the recovery machine is off on Friday. It can't decide that an old system should get the owner, not the newest tech. Even ServiceTitan's agent, with the whole board in front of it, can escalate or transfer a call to a live CSR when it "falls outside defined rules or requires human judgment".

What it can do is make your callback short. When the caller asks for a time, it says: "I can't give times, I'm the AI assistant. Dave will ring you back with one." Then it texts Dave and gets out of the way. Anything it says on your line is your promise, not the software's.

Do this this week

1. Write down your call types. Five or six lines. Run each through the four-yes test.
2. Pull the hottest week of last summer. Count the no-cool jobs that ran over their slot or needed a second visit. That's your wrong-slot rate with people booking.
3. On ServiceTitan, find out who adjusts capacity on a hot day, and check the Virtual Agent's can't-book list against it. On Jobber, check which services are on the booking form, how long each is set for, and the earliest availability.
4. Ring your own line and ask, "Can someone come at two today?" If it says yes, find out what it checked before it answered.
5. Write the hand-off sentence: who rings back, and how fast.

If you'd like a second opinion on which of your calls pass the test, book a growth call. Thirty minutes, free. If the answer is "switch on the agent you already pay for and give it a short list", that's what I'll say. What I'd build for an HVAC shop is on the HVAC page.