Your Intake Process Is Losing You Jobs (Not Your Reviews)

The First 90 Seconds Is Where Your Revenue Goes

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

I'd built relationships during my Lonestar years. I had referrals lined up. The marketing was fine. The problem was that every call after 5pm, every call Priya picked up because I was under a panel, every call that went to voicemail and got a callback the next morning — those calls were dying. Customers hung up uncertain. They didn't book, and they didn't leave a review explaining why. They just disappeared.

The biggest unspoken difference between shops that scale and shops that don't is intake. I've said it before and I'll keep saying it because I watch shop owners ignore it every year. Most are fumbling it badly without knowing it — because they don't record their calls and they've never actually listened back.

That's not a judgment. It's a design flaw. You cannot audit a process you cannot hear.

---

What's Actually Happening on Your Phones Right Now

Here's what a broken intake process looks like from the inside. Owner answers when available. Employee or spouse picks up when they can't. No script. No written callback window. No protocol for calls that come in mid-job. The booking decision is whoever picked up doing their best and hoping the customer tries again.

In the first three months of Reeves Electric, I answered every call myself. Not because I wanted to be the hero on the phones. I was already running five jobs a week, invoicing at night, and learning QuickBooks Online at 10pm. I did it because you can't hand off a process you haven't documented, and you can't document a process you haven't watched yourself.

So I logged every call on a legal pad. What did they ask first? What did I say? Did they book — and if not, where did the conversation go quiet?

What I found wasn't rude staff or wrong pricing. It was ambiguity. Callers ended the conversation not knowing what came next, what it would cost, or whether we were even the right shop. Customers don't say "I'm uncertain." They say "let me think about it" and call the next shop on the list.

Most owners think their booking rate is higher than it is because they're measuring the wrong denominator. They count jobs that booked. They don't count the calls that didn't. If you don't have recorded calls and source attribution, you're guessing. The owner who tells me "we close most of our calls" almost never knows what most actually means.

---

More Leads Won't Fix a Broken Intake Process

When shops come to me with a booking problem, the instinct is always to buy more leads. Run more ads. Chase more reviews. More input, more output.

That's the wrong diagnosis.

If your intake is leaking, pouring more calls into it doesn't fix anything — it makes the leak more expensive. You're paying more per lead to achieve the same broken result.

Google LSA is where I see this most clearly. LSA works. I run it, I'll keep running it. But those leads close at a lower rate than organic or referral because the customer is actively shopping. They called three shops. They're going to book whoever earns their confidence fastest. If your intake stalls on price questions, fumbles the scope conversation, or leaves someone waiting 18 hours for a callback, LSA spend is actively working against you.

The real number to fix before you increase your ad spend isn't your cost per lead. It's your booking rate per call, broken out by source. You can't know that number without recorded calls.

CallRail is how you get there. You assign tracking numbers to every channel — LSA, your website, your truck wrap — and every call gets recorded and attributed to its source. Runs $50 to $150 a month for a small shop. In my shop, the booking rate on LSA calls runs about 23 points lower than on organic. That number tells me exactly how much I can afford to pay per LSA lead before I'm underwater. Without it, I'd be guessing like everyone else.

Fix the intake process first. Then scale the lead volume.

---

What a Repeatable Intake System Actually Looks Like

A working intake process has four parts: a qualifying script, a callback window, a dispatch handoff, and a booking confirmation. All four have to be written down and trained on. The minute any of them lives only in someone's head, you've got a single point of failure.

The qualifying script isn't a telemarketer read-through. It's five questions:

1. What's the issue or the work you need done?
2. What's the age of your home — do you know if it's been rewired since original construction?
3. Do you know your panel size — 100-amp, 150, 200?
4. Where's the panel relative to where the work needs to happen?
5. Has anyone looked at this before, or is this the first call?

I built those out of the EV charger work specifically. The gap between "easy Level 2 install" and "full service upgrade" was blowing up jobs at the site — customer had seen a $599 franchise ad, actual scope was $6,400, nobody had asked the right questions on the front end. The intake call isn't just getting an appointment on the calendar. It's qualifying the scope so the tech shows up with the right parts, the right time block, and no surprises. An underprepared tech on a job twice the expected scope costs you the review before anything gets touched.

The callback window is simple: missed call gets a callback within 25 minutes during business hours. After-hours calls get an automated text — not a voicemail — acknowledging receipt and giving a morning window. CallRail or your CRM can trigger that automatically.

The dispatch handoff is where small shops lose most of what the intake call captured. The CSR books the job and the tech shows up with an address and a time slot, no qualifying notes. Everything from the intake conversation has to transfer to the job ticket. Jobber handles this cleanly if you build the intake fields into the job creation flow. Service Fusion does too.

Booking confirmation closes the loop: text when booked, reminder the day before, two-hour arrival window the morning of. In my shop, that sequence cut confirmation callback volume by about half. Customers call to confirm when they're unsure. Stop giving them a reason to be unsure.

