Your Intake Process Is Losing You Jobs Before Trucks Roll

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

I'd spent six months before launch doing everything right. Pricing model, software stack, two branded vans. I thought I was ready. What I hadn't planned for was the fact that I was now, personally, the guy who received the irritated 9:30pm call from the customer whose breaker kept tripping — and that I had no idea what to say to her that would actually help.

The electrical work was fine. My work has always been fine. The problem was everything that happened before and around the truck showing up. What the customer was told on the first call. What the tech had — or didn't — when he pulled into the driveway. That was the job. I just didn't know it yet.

---

The Call Is the Job

At Lonestar Electrical Services, where I ran service work from 2014 to 2021, there was a dispatch process. A CSR team. Intake forms, job codes, a scheduling system somebody else maintained. I worked inside that structure for seven years without having to think about it. I thought it transferred automatically.

It doesn't. It exists because someone built it.

When I launched Reeves Electric, none of that infrastructure came with me. I had a CRM and a phone number. What I didn't have was a documented intake process — because I assumed my experience meant I already knew how to run the call. That assumption cost me the first ninety days.

The call comes in. Someone answers it — maybe the owner, maybe a spouse, maybe whoever's nearest the phone. They figure out what the customer needs, schedule something, and a truck rolls. The whole thing runs on memory and habit.

That's not a system. That's hoping.

---

What Bad Intake Actually Costs You

Intake failures almost never show up on the line where you'd look for them.

You lose a booking, you think the customer price-shopped you. You get a bad review, you think the tech had a rough day. Your average ticket is down, you think it's the market. Your callback rate is up, you think it's a parts problem.

What I saw in my own shop — and what I hear from guys I talk to at every scale — is that most of this traces back to the first call. Owners never know, because they don't record their calls and can't hear what's actually going wrong.

The intake failure almost never looks like a missed booking. It looks like a bad review three days later, a change order fight, a tech showing up without the right parts. The call was two days ago. Nobody connects them.

Take EV charger installs. A customer calls wanting a Level 2 charger. The person answering hears "EV charger install" and quotes whatever sounds competitive. Truck rolls. Tech gets there and finds a 1972 ranch with a 100-amp service, a Federal Pacific panel, a meter base on the wrong side of the house. The actual scope is a panel upgrade, possibly a service upgrade, a new dedicated circuit. We're now looking at a job three to four times the original number.

The shop writes a change order. The customer feels played — even when they shouldn't, because the original quote was never for this job. The review goes up that night. You know the review.

That's not a scope failure. Nobody lied about the electrical work. Five questions on the first call would have revealed the real scope, and everything downstream wouldn't have paid for it.

The same pattern plays out in panel work and service upgrades — any job where complexity isn't obvious from the customer's description. Bad intake inflates callbacks, kills your NPS, and sends techs into jobs they weren't set up for. The damage is invisible because nobody recorded the call it came from.

---

What a Documented Intake System Actually Looks Like

It's not a new CRM. It's five questions.

For EV charger calls specifically, here's what I built after seeing the pattern enough times: before a truck rolls, the person answering asks the customer the age of their home (pre-1990 is a flag), whether they know their panel amperage (100-amp is a flag), where the panel is relative to the garage, whether they've had any electrical work done recently, and whether they own or rent. Five questions, two minutes, and I know within a reasonable margin whether this is a $1,100 job or a $7,000 job before anyone drives anywhere. Those numbers are from actual jobs in my queue — not a bracket I made up.

If it might be the $7,000 job, I offer a $99 site assessment, credited against the work if they book. Honestly, if someone won't spend $99 to get an accurate quote, the change-order conversation was going to be worse. The customers who book the assessment convert at a high rate and arrive with accurate expectations.

The intake information has to actually reach the dispatcher and then the tech. If it lives in a CSR's mental notes, it dies there. Panel condition, access details, what was promised, what was flagged — all of it goes into the job record, so when the tech opens the job on his phone in the driveway, he's not going in cold.

On hiring: I brought on a part-time bookkeeper first. Then a part-time CSR and dispatcher, about 60 days later, once the books were clean enough to train someone against a real process. Hire before the process exists and you're handing chaos to another person. The process has to come first.

---

Your CRM Isn't the Problem. Your Call Is.

The shops I see struggling with intake are usually evaluating Jobber versus Service Fusion, debating scheduling plug-ins, wondering if they need another tool. They think the software is the system.

It isn't.

For a five-truck residential shop in 2026, the right stack is Jobber or Service Fusion at the core, CallRail for tracking, Zapier for the glue, and QuickBooks Online for accounting. The tools are fine. What they cannot do is ask the customer the right questions, set the right expectations, or catch the scope signals a trained person would catch.

