Answer Your Own Phones for 90 Days — Then Fix Everything

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

Not 40. Not 14. A four. I'd spent four months before launch building what I thought was a real operation — pricing model, software stack, branded vans. I had a plan for everything. What I had not planned for was being, personally, the person responsible when a customer called at 9:30pm about a breaker that kept tripping and got a bad experience on the other end of the line.

I thought the intake was handled. The score said otherwise.

So I went back to the phones for ninety days. Answered every call myself, took notes after every one, rebuilt the process from what those calls actually taught me. By month nine, NPS was 81.

---

The Problem With Running Your Business From the Whiteboard

Here's something I've seen in my own shop and heard from guys I've talked to: once you delegate intake, your intuition about it stops updating. You see reports. You listen to a recording here and there. Your dispatcher tells you why a customer was upset. You feel like you have a handle on it.

You have a handle on the summary. That's different.

When I was at Lonestar running service jobs at scale, I knew the metrics. I did not know what it felt like to be the customer at 9:30 on a Tuesday night. Those are not the same knowledge and treating them as equivalent is where revenue goes.

On gut instinct: your gut after 4,000 service calls is earned. Your gut after 80 is a guess. Most owners who've delegated intake for years are running on older signal than they think. Stepping away was the right call. The cost is that the market kept moving and your read on the intake conversation didn't.

---

What 90 Days on the Phone Actually Teaches You

Week one: you realize you've gotten rusty at this. Week six: you're seeing the same friction points cycle back. By week ten, you know things about your own business that you cannot get any other way.

Specifically — you know which channel produces callers who are ready to book and which produces callers who are pricing three shops at once. You know which job type generates the most friction in the quote conversation. You know what a nervous caller sounds like thirty seconds in, and what they need before they'll commit.

The EV charger install market is a good example. There's a national franchise running $599 install ads, and that number is sitting in the head of most callers who want a Level 2 charger. The actual scope on a 1972 ranch with a 100-amp Federal Pacific panel and a meter base on the wrong side of the house is a different number — by a lot. The gap between what the customer expects and what the job actually costs is where the conversation goes wrong.

I didn't fully understand how bad that misalignment was until I'd personally fielded forty versions of that call. Not listened to forty recordings. Fielded them. Heard the exact moment the customer's voice changed. Heard what I said that helped and what made it worse. You cannot get that from a transcript.

I run CallRail tracking numbers on every channel. I can pull booking rate, average call duration, revenue closed by source. That data only becomes legible when you have real intuition about what the caller from each channel actually sounds like. Ninety days on the phone is what builds that.

---

The Contrarian Position: Call Recording Alone Won't Cut It

I will not stop recommending call recording. Every call recorded, sampled weekly, four calls reviewed with my dispatcher — two that booked, two that didn't — tagged for what worked and what didn't. That practice doubled our booking rate in 2023. CallRail runs me about $90 a month and it's my highest-value software spend, full stop.

And it's still not the same as picking up the phone yourself.

Call recording tells you what happened. Answering calls yourself for ninety days tells you why — and what to do in the first thirty seconds when it starts going wrong.

Recording review is retrospective. Game film. Valuable. What it cannot give you is the live experience of a caller's emotional state shifting in real time — the question they almost ask but don't, the pause before they hang up.

From what I've seen in my shop: most small-shop revenue leakage happens in the first call. Not in the quote. Not in the close. The first call. Recording surfaces the symptom — short call duration, low booking rate, the caller who said "I'll think about it." Answering yourself surfaces the cause.

There's a layer of reality below the recording that only shows up when you're in it.

---

What I Found When I Picked Up the Phone

When my NPS hit a 4, I didn't pay someone to tell me what was wrong. I went back to the phone and answered every call for ninety days. Took notes after every single one.

What I found: I hadn't designed an intake process. I'd assumed one. There's a difference.

I had a CRM. I had a call script taped to the dispatcher's monitor. What I hadn't done was verify the script matched the reality of the calls — and it didn't. The script was written for a customer who knew what they needed and was ready to book. Most actual calls were people who were scared about a safety issue or had already called another shop and been burned.

The 9:30pm breaker call made it undeniable. The customer wasn't angry at the start. They were anxious — intermittent trips, didn't know if it was dangerous. What they needed in the first thirty seconds was someone to tell them they'd called the right place and this was going to get handled. What they'd been getting was a booking flow that treated them like a scheduling unit.

