Your Customer Relationships Die When Your Key Person Does

What Happened When Mike Couldn't Answer the Phone

March 2020. I've owned Whittaker Plumbing & Drain for about sixty days. My dad Mike is in the hospital — went in for a knee replacement, developed a complication, turned into six weeks before he came home. The world is shutting down. I'm running dispatch from a card table in the garage. Hank was two and climbing up my leg and chewing on a pen.

And the calls are dropping.

Not dropping because of the pandemic. Dropping because the phone was getting answered by someone customers didn't recognize. My voice. Not Mike's.

My dad built this shop in 1984. Thirty-six years. One truck to three. Grew it on personality — his personality, specifically. Every loyal customer was loyal to Mike's cell number. Mike's first name. Mike showing up at the door in January when the stack froze and staying until it was fixed. He knew these people. Their dogs' names. Their kids' graduation years. He went to some of their funerals.

None of that was written down anywhere I could find.

---

Loyal Customers Aren't Yours — They're on Loan

Here's what nobody wants to say out loud: a loyal customer isn't really yours.

A customer who calls Whittaker Plumbing — the number, the office, gets Becca or whoever's on the phone — that's a relationship the shop owns. Address in the system. Job history documented. Whoever picks up knows what to say. That customer is sticky to the company.

A customer who calls Mike is something else entirely. That relationship lives inside Mike's phone and Mike's memory. The second Mike isn't available — hospital, bad hip, retirement, whatever — it's gone. You can't see it on a balance sheet. You can't audit a relationship that hasn't gone missing yet. So you call it a loyal customer base and feel good about yourself and you never notice you're holding borrowed money.

My dad mentioned certain names at dinner for years. The Kowalski account. The lady on Edgewater. A property manager named Gerald who had twelve units and called Mike personally on every one. I figured they were ours.

By week three of Mike being in the hospital, Gerald had already called somebody else. Not out of disloyalty. He'd tried twice, got a voice he didn't know, left a voicemail, didn't hear back fast enough. His water heater had gone. He needed a plumber. He found one.

That's it.

---

Eight Weeks That Almost Finished Us

Mike's "Rolodex" wasn't even a Rolodex by 2020. It was a flip phone with four hundred contacts and thirty-six years of showing up in person. Which accounts were seasonal. Which customers paid slow but always paid. Which property managers wanted a call before you went in, not after. All of it was in his head and on that phone.

None of it transferred.

When I started pulling at the thread, I found the same story over and over. Customers told me later: we called and got someone we didn't know, figured you were slammed, so we waited — and then the main backed up and we couldn't wait anymore. Or: we left a message and nobody called back in time, so we went through Angi. Real jobs. Real accounts. Gone in eight weeks because there was nothing to replace the one phone number everyone trusted.

Then Mike came home. Got his phone back. And some of it came back too. A few calls returned. A few accounts reactivated.

That was the scariest part of the whole thing.

Because it meant the problem was still personal. His return papered over something that needed to be structural. We'd gotten lucky, and I knew it, and I wasn't sure I'd get lucky again.

---

What It Means for the Business to Own the Relationship

Becca works the office two days a week. What those two days actually do — what they've done since we got serious about it in late 2020 — is keep the customer relationship alive inside the business, not inside a technician's phone.

When Dom goes out on a job, the notes come back through Jobber. When a customer calls in, whoever picks up can pull the address, see every job we've done there, every note, every callback. The customer isn't calling Dom. They're calling Whittaker Plumbing, and Whittaker Plumbing knows who they are.

The Nextdoor piece matters here too — especially in Parma. This is a neighborhood market. People ask for plumber recommendations on Nextdoor the way they used to ask the guy at the hardware store. If five neighbors know Dom's name and face and his cell number, and Dom leaves, those recommendations leave with him. If they know Whittaker, and they've talked to Becca, and they got a follow-up call after the job — the business name is the thing that travels.

That's what you're actually building toward. Not the face. The name behind the face.

---

The Tech Guy Problem

This isn't only a succession problem. It replicates at every level of the shop, and I can prove it because it's happening to me right now.

