Your Dispatcher Role Doesn't Exist Yet. That's the Problem.

The first call I missed after launching Reeves Electric wasn't a missed call. I answered it. It was 9:31pm on a Tuesday in March 2022, a customer whose breaker kept tripping on the kitchen circuit, and she was annoyed in the quiet way that means she's already composing the review in her head. I walked her through a reset. Told her someone would be out first thing Thursday. Wrote it on a sticky note.

The sticky note ended up under my laptop. Nobody went Thursday.

That wasn't just a customer service failure. It was a dispatching failure. There was no system that owned the path from that phone call to a booked slot on a tech's calendar. There was just me, in my head, trying to hold a five-job-a-day schedule together with muscle memory and goodwill. A sticky note under a laptop is what informal dispatching actually looks like.

The section below is going to sound familiar if you're running three to five trucks. That's intentional.

---

The Hours You're Spending on This Are Not Free

Every owner-run shop has a version of this. You're in the truck, knee-deep in a panel, and your phone buzzes twice — one is a new inquiry, one is a tech asking whether to wait on a permit or move to the next job. You handle both between pulling wires. You reroute the tech in your head, flag the inquiry mentally, move on.

That's not multitasking. It's context switching. Every interruption pulls you out of the work that only you can do.

You can see a $52,000 salary on a P&L. You cannot see the $9,200 panel-plus-service-upgrade quote you didn't write because you were handling a scheduling callback at 2pm. The expense is real. It just doesn't have a line item.

At three trucks doing residential service in Austin, my rough daily capacity was eight to ten dispatched jobs. Getting from eight to ten required someone watching the board in real time and filling gaps when a job ran short or a cancellation came in. When I was doing that from the truck, I caught the obvious gaps and missed the subtle ones. The demand was there. The mental overhead wasn't manageable.

---

Dispatching Isn't Scheduling. It's Intake, Conversion, and Utilization.

People picture someone answering phones and moving names around on a calendar. That's not what the role actually controls.

What it controls: whether a caller books or hangs up. Whether a tech's day has gaps or doesn't. Whether a same-day cancellation turns into a filled slot or a dead afternoon. Each of those has a direct dollar figure attached to it.

I've said this before and I'll keep saying it — the biggest unspoken difference between shops that grow and shops that plateau is intake. The moment a real customer with a real problem calls and hears a confident, scripted intake versus a confused "uh, let me check with the owner" — that moment belongs to whoever picks up the phone. When no one formally owns it, it belongs to whoever's nearby, in whatever headspace they're in, with no script and no accountability.

The practice I run now — every week, my dispatcher and I pull four calls in CallRail, two that booked and two that didn't, and tag what worked and what broke down — only exists because the role is formalized. Before I had a dispatcher, that review never happened. Which meant the booking rate never got analyzed and I was running whatever conversion rate I'd accidentally built.

Booking rate doesn't improve because you run a better ad. It improves when someone gets better at answering "how soon can you come out?"

---

When the Math Says Three Trucks, Not Five

I've heard it framed as a five-truck threshold. I think that's about two trucks too late.

Here's how I think about it. As the owner of a residential service shop, with a master license and the ability to scope complex jobs, my time is worth at minimum $120 an hour to the business. Not my pay — the value of what I produce when I'm doing work nobody else on my crew can do: quoting a panel upgrade, deciding whether a job needs a permit pull, training a new tech. When I'm instead handling a scheduling callback at 1:45pm, I'm spending that capacity on something a well-trained CSR does for $18 an hour.

In early 2022, dispatching was running me somewhere between two and a half and three hours a day. That's not a guess — I started logging it during the ninety-day intake rebuild. So call it $300 of owner-level capacity, daily, going toward work that didn't require a master's license.

A part-time CSR in Austin running 25 hours a week ran me about $34,000 fully loaded when I made the hire. The math wasn't close.

Reeves Electric did $1.4M in 2024. I'm tracking toward $2.1M in 2026. I'm not sharing those to impress anyone. I'm sharing them because the dispatcher hire didn't come after the revenue growth — it preceded it. Getting those hours back is what made the quoting cadence and the weekly numbers reviews actually possible.

---

You Probably Don't Need a Full-Time Dispatcher Yet. But the Role Still Needs an Owner.

I don't think every three-truck shop needs a W2 dispatcher on payroll Monday morning. The mistake isn't the timeline. The mistake is leaving the role informal.

A part-time CSR who formally owns intake and scheduling closes most of the gap. That's the right first hire. Not someone who answers phones when they're free — someone whose job description begins with "you own the phone and the schedule."

My own sequence: bookkeeper first. Clean books are the foundation for every hire conversation that follows — without them you're making staffing decisions on gut feel. Then the CSR role, sixty days later, once the financials were stable enough that I could train someone without feeling like I was handing them a burning building. I didn't hire both in the same week. I tried that once at Lonestar. Too many moving parts at once — when something broke, I couldn't tell what was causing what.

The CSR role at Reeves Electric didn't arrive as a full dispatcher. It evolved. Volume grew, the scheduling complexity grew, and over about eight months the role became clearly dispatcher-shaped. That's a reasonable path. Skipping the formalization because you think you're managing fine is not.