Run this inside your software stack — CallRail for attribution and recording, Jobber or Service Fusion for workflow. Running it off a personal cell and a notepad is exactly why it collapses the moment you're not holding the phone yourself.

---

Month Two, NPS of 4, and What Actually Changed

By the end of month two, I had a bad number and I had data. The NPS of 4 came from six reviews — small sample, directionally accurate. The pattern in the comments wasn't "the work was bad." It was "hard to reach," "wasn't sure what was happening," "felt like I had to follow up myself."

Those aren't quality complaints. Those are process complaints.

The ninety days on every call were not comfortable. I didn't think I was learning anything new. I already knew how to talk to customers. What I was actually learning was the gap between what I assumed a caller wanted — a price, a date, a yes — and what they needed in the first 90 seconds to feel confident booking.

They needed a specific next step with a time attached. Not "we'll get someone out to you." Something like: "I'm going to get you on for Thursday between 10 and noon, and you'll get a confirmation text in the next 15 minutes. If the scope is more involved than what we've talked about, your tech will walk you through it on site before any work starts." That sentence. That level of specificity.

I wrote down the language that booked jobs. I wrote down the exact moments in lost calls where the customer went quiet. Those notes became a script. The script became training. By month nine, NPS was 81.

The reviews didn't change because I ran better ads. They changed because customers stopped feeling uncertain.

---

What to Do Monday Morning

Start here. Three moves, this week.

Step one: get CallRail set up before Friday. Assign a tracking number to every active marketing channel — LSA, your website, your truck wrap. The plan runs $50 to $150 a month. That's the prerequisite for everything else, because you cannot fix what you cannot hear.

Step two: listen to four calls this week. Two that booked, two that didn't. Sit down with whoever answers your phones and find the specific moment in each lost call where the customer's confidence dropped. Price question? Availability fumble? "Let me check and call you back"? Write those moments down. That list is your script draft — you're not inventing a process from scratch, you're finding what's already breaking and building the fix around the actual failure points.

Step three: calculate your booking rate and review it weekly. In my shop, anything below 65% on residential service requests — meaning calls where someone described a real problem and asked about availability or pricing — means something in intake is broken. If you're below that, you have a process problem. If you don't know your number yet, pull inbound call volume from CallRail or your carrier for the last 30 days, match it against booked jobs, and do the math. Review it every week the same way you review revenue. If both numbers drop together, you know where to look first.

The leads aren't the problem. The first 90 seconds are the problem. Your ad spend, your review count, your hiring pipeline — none of that is fixable this week. The intake process is.

---

FAQ

My booking rate seems fine — customers who call us mostly book. How do I know if I actually have an intake problem?

"Mostly" is doing a lot of work in that sentence. The question is what your denominator is. If you're only counting calls that turned into real conversations, you're probably missing the after-hours voicemails that never got a callback, the calls that dropped during hold, and the ones that ended with "let me think about it." Pull your actual inbound call volume from CallRail or your carrier for a month and match it against booked jobs. If you don't have that data, you don't know if it's fine. You think it's fine.

I'm still the one answering most calls. When does handing intake off to a CSR actually make things better instead of worse?

When you have a written script and a documented process to hand off — not before. Handing someone a phone without training gets you a worse result than the owner doing it imperfectly. Spend time on the calls yourself, take notes, write down what works. Build the script from that. Then hire the CSR and train them against it. The script is what makes the handoff work. Without it, you're hoping they're naturally good on the phone.

What does a call script actually look like for a residential electrical shop — isn't every call too different to script?

The variation happens in the middle, not at the open and not at the close. The first 60 seconds and the last 60 seconds are nearly identical on every call that books — your name and company, a question that starts the qualifying conversation, and a close that gives the customer a specific next step with a time attached to it. The five questions above work across most residential service categories. Script those anchors, let the middle flex. You're not scripting a monologue, you're scripting the transitions.

We're using Jobber and it has a built-in booking form. Is that the same as having a real intake process?

No. The booking form is data capture. An intake process is the qualifying conversation, the scope confirmation, the callback window, and the tech handoff. Jobber handles scheduling and job management well, but if someone fills out the online form and nobody calls within 25 minutes to confirm scope and timing, the form didn't do the work. Use Jobber for what it does well and don't confuse the software with the system.

How do I calculate my actual booking rate when some calls are tire-kickers and some are real jobs?

I count any call where the customer described a specific problem or asked about availability or pricing. Someone calling to ask if we do commercial — we don't — doesn't count. Someone asking about panel upgrades and wanting to know our availability counts, even if they never mentioned a timeline. The bar is: did they want to explore hiring us for something? If yes, that's the denominator. Every one of those calls that doesn't become a booked job is worth understanding.

I've listened to some of our calls and they're not great. How do I coach someone on phone skills without it turning into a whole HR situation?

Start with the call, not the person. Pull up the recording together and find the moment where the customer went uncertain. Ask what they'd do differently. Run it weekly with two or three calls at a time — not as a surprise audit, but as a standing practice. When it's routine, the defensiveness drops. You're building shared language around what a good call sounds like. That's a different conversation than telling someone they're bad at their job.