I couldn't have written a script that addressed that without living the call. Every new line in the rebuilt intake process traces back to a specific call that went wrong in a specific way. The rebuilt process isn't theoretical.

NPS hit 81 by month nine. Answering the phones wasn't the only reason — hiring, dispatch, invoicing, all of it improved. But none of that would have been built correctly without the raw material the calls gave me. You can't fix what you haven't diagnosed.

---

When You Hand the Phones Back — and What to Do Differently

This is not a case for answering your phones indefinitely. You have five trucks. You have bids to write. The case is for doing it long enough to build the intake system your business actually needs, then handing off to someone who can execute it correctly.

My sequencing: hire the bookkeeper first, the CSR second. Don't do them at the same week — I tried that, it was a mess. The bookkeeper workflow is discrete. You can train someone on QuickBooks Online and invoicing with relatively clean instructions. The CSR is harder, because you can only train them correctly once you know what a good call sounds like. You only know that after you've lived it.

What makes the handoff work is the library you built. Before you start the ninety days, get CallRail on your primary inbound line. Every call you answer gets recorded from day one. You're running the diagnostic and building the recordings you'll actually use to train your CSR simultaneously. When you hire them, you're not handing over a script written in the abstract — you're handing over sixty hours of real calls, tagged, annotated, with a script derived from what you actually heard.

After the handoff, weekly call review keeps the system honest. Four calls a week, two that booked, two that didn't. You and your CSR, same room or shared doc, tagging what worked. The ninety days gets you there. The weekly review keeps you there.

---

What You Do Monday Morning

Day one: Get CallRail on your primary inbound line. Roughly $90 a month. Run it before you start answering, because the recordings are the whole point — you're building the training library at the same time you're doing the diagnostic.

Day two: Build a simple intake notes doc. I use a running Airtable; a Google Sheet does the same job. Columns: source, what they called about, what they expected to pay, what you quoted, whether they booked, one thing that surprised you. Ninety seconds of logging after every call. At ninety days you have a real dataset.

Day three: Tell your dispatcher what you're doing and why. You're not going back to the phones because they're failing. You're going back because you personally haven't heard enough of your own calls to make good decisions about the intake system. That's true. Say that.

Days four and five: Answer the calls. Log the notes. Every call that goes sideways in a way you didn't expect is a system gap you didn't know existed. Those surprises are what you came for.

---

FAQ

I've been in business eight years. My dispatcher knows our customers better than I do at this point. Why would I go back to the phones?

Your dispatcher knows your current customers. You need to know the ones calling now who aren't booking. Eight years of delegation means your intake read is calibrated to the market as it was, not as it is. Pricing expectations, competitive context, caller profiles — all of it shifts. Your dispatcher adapts gradually without necessarily flagging it. You'll likely find they're doing some things brilliantly and some things that made sense in year two and haven't been revisited since.

What if answering calls pulls me off jobs and I lose revenue during the ninety days?

It will pull you off some jobs. The honest answer is: do it anyway. In my experience, shops that have never run this experiment consistently underestimate intake leakage. They think the problem is in the quote or the close. It's usually in the first ninety seconds. If you're genuinely field-constrained, start with a thirty-day stretch on calls you can cover without missing installs — mornings before you roll, or after the trucks are back.

Can I shortcut this with a mystery shopper audit or a consultant?

A mystery shopper gives you two to five data points. A consultant gives you a framework built on what they've seen at other shops. Neither gives you the volume of first-person exposure you need to actually redesign your intake. The problem with secondhand information is that it describes what happened without building your judgment for when a call goes off-script. You build that by being on the call.

My CSR is good. Can't I just retrain her instead of picking up the phone myself?

You can retrain her on a script. The problem is whether the script is right. Most owner-written intake scripts are built on assumptions — what the owner thinks customers ask, what the owner thinks the friction points are. Those are usually wrong in specific ways that only become visible when you're in the conversation yourself. Retraining a good CSR on a bad script produces a good CSR executing a bad script. Do the ninety days first. Write the script from the data. Then retrain.

How do I handle the handoff without call quality degrading?

Don't make it a hard cutover. Start with your CSR covering specific windows while you stay available — mornings, say — before she's carrying the full load. The recorded library you built is the primary training tool; she's hearing what a good call sounds like, not just reading your description of it. And keep the weekly review in place permanently. Four calls a week, tagged together. That's what prevents the slow drift back.