Jobber doesn't make your intake better. It documents your intake faster — which means if your intake is bad, you now have a very efficient record of the bad information.

The same owners who think their marketing is working because the phone is ringing also think their intake is working because someone's answering. They've never pulled a call recording and listened. They don't know what questions are being skipped, what promises are being made off-script, or how many calls die in the first forty seconds because the person answering sounds like they'd rather not be.

I didn't know any of this about my own shop until I started listening to the calls. You can't fix what you haven't heard.

---

The Ninety Days I Spent on the Phone

Month two, NPS of 4. Month nine, NPS of 81. Here's what happened.

I answered every inbound call myself for ninety days. Every one. I took notes by hand on what customers were actually asking, what they were frustrated by before I even quoted them, what expectations they'd arrived with. I wasn't running an experiment. I was trying to understand why customers were unhappy with a business where the electrical work was genuinely good.

What I found: customers were calling with questions I wasn't set up to answer efficiently. They were getting vague booking windows. Callbacks that came late or not at all. Invoices that didn't match what they thought they'd been told. None of it was in the electrical work. All of it was in the intake — specifically, in the fact that I'd never written any of it down.

I built the first version of the intake system during those ninety days. Rough script, five questions per job type, a booking-window policy, a callback policy. Functional before it was pretty.

What I kept — and still run — is a weekly call review. Every Monday, before anything else, I pull four recordings with whoever handles dispatch. Two that booked, two that didn't. We listen. We write down three things that went wrong and one that went right. We don't try to fix everything at once.

That practice is what moved our booking rate. Not a hire, not a software change — listening to our own calls on a fixed cadence and working from what we actually heard. The difference between what you think your intake sounds like and what it actually sounds like is not small. I was surprised every week for the first two months.

---

What You Can Actually Fix by Next Monday

This week: get recording. CallRail runs $50 to $150 a month for a small shop. You assign a tracking number to every inbound channel — Google ads, LSA, the number on your truck wrap, your website. Every call gets recorded and attributed to source. That's it for now. Start collecting. Dollar for dollar it's the most useful software spend I have — and I say that having tried most of what's out there.

Next Monday morning: pull four calls. Two that booked, two that didn't. Listen with whoever handles your dispatch or intake. No scoring sheet yet. Just write down three things that went wrong and one that went right. Twenty minutes. Do it before you open your schedule.

This week, on paper: write the five questions. Not a full script. Just the five things that, if you knew the answers before the truck rolled, would eliminate your worst intake failures. For EV charger calls in my shop: home age, panel amperage, panel-to-garage distance, recent electrical work, own or rent. Your mix is different. Write your version down and put it next to the phone.

Questions first. System second. Hire third. Every shop I've watched try to skip that order ends up with a CSR who's very efficiently doing the wrong things.

---

FAQ

I have one truck and I'm taking all my own calls. Is intake something I need to worry about yet?

Yes — and this is the best time to build the habit. When you're the only one on the phone, you feel the intake problems directly. You know when a call goes sideways. The work right now is paying attention to why and writing it down. If you build a real intake process at one truck, you'll have something worth handing to a CSR when you hire. If you wait until you hire, you'll spend months trying to document something you've been doing on instinct.

What's the difference between an intake problem and a pricing problem?

If customers are saying yes to the price but showing frustration later — at the change order, at the invoice, at the job itself — that's intake. You set expectations on the call and they didn't hold. If customers are hearing the price and ending the call, that might be pricing, but listen to the recordings first. A lot of "price objections" are presentation failures that happen before the number even comes up.

I tried hiring a CSR and it was a disaster. What did I probably do wrong?

Most likely: you hired before the process existed. You handed a new person a vague sense of how things work and expected them to fill in the gaps. When it went wrong, it felt like a hiring problem. It was a documentation problem. A CSR can only follow a process that exists in writing. If yours lived in your head, no amount of good hiring fixes it.

How do I get my CSR to follow a script without sounding robotic?

Don't give them a script. Give them questions. A script tells them what to say word-for-word and sounds canned because it is. A question list tells them what information they need to collect — they use their own voice to get there. Once someone's asked the panel-age question three hundred times, they don't need the card anymore. Start with the card.

Is there a way to measure intake performance without CallRail?

Yes, more manually. Google Voice records calls. You track booking rates in a spreadsheet — calls in, calls booked, revenue booked. Attribution will be incomplete, but the call-review practice still works. The goal is to hear your actual calls on a regular cadence. How you capture them is secondary.

At what point does something else become the bigger constraint?

In my shop, intake was the binding constraint until our booking rate was consistently strong and NPS was stable. Once those held, the constraint shifted to capacity — truck count and tech availability. In conversations with other owners, that's usually how it sequences. Fix the conversion rate first. Spending money on leads while intake is broken just means losing those leads faster.