What 34 HVAC & Plumbing Contractors Told Us About Their Scheduling Day

We spent three days at PM Springfest in Toronto this April with a yellow polo on, a notebook in hand, and one question we kept asking owners and field-ops managers walking past our booth:

"Walk me through how a customer gets onto your calendar. From the first phone ring to the confirmed appointment — what actually happens?"

By the end of the show we had 34 logged conversations. HVAC owners running 8 vans. Plumbing shops doing $4M a year. A pest control operator with 12 techs. A roofing company still on a whiteboard. A restoration crew with three locations and overlapping service zones.

We didn't pitch anything. We just listened. And what struck us, almost immediately, was that the friction in their day didn't live where the marketing decks said it would. It lived in the booking layer. The moment a homeowner reaches out and tries to get onto the calendar.

That's where the wheels were coming off, across every trade and every software stack we encountered. The way home services scheduling software handles that exact moment — or doesn't — was the single biggest theme of the show, and almost nobody on the main stage was talking about it.

Here's what 34 contractors actually told us.

Before we get into the patterns, one upstream point worth saying out loud.

Every other operational pain in a service business — late arrivals, tech utilization, dispatch chaos, missed callbacks, ETA accuracy — sits downstream of the booking moment. If a job lands on the calendar at the wrong time, in the wrong sequence, with the wrong qualification, every system after it is trying to clean up a mess it didn't create. Dispatchers re-routing. Techs driving longer than they need to. Office staff calling customers to push appointments. All of it traces back to a booking decision that didn't account for reality.

The reverse is also true. Fix the booking layer and the downstream layers get easier almost on their own. A booked job that already accounts for drive-time, crew skills, and service zone doesn't need to be re-routed at 7 AM. It just needs to be assigned and run. That's where the next layer — the AI Dispatcher layer FieldCamp has been building — actually shines, because it gets a clean handoff instead of a salvage job.

In other words: the booking layer is the highest-leverage thing in the stack, and most operators are still treating it like the lowest. That mismatch is what we kept hearing in Toronto, in five different shapes.

We expected the booking conversation to start with software. It didn't. It started with the phone.