One thing I won't move on: CallRail has to be running before the hire, not after. Tracking numbers assigned to every active channel. Call recording on. Four weeks of baseline data collected. You need to know your current booking rate by source before you hand someone the phone. Otherwise you have no starting line and no way to evaluate whether anything is actually improving.

---

What Month Two Looked Like

My NPS in month two of Reeves Electric was a 4. Not 40. Four.

Here's what was actually happening. Every call was improvised. When I was in the truck, I answered when I could and called back when I remembered. Same-day schedule changes — tech finishes early, job cancels — I handled in my head, which meant inconsistently. Sometimes I caught the gap. Sometimes a tech drove home at 2pm while a customer waited three days for an opening.

The symptoms were specific. Late callbacks. Wrong-tech dispatches — sending my apprentice to a job that needed a journeyman. No-shows where I'd mentally booked something that never made it onto anyone else's calendar. None of those felt like dispatching failures in the moment. They all felt like I had too many things going at once.

For ninety days I answered every single call myself. I took notes on the specific breakdown points — not "customer was unhappy" but: call came in at 4:47pm, I was on a panel, called back at 6:15pm, customer had already booked someone else. Or: tech dispatched to a 200-amp upgrade, customer expected a quote, tech didn't have the paperwork to run a load calc. I was documenting, without fully realizing it, exactly what a dispatcher needs to know, own, and execute.

By month nine, NPS was 81. That improvement wasn't one thing. But a real portion of it wasn't technical quality or pricing. It was customers being handled well on the phone — answered quickly, told what to expect, confirmed the day before. Once someone formally owned that, with a script and a schedule and a weekly review, it stabilized in a way that gut-feel dispatching never could.

---

Three Things to Do Before You Post the Job

Don't post the listing this week. Do these first.

Get CallRail running. Buy tracking numbers, assign one to each active channel — Google LSA, your website, your truck wrap, whatever you're running. Turn on call recording. Run it for four weeks. What you're building is a baseline: booking rate by source, average call duration on booked versus non-booked calls, and a library of real calls your new hire can learn from. You cannot hand someone a job to improve without showing them the starting line.

Write the intake script. I use a five-question phone screen for every call that could involve a panel or service upgrade: How old is the panel? Do you know the brand? Where's your meter base relative to the garage? Any tripping or flickering recently? Has any previous work been done on the panel? Three minutes, and it separates a $700 charger install from a $6,400 service upgrade before anyone rolls a truck. That script lives in a shared Google Doc, referenced on the dispatcher's second monitor, and it's what a new hire owns on day one. A new dispatcher needs a written script to run, not a feel for how conversations usually go.

Put the weekly call review on the calendar before the hire starts. Not after. Before. Thirty minutes, same time every week, you and your dispatcher, four calls from CallRail. Two that booked, two that didn't. The accountability structure has to exist from day one. Without it, you hired someone to answer phones. With it, you hired someone actively working your booking rate.

Get those three things in place. When you post the job, whoever walks in has a tool stack, a documented intake process, and a recurring review structure ready to go.

---

FAQ

If I'm running two trucks, is this relevant yet?

Yes, with a qualifier. You probably can't justify the hire yet. But ask yourself whether you're currently losing jobs to slow callbacks, fumbled phone conversations, or a schedule you're holding together in your head. If yes — and most two-truck owners answer yes — set up CallRail now and document the intake script. When you add the third truck, you'll have a baseline already built instead of starting from scratch.

What's the difference between a dispatcher and a CSR?

At a small shop, mostly the same role. A CSR owns intake — the first call, the booking, the pre- and post-job communication. A dispatcher owns the real-time board: rerouting techs, filling cancellations, managing same-day changes. At five trucks those might be two people. At three trucks, one person does both. When I say hire a dispatcher, I mean hire the person who formally owns the schedule and the phone.

How do I know if my dispatcher is actually performing?

Four numbers: booking rate by source, average time from first call to booked appointment, tech utilization (billable hours divided by available hours), and how often a same-day cancellation gets filled versus stays empty. If the dispatcher is doing the job, the first three go up and the last one stops being a recurring problem. Pull those numbers out of CallRail and your field service software — Jobber, Service Fusion, whatever you're on. Review them monthly at minimum.

I tried a part-time scheduler before and it didn't work. What usually goes wrong?

No intake script, so the person improvised every call and got inconsistent results. No call recording, so neither of you could tell what was or wasn't working. No recurring review, so bad habits ran for months before you noticed. The role was undefined and unmonitored, and the person had no real mechanism to improve. Fix the structure before you post the job again.

In-office or remote — does it matter?

I run my dispatcher in-office. The thing you lose with remote isn't the work itself — the scheduling software and CallRail both work fine remotely — it's the ambient information. A tech stopping in to say the 2pm job is running long. A customer on hold while you're mid-call. You can rebuild that through a structured Slack channel or a dedicated group thread for the board, and some shops do it well. I've just found in-office easier to manage. If remote is what makes the hire possible, do it with the structured communication channel in place and clear expectations on response time.

When does part-time need to become full-time?

When your part-time person is consistently maxing their hours and you're still seeing missed calls, slow callbacks, or gaps that aren't getting filled. In my shop that showed up around four trucks running eight or more jobs a day. The signal isn't truck count — it's when the volume has outgrown the hours. At that point you've also been measuring booking rate and utilization long enough to know exactly what the full-time hire is worth. The decision isn't a gut call. It's already in the numbers.