Stop Dropping Everything for Your Best Customers

Stan Kowalski called on a Wednesday at 10:47 a.m. Burst pipe in the basement, water coming up through the floor drain. The guy's been with Whittaker Plumbing since my dad's time — calls twice a year, always pays same day, never haggles. When I saw his name on my phone I told Dom to wrap up what he was doing and head to Broadview.

That felt like loyalty. It wasn't. I'll get to what it actually was in a minute.

---

The Drop-Everything Instinct and Where It Comes From

Here's the thing about the drop-everything instinct. It feels like love for your best customers. In a one-man operation with a Rolodex and a kitchen phone, honestly, it kind of is. That's exactly how my dad ran this shop from 1984 to 2019. Mike Whittaker knew every customer by name, knew the wives' names, knew the dog's name. Somebody called in a panic and Mike showed up. That was the whole system. And it worked — because Mike was the system.

Then in March 2020, Mike's phone stopped getting answered. He was in the hospital — a knee replacement that turned into a six-week complication — and I was running dispatch from a card table in the garage with Hank climbing on me. Hank was two. The shop was three trucks and I was trying to figure out who was where and what was promised and what parts Dom needed Thursday morning. None of it was written down anywhere. It lived in Mike's head and in Mike's phone.

The shop almost died in eight weeks. Not because we had bad customers. Because "drop everything" works for one guy. One guy who never goes down.

That's what no system looks like under pressure — a card table, a two-year-old, and a phone full of customers expecting the person who always picked up. And that person wasn't there.

---

You're Not Being Loyal. You're Being Loud.

Let me name the thing directly. Dropping everything for your best customers feels good to you. The customer just knows someone came fast, which is nice, but it's not what built the relationship. And it blows up the board for everybody else that day.

I've said this a hundred times: a good CSR is worth two trucks. I mean that literally. Becca works the office two days a week — other three she's teaching preschool — and those two days outperformed my fifth truck. Not because she's magic. Because she's a system. She knows who's on the board, what's promised, what the real emergencies are. Real loyalty to a customer lives in the dispatch board and the person running it. Not in me personally sprinting out of whatever I'm doing.

The customer you bumped to get to your best customer? That's somebody's mom too. My whole training program is four words: treat the call like your mom called. Your schedule doesn't change that.

When I pulled Dom off that Wednesday to get to Stan Kowalski's burst pipe, Dom was mid-job on a slow drain call on Denison. Lady had been waiting since 9 a.m. She waited four more hours. She left a two-star Google review. Google reviews matter more than people think — more than Yelp, more than anything except Nextdoor in a neighborhood like mine. That two-star review is still sitting there. Stan never knew any of it happened.

---

What the Wednesday Actually Cost

Dom leaves the Denison job at 10:52. Gets to Broadview at 11:15, finds the burst, shuts the water, assesses the repair. Done by 1:30. Solid job, good work, Stan pays same day like he always does.

Meanwhile, the Denison lady sits waiting. No call, shifted ETA when she finally called back in, didn't see a truck until after 2 p.m. She was gracious on the phone. She was not gracious on Google.

Two stars. "Showed up hours late with no communication. The drain works now but I don't trust them." Based on what I can track, fourteen people have seen that review in the last year. How many didn't call because of it? I don't know. That's the part that keeps me up.

The actual cost of the hero run to Broadview wasn't the two hours Dom was over there. It was the four hours the Denison lady sat waiting, whatever she told her neighbors, and the review that's still there. Stan's a great customer. He wasn't worth that trade. He didn't ask me to make it. I made it without thinking, because his name pulled me out of the system and into a panic response.

Stan would've waited two hours. He's been with Whittaker Plumbing for thirty years. He's not who bolts. What Stan actually needed was a straight answer and a real ETA. He needed the shop to function. Not a hero.

---

What Your Best Customers Actually Want

Your best customers called because they trust the shop. They're not panicking because they expect you personally to materialize in twelve minutes. They're panicking because a pipe burst and water is coming up through the floor drain. What stops the panic is a calm voice on the phone, a real time, and a guy showing up when he said he would. That's the product. That's what "those guys always come through" actually means.

The people in Parma who've been with us since my dad's time — they're the ones who send us work. Not because they'll write a testimonial. But because someone on their street asks who does their plumbing and they say "Whittaker, been using them since Mike was running it, they always come through." That story gets told because of reliability over ten years. Not because Joe personally showed up in fifteen minutes one time in a panic.

What Stan actually wants is Dom there in two hours with the right parts and a straight answer. The frenzy I bring when I drop everything doesn't add to that. Mostly it just makes me feel better.

---

Build the Process That Serves Them Better Than You Can