Dom is two years out of his apprenticeship. Customers like him. A few have started asking for him by name, which I understand — last fall he diagnosed a slow drain on Broadview that three other shops had snaked twice without fixing. He found a partial root intrusion about forty feet in that the camera barely caught. Guy like that earns a reputation. I'm glad he works for me.

But here's what I'm watching. Certain customers are starting to call Dom's cell instead of the office. His intentions are fine. The problem is structural. The moment that happens, the job notes stop coming back through Jobber. The follow-up doesn't route through Becca. The customer is building a relationship with Dom, not with the shop — and if Dom leaves, or gets hurt, or has a bad week, those customers have no anchor.

Dom doesn't document well because I haven't made him. I'm in a truck two days a week when I should be in the office. That means I'm not watching the training. The habits Dom needs to build aren't getting reinforced because I'm not there to reinforce them, and I keep saying I'll fix it when things slow down. They don't slow down. Guys like Dom aren't worse than apprentices were in 2005. They're trained worse. By guys like me who say they'll fix it later.

I know what later can look like.

---

What to Do With This

Here's what I'd do if I were starting this from scratch Monday.

Pull every customer record from the last two years. Go through them and count how many have no job notes. No contact history. Nothing beyond an invoice and a paid stamp. That count is the size of your problem — not customers you already lost, but customers you still have who haven't actually been captured by the business yet. If your key person disappeared tomorrow, those are the ones who'd go with them. Write the number down. It's not going to feel good.

Then pick up the phone. Actual phone call, from the office — from Becca, from your CSR, from whoever answers your phones — to your top twenty accounts. Not to sell anything. Just to check in. Hey, we serviced your water heater last spring, wanted to make sure everything was running right, and if you ever need us, here's the number. That call introduces the business as the relationship. It gives you a reason to log the conversation somewhere that survives the next time a key person goes missing.

Mike's flip phone can't be the customer record. It wasn't even a good one when it was working.

---

The customer isn't calling to reach a company. They're calling because they trusted someone. Your job is to make sure the company is what they trusted, and they just didn't know it yet. Most shops never do that work. Then someone leaves and they find out what they actually had.

---

FAQ

If my best tech has been with us fifteen years and customers love him, do I actually have a problem?

The longer he's been there, the bigger the problem. Fifteen years means fifteen years of customers associating a face with the service. When he retires or gets hurt, you're not just losing a tech — you're losing whatever portion of your repeat base doesn't know who to call next. Don't make him less likeable. Make sure every job he touches is documented and followed up through the office, so when someone calls in asking for him, whoever picks up already sounds like they know the customer.

What do I put in a customer record that makes it useful?

More than you think you need. Job history, yes. Also: what work's been done, any quirks about the house, how they like to be reached, whether they're older and want extra lead time, who referred them. Anything that lets someone new pick up the phone and not sound like a stranger. I tell my guys: if I handed this record to someone on their first day, could they make this customer feel known? If the answer is no, the record isn't done.

My dad is still technically involved — how do I move his relationships without blowing it up?

You don't cut him out. You build a backup alongside him. Have the office follow up on jobs he handles, so customers start hearing from the shop, not just from him. When he introduces a customer to you or another tech, he frames it — "this is who handles it going forward." Warm transfer over time, not a hard cutoff. The friction only comes if it feels sudden or hidden.

How do I know how much of my customer base is actually at risk?

Look at your repeat customers from the last two years and ask two questions. First: do they call the office number, or do they call a cell directly? Second: do they have real job records in the system, or does most of what we know about them live in someone's head? The more of the second answers, the more at risk you are. You won't get a clean number. But you'll know if it's a small problem or a large one.

A customer says they only want one specific person on my crew. What do I do?

You honor it when you can and manage it when you can't. Don't fight the preference — it means a good experience happened, which is your success. When that tech isn't available, whoever goes out leads with what they know: "Dom told me about the work on your main line, I've got the full notes here." The customer needs to feel like the knowledge transferred. Most of the time, if the work is good, they'll accept the new person.

We've been on Jobber for two years. Isn't this handled?

Jobber doesn't do this for you. The software is where you put the information — it doesn't decide what matters, it doesn't make your techs write notes, and it doesn't call your customers. Becca figured out Jobber in about a month. The part that took longer was getting me and Dom to close the loop on every job, every time. Software is the bucket. You still have to fill it.