Episode 9·

Stop Overbooking June: Capacity Buckets and Triage

Intro

For owner-operators and dispatchers heading into summer rush who are tired of blown windows, overtime, and angry callbacks when emergencies hit a packed board. You'll get a practical three-bucket capacity plan you can install this week, plus the triage system that protects high-value work without turning anyone away.

In This Episode

Mike and Chris walk through why first-come, first-served scheduling breaks during peak season and how a simple three-bucket capacity plan prevents the chaos. They cover the four-step triage process (classify by urgency and value, place in the right bucket, assign windows with buffer, route for density), specific tool settings in ServiceTitan, Jobber, and Housecall Pro, and the common failure points that blow up the system. The episode includes dispatcher scripts for urgent vs. standard calls, concrete daily numbers for capacity holds, and the 1 p.m. release rule that keeps unused slots from going to waste.

Key Takeaways

  • Hold 2-3 same-day slots per crew for urgent work and 4-6 next-day slots for priority revenue, with a 1 p.m. release rule for unused capacity
  • Run a four-step triage on every call: classify by urgency/value/location, place in bucket, assign window with buffer, route for density
  • Make capacity holds visible on your board using ServiceTitan's Adjustable Capacity Planning, Housecall Pro tags, or Jobber's calendar color rules to prevent CSRs from backfilling with low-value work

Timestamps

Companion Resource

Chris: You need to stop booking every call that comes in.

Mike: Stop booking calls.

Chris: Stop booking them the way you're booking them now. First come, first served, next open slot, pack the board.

Mike: That's how every shop I know runs it.

Chris: And that's why every shop you know melts down in June. You're scheduling April weather in a July world. The board looks full on Monday, and by Wednesday you've got two no-cooling emergencies stacked on top of a maintenance you should've run in March, a tech driving forty minutes across town between jobs, and your dispatcher making promises you can't keep.

Mike: You just described last summer.

Chris: I just described every summer. And the fix isn't more techs. It's not more hours. It's deciding — before the phone rings — which jobs get today, which jobs get tomorrow, and which jobs get routed by zone into a standard window.

Mike: Three buckets.

Chris: Three buckets. And a two-minute triage on every single call.

Mike: If you're heading into AC season without a capacity plan — no holds, no triage, just whoever calls first gets the next slot — you are going to blow windows, burn overtime, and lose the high-value jobs that actually pay the bills. That's not a guess. That's what happens every peak season to shops that book like it's still spring.

Chris: I'm Chris. That's Mike. And today we're building the three-bucket capacity plan you can install this week — same-day holds, next-day priority, standard by zone — plus the triage your dispatcher runs on every call before anything touches the calendar.

Mike: So let me paint the picture for anybody who hasn't lived through a bad June yet. You've got four techs. Monday morning the board is stacked — eight jobs per tech, nice and full. Feels great.

Chris: Feels great at seven forty-five.

Mike: By ten thirty, two no-cooling calls come in. Real emergencies — elderly customer, no AC, ninety-two degrees. You can't say no.

Chris: You shouldn't say no. Those are your highest-value calls.

Mike: Right. But where do they go? You've already packed the board. So now you're bumping a maintenance to fit the emergency, the maintenance customer gets a call saying we need to reschedule, and the tech who was supposed to run that maintenance is now driving twenty-five minutes across town to the emergency because you didn't plan for it to be in his zone.

Chris: And that's one day. Multiply that by twelve weeks of peak and you start to see the real cost. It's not just the overtime — although that's real. It's the blown windows. J.D. Power did a study on in-home service visits and found that shorter, reliable arrival windows are directly tied to higher customer satisfaction. When you miss a window or stretch it from two hours to four because you're scrambling, the customer remembers.

Mike: They remember. And they tell Google.

Chris: They tell Google. So the cost of not having a capacity plan isn't just overtime dollars. It's callbacks, it's one-star reviews, it's the replacement job you couldn't fit because a tune-up was sitting in the slot.

Mike: Okay, but I want to push on something. You said stop booking first come, first served. That feels risky. If a customer calls and I say "we can't get to you until Thursday" when I've technically got an open slot tomorrow—

Chris: You're not turning anyone away. You're routing them to the right slot. That's the difference. Capacity-based scheduling doesn't mean fewer jobs. It means the right jobs in the right slots. The emergency gets today. The approved repair estimate — that's money waiting to be collected — gets tomorrow. The routine maintenance gets a standard window routed by zone so your tech isn't crisscrossing the county.

Mike: Three buckets.

Chris: Three buckets. Same-day urgent, next-day priority revenue, standard routed. And every call gets classified before it touches the calendar.

Mike: All right, walk me through what the dispatcher actually does when the phone rings.