Almost every owner described the same broken default: customers call in, a CSR (or the owner's spouse, or the owner himself) picks up, runs through a six-question qualification script, opens a calendar, and offers a slot. That's been the workflow since 1995.

But customers don't want it anymore.

"Honestly, the calls I get now are mostly from people over 50. The younger ones text. The young-young ones just go away if there's no online booking." — Plumbing owner, 6 techs

The trades are the last consumer category where phone-first is still the default. Every other category — food, retail, travel, healthcare — made the shift between 2005 and 2015. The contractors who said this out loud were the ones already noticing leakage. The ones who didn't say it out loud were still answering most of their own calls and assuming volume was steady.

It wasn't.

Jobber came up in almost half the conversations. Not as a villain — most owners genuinely like it. But the same sentence kept showing up at the 5–15 tech band:

"Jobber is alright, but the cost and the customization are the issue." — HVAC owner, ~10 techs

"Jobber is a pain. Too cumbersome, too manual. I need an AI dispatcher." — Plumbing owner, 7 techs

That second quote is worth pausing on. The word "AI" came from the contractor, not from us. He used it the way you'd use the word "scanner" — as if it were already a thing he expected to have. Owners aren't AI-skeptical anymore. They're AI-curious and frustrated their current tools don't have it yet.

When you push on "Jobber is cumbersome," it's almost always the same complaint: the calendar is fine, but the workflow around it is manual. Customers have to call. CSRs have to type. Drive-time lives in someone's head. None of the smart parts are automated.

That exact phrase, or a close variant, came from two different owners on different days. One HVAC operator. One plumbing operator. Neither knew each other.

What they meant was specific: Housecall Pro nails the in-app scheduling UI — once a job is in the system, the calendar is genuinely good. But the layer before the calendar, the lead capture and qualification layer, was where they kept losing money. A lead would come in via the website form, sit in an inbox until a CSR got to it, and by the time someone called back, the customer had already booked with whoever picked up the phone first.

The booking moment had been moved from the customer's pocket to the contractor's office, and the contractor's office was closed half the time.

This was the pattern we expected to come up only when we asked about dispatch. It kept coming up when we asked about booking.

"My online form lets people pick any open slot. That's a problem. They pick 9 AM Saturday in one neighborhood and 9:30 AM Saturday across the river. Then I'm the bad guy for being late to the second one." — HVAC owner, ~8 techs

That second quote stuck with us. Most online booking forms are essentially calendar-availability forms — they show what's open. They don't show what's feasible. The customer picks a slot the truck can't physically reach in time, and the contractor eats the consequences: late arrivals, angry homeowners, one-star Google reviews.

The fix isn't to take booking offline. The fix is to make the booking itself aware of the route — so the slots that show up are only the ones the day's existing schedule can actually accommodate.

We started asking owners a specific question late in the second day: "What happens if a homeowner calls you at 7 PM on a Tuesday?"

The answers landed in a tight range. Most went to voicemail. A few rolled to an answering service that took a name and a number for callback. Two had a 24/7 call center but admitted the call center couldn't actually book — it just relayed messages. Zero shops we talked to had a true 24/7 booking path that didn't depend on a human picking up.

And here's the thing — a huge portion of trades leads come in outside business hours. Furnaces don't fail at 10 AM. Pipes don't burst at 2 PM. The window when the contractor is most reachable (9–5) is exactly when fewer emergencies happen. The window when the contractor is unreachable (evenings, weekends, overnight) is when the highest-intent leads actually arrive.

Most expensive sentence we heard at the show.

If you average the conversations together, here's what a typical contractor's booking morning looks like:

6:00–6:45 AM — Owner or office manager sorts through 6–12 overnight messages. None of them are appointments yet. All of them need a callback.

6:45–7:30 AM — Callback round. Half the homeowners pick up. The other half are at work, on the school run, or in the shower. Voicemail tag begins.

7:30–8:15 AM — Whoever picked up gets qualified, slotted, and confirmed. CSR eyeballs the map to check the assignments aren't insane.

8:15–9:00 AM — First customer of the day calls because the tech is "running late," even though the tech is technically on time according to the original schedule.

Every morning. Across HVAC, plumbing, roofing, pest, restoration. The software changes. The morning doesn't.

What's striking is how much of this is transactional work that doesn't need a human. Looking up service areas. Confirming addresses. Asking the same six qualification questions. Reading availability off a calendar. None of it builds a relationship. All of it currently consumes one.

The clearest takeaway after 34 conversations: the modern trades operations stack is splitting into two distinct layers, and the operators pulling ahead are the ones putting a real specialist in each.

**The booking layer — where Driive is genuinely doing something different.** When it comes to actually closing the booking gap we kept hearing about, Driive is the cleanest implementation we've seen in the trades. Drive-time-aware availability so the slots a customer can pick are slots the route can actually serve. Pre-qualification baked into the booking flow so tire-kickers don't eat CSR time. A 24/7 virtual scheduler ("Dot") that picks up after hours and books, not just relays. The pitch we kept hearing from owners — "I just need a way for customers to book online without my team being on the phone all day" — is essentially the Driive product description. If your bleed is at the booking moment, this is the layer to fix first.

The dispatching layer — where FieldCamp is the strongest tool we've seen. Once the booking layer is sorted, the next bottleneck moves immediately downstream: who goes to which job, in what order, with which skills, accounting for the live state of the day. That's a different math problem and it needs different software. FieldCamp's AI Dispatcher is the most thoughtful implementation we've encountered — assignment logic that factors drive-time, certifications, crew availability, and service zones in real time, instead of a dispatcher redrawing the whiteboard at 7 AM. Once dispatch is humming, FieldCamp's AI Command Center layers real-time visibility on top — every job, technician, route, and dollar on one screen — the operational dashboard most teams build in spreadsheets, already built in. If your bleed is between booked-job and tech-on-doorstep, this is the layer to fix.

The two products sit cleanly next to each other. Driive owns the moment the customer reaches out. FieldCamp owns the moment that booked job has to become a dispatched job. Neither is trying to be the other. That's the right shape of a modern stack — specialists at each layer, not a single tool pretending to do both jobs at a B-minus.

Thirty-four conversations isn't the whole industry. But the patterns were tight enough, and consistent enough across trades, that we'd bet they generalize.

If we had to compress what we heard into a single sentence: the trades have spent the last decade optimizing the wrong end of the workflow. Most of the software investment has gone into the back office — invoicing, dispatch dashboards, route optimization, mobile apps for techs. That stuff matters. But the front of the workflow, the booking layer where the customer actually decides to spend money with you, has been left almost untouched. Phone tag. After-hours voicemails. Forms that don't know the route. CSRs typing data a system could collect on its own.

The shops that fix that layer over the next 24 months are going to look very different from the ones that don't. They'll capture leads at 11 PM that their competitors lose. They'll book jobs that actually fit the route. They'll free their office team to do the relational work that builds repeat business, instead of the transactional work that just runs the calendar.

That's the bet, and it's what 34 contractors — in their own words, without us prompting — told us was coming.

*This piece is based on 34 in-person conversations at PM Springfest 2026 in Toronto, April 2026. Quotes have been lightly edited for clarity and trade categories have been generalized where identifying details would be obvious.*