First thing: your CSR needs actual language. Not general guidance — words. Specific sentences. The one that works in our shop is: "I'm going to get you on the schedule today and Dom will call you thirty minutes before he heads your way." That's it. Becca didn't have that written down until I made myself write it down, maybe a year and a half in. Before that she was winging it every time, and when you wing it every time, you get different answers, and different answers train customers that pushing sometimes works.

Second thing: a priority flag in the dispatch board. We tag customers who've been with us more than five years. We tag genuine emergencies separately — active water, no heat in January, sewage backup, no hot water in a house with little ones or an old lady living alone. Those tags give Becca something to look at when she's figuring out who goes where. She doesn't have to call me every time a longtime customer panics. The board tells her what to do.

Third thing, and this is the one nobody wants to hear: stop handing out your personal cell number. I did it for years. Felt like VIP treatment. What it actually did was train a handful of customers to go around the board entirely and call a guy who's under a sink in Parma Heights and can't think straight. A flag in the system gets them better service than my cell number does.

The difference between what we run now and what my dad ran on personality is that ours is written down. Not colder — documented. A named triage process isn't a way of caring less about your longtime customers. It's what keeps the shop alive when you're sitting at a card table in a garage and can't personally call everyone back. Mike's system was great until Mike couldn't run it. Mine has to work when I'm not in the room.

---

What You Do Monday Morning

One: write down the five names. The customers you'd currently drop everything for. Put them on paper. Then ask — did any of them actually ask you to jump the line for them? Or did you do it twice and now you're stuck with it? Figure out which ones are real emergencies and which ones are just habits you fell into.

Two: give your CSR the sentence. Write it down, tape it to the monitor. "I'm going to get you on the schedule today and [your tech] will call you thirty minutes before." Becca runs the office two days a week and runs it well, but she runs it well because the words exist on paper now. If your CSR has to invent the answer every time a panicked longtime customer calls, you're going to get twelve different answers and twelve different expectations.

Three: put the flag in the dispatch board. Add a tag for your priority customers. Not so they automatically jump the line — so the person running the board has something to look at when they're figuring out the day. The decision shouldn't live in your head. If it does, the shop can't move without you. March 2020 already taught me that. I got it.

---

FAQ

My best customer has my personal cell number and texts me directly — how do I walk that back without torching the relationship?

Don't take the number away. Just stop answering in real time. Respond a few hours later: "Got this — had Becca get you on the schedule, Dom will call before he heads over." Do that three or four times and you've changed the habit without a conversation. They still feel taken care of. The answer's just coming from the shop now instead of from your hip pocket while you're under someone else's sink.

How do I know if a call is actually an emergency or if they just think it is?

Active water. No heat in January. Sewage backup. No hot water in a house with little ones or an old lady living alone. Those are emergencies. "The drain is slow and I have company Saturday" is not — even if the customer's panicking. Train your CSR on the four or five real categories and let them make the call. If it doesn't fit, it's not an emergency. It's an urgent job. Urgent jobs can go same-day without blowing up the board.

What do I tell the customer I had to bump when a real emergency came in?

Call them before they're waiting. That's it. If Dom's getting pulled, Becca calls the bumped customer before Dom leaves the driveway. "We had an emergency come in, need to move your window — here's your new time, Dom will call you thirty minutes out." Most people are fine with that. What they're not fine with is sitting there wondering. The bump itself isn't what costs you. Leaving them in the dark during the bump is what costs you.

Isn't there a case for dropping everything — like a customer who sends real volume?

Yeah. A property manager with a building full of units who's keeping us busy all year gets different treatment than a once-a-decade homeowner. But different treatment should mean a standing same-day slot, not me dropping a mid-job to sprint across town. They should be tagged in the system so Becca knows to find same-day without calling me. If the relationship requires me to personally jump every time they call, that's not a good account — that's a situation I created by saying yes too many times.

How do I build a priority tier without every customer deciding they're the priority?

History. Consistent payment. Multiple jobs over multiple years. You don't have to tell anyone they're not priority. You just tell them "I'm going to get you on the schedule today." That sentence works for everyone. The flag just means Becca looks harder at the board to make same-day happen. The customer never sees the flag. They see results.

My guys expect me to make the call on who jumps the line — how do I get that out of my head?

Write down what an emergency is and what a priority customer is. Give it to your CSR. Something like: "Active water, sewage backup, or no heat November through March — emergency, find same-day. Customer with us five-plus years — priority, same-day if the board allows, first morning slot if not." Print it out. The first few weeks your guys will still call you. You say "what does the board say?" They stop calling. The answer's on the paper, not in your head — which is good, because your head isn't always available, and the shop has to run anyway.