Chris: Four steps. And I mean four steps on every call — not just the ones that feel urgent. Step one: classify. Your CSR asks three questions. Is this urgent — no cooling, active leak, safety issue? What's the job value — is this a repair, a replacement estimate, a membership tune-up? And where are they — which zone?

Mike: You're asking my CSR to think about job value on a ringing phone.

Chris: Not in those words. They're asking what's going on, and they already know from the job type whether it's a diagnostic that could turn into a five-thousand-dollar replacement or a twenty-minute filter change. You're just making the classification explicit. Tag it P1, P2, or P3.

Mike: P1 is the emergency.

Chris: P1 is urgent — no cooling, active leak, safety. That goes into the same-day bucket. P2 is priority revenue — the approved repair, the replacement estimate the customer already said yes to, the VIP member with an issue. That goes next-day. P3 is everything else — maintenance, non-urgent diagnostics, routine work. That goes into a standard window by zone.

Mike: Okay, step two is placing it in the bucket. What's step three?

Chris: Assign the arrival window with buffer. And this is where shops mess up. During peak, you do not promise exact times. You offer two windows — eight to twelve, twelve to four. And you build in thirty to forty-five minutes of buffer per visit so your tech isn't running from one driveway straight to the next with zero margin.

Mike: We used to promise exact times. "Your tech will be there at two." And then the eleven o'clock job runs long, and now you're calling the two o'clock to push them back, and they're furious because they took off work.

Chris: Right. A four-hour window with a reliable show-up beats an exact time you miss. The research backs this up — customers care more about you showing up inside the window than about the window being narrow. Housecall Pro lets you set default arrival windows from fifteen minutes up to four hours, and you can override per job. Jobber has arrival windows on their Connect and Grow plans. ServiceTitan ties it into their appointment windows. The tools already support this.

Mike: And step four?

Chris: Route for density. When you're placing P2 and P3 work, you keep it in the same zone as existing runs. If you've got two open slots and one is near three jobs already booked in the north side and the other is a solo run on the south side, you put the new job on the north side. Less windshield time, more wrench time. Peer-reviewed research on fleet routing shows optimized routes consistently cut total field time compared to manual scheduling — the exact percentage varies, but the direction is clear.

Mike: So Jobber does some of this automatically, right?

Chris: Jobber's Online Booking uses the client's address and estimated travel time to surface slots near existing jobs. It avoids unrealistic back-to-back appointments. Housecall Pro has Service Areas — you define zones by city or ZIP, assign techs to each zone, and the system steers work to the right crew. ServiceTitan's Weekly Dispatch Board gives you a seven-day view so you can see where the density is and where the gaps are.

Mike: I didn't know Jobber was doing the travel-time thing automatically.

Chris: It's built into Online Booking. Not everyone has it turned on, but it's there.

Mike: Okay, so I buy the framework. But give me real numbers. I've got three crews. What do I hold?

Chris: Starting point — and you adjust this based on your actual call patterns — two to three same-day slots per crew for urgent work. Four to six next-day slots per crew for priority revenue. Everything else is standard, routed by zone.

Mike: So on a three-crew day, I'm holding six to nine same-day slots across the shop.

Chris: And twelve to eighteen next-day. The rest of your capacity is open for standard work, but it's routed — not just dropped into the next open hole.

Mike: That's a lot of holds. What if the emergencies don't come?

Chris: They will in peak. But if they don't — and this is important — you release unused same-day holds at one p.m. Not earlier. At one o'clock, if you've still got same-day slots open, you release them to P2 work. High-value repairs, approved estimates. You don't release them to a twenty-dollar filter change.

Mike: One p.m. release rule.

Chris: One p.m. And you re-evaluate your next-day holds at the same time. If you've had three consecutive days where same-day holds went unused, you pull one slot back the next morning. The numbers aren't permanent — they're a starting point you tune weekly.

Mike: All right, so the dispatcher has the buckets, they've got the triage. What does the actual call sound like?

Chris: For a P1 — urgent, no cooling — the script goes something like this: "Thanks for calling, we'll get you taken care of today. Quick safety check" — and they ask two or three diagnostic questions. Then: "I'm holding a same-day arrival window, eight to twelve" — or twelve to four, whatever's open. "We'll text updates while the tech is en route. Can you approve a diagnostic up to" — whatever your number is, eighty-nine dollars, a hundred nineteen — "so we can move fast?"

Mike: That's clean. What about P3 — the standard job?

Chris: "Good news, we're routing your area on Thursday with a twelve-to-four arrival window. That keeps you in the fastest route and avoids reschedules. We'll text updates. Does that window work, or would Friday eight-to-twelve be better?"

Mike: "Good news, we're routing your area." I like that. It doesn't sound like you're pushing them off. It sounds like you've got a system.

Chris: Because you do have a system. And customers respond to that. They'd rather hear "we're routing your area Thursday" than "uh, let me see what's open... how about... Wednesday? No wait, that's full..."

Mike: Yeah, that's what it sounds like right now.

Chris: And there's a daily rhythm to this. Every morning at seven forty-five — two minutes, not ten — you run a stand-up. Yesterday's misses. Today's bucket targets per crew. Any warranty or recall work that has to fit today. Road closures or zone shifts. Done. The rule coming out of that stand-up is simple: every call gets bucketed before it touches the calendar. No exceptions.

Mike: Okay, so what goes wrong? Because I know something goes wrong.

Chris: Three things. First — and this is the most common one — your CSR backfills same-day holds with low-value work. A tune-up calls in at nine a.m., there's a same-day slot open, and they drop it in because the slot is empty and the customer wants today.

Mike: Because the CSR is trying to be helpful.

Chris: Right. And now when the no-cooling call comes at ten thirty, you've got no room. The hold exists to protect against exactly that call. You have to make the holds visible on the board — block them, color them, whatever your tool supports. In ServiceTitan, Adjustable Capacity Planning lets you define which job types can claim which slots. The system enforces it. In Housecall Pro, you use tags — P1, P2, P3 — and you train dispatch to check the tag before booking. In Jobber, you can use calendar color rules based on keywords in the visit title to make priority jobs visually obvious.

Mike: So the CSR can see at a glance — that red block is a same-day hold, don't touch it.

Chris: Exactly. Second failure: you didn't pre-book your maintenance into shoulder season. BDR — they're a big HVAC coaching outfit — has been hammering this for years. If your membership tune-ups are all stacked into May and June, you've just filled your peak capacity with your lowest-revenue work. Those tune-ups should be running in March, April, October. Not competing with five-thousand-dollar replacements in July.

Mike: We do that. We let members book whenever they want, and they all want May.

Chris: So you book them proactively. Call them in March, schedule the tune-up, get it done before the rush. That frees peak capacity for the work that actually pays.

Mike: And the third failure?

Chris: No warranty or recall hold. You need at least one slot per crew per day reserved for warranty and recall work. Because when a compressor you installed last month fails, that customer is not waiting until Thursday. And if you don't have a slot, you're bumping paying work to fix your own mistake.

Mike: Which costs you twice.

Chris: Which costs you twice. Now — if that warranty slot goes unused three days in a row, you roll one slot to P2 the next morning. You don't let it sit empty forever. But you start each day with the hold in place.

Mike: I want to come back to something that's been bugging me. The customer who calls for a standard job — a routine diagnostic, nothing urgent — and I'm telling them Thursday. Meanwhile the guy who calls an hour later with an emergency gets today. That feels unfair.

Chris: It feels unfair if you think of scheduling as a line. First in line, first served. But that's not how a hospital runs an ER, and it's not how a shop should run peak season.

Mike: We're not an ER.

Chris: No, but the principle is the same. You triage by severity and value because the alternative is worse for everyone. The standard customer who gets a reliable Thursday window with a text update and a tech who shows up on time — that customer is happier than the one who got promised Tuesday, got bumped to Wednesday because an emergency came in, and then the tech showed up forty minutes late because he was driving across town from the emergency.

Mike: Yeah. That's what actually happens.

Chris: The research from J.D. Power supports this — customers care about reliability more than speed. A predictable window they can plan around beats a fast promise you break. And your standard customers still get routed efficiently. They're clustered by zone, they've got buffer built in, they get text updates. They're not being punished. They're being scheduled intelligently.

Mike: And if the same-day bucket doesn't fill, you release it at one.

Chris: At one. So the capacity isn't wasted. It's protected until you know you don't need it, and then it flows to the next highest-value work. The board stays full. The difference is what fills it and when.

Chris: So — back to where we started. You need to stop booking every call into the next open slot. Not because you're turning work away. Because you're protecting the board so the right work lands in the right place at the right time. Three buckets — same-day urgent, next-day priority, standard by zone. A four-step triage on every call. A two-minute stand-up every morning. And a one p.m. release rule so nothing sits empty.

Mike: And if you want the whole thing on one page — the bucket targets, the triage steps, both dispatcher scripts, the tool toggles for ServiceTitan, Jobber, and Housecall Pro — we put together a Peak-Week Dispatch Kit. It's on the Resources page. Tape it by the phones.

Chris: That's the move.

Mike: All right. One question to ask yourself this week.

Chris: Look at your board from last Monday. How many jobs got bumped, rescheduled, or ran late because an emergency came in and you had nowhere to put it? If the answer is more than one — you need buckets before June.

Mike: That's the question. Thanks for listening. I'm Mike.

Chris: I'm Chris. We'll see you next Tuesday.

capacity planningdispatchpeak seasonHVAC schedulingtriage systemServiceTitanJobberHousecall Proroute optimizationcustomer satisfaction