Customers Always First: Running Operations Around the Live Phone Call

Short answer: Customer escalations in home services rarely come from the repair itself. They come from communication: a call nobody picked up, a callback that never came, bad news sent by text with no options. The customer gets passed around, repeats the story, and gets angrier at every step. "Customers always first" fixes this only when it becomes an operating rule: named people answer existing customers live, the call center is the reception and the safety net, meetings give way to ringing phones, bad news goes out by voice, and software takes the keyboard work so people have time to talk.

Most customer escalations in home services do not start with a bad repair. They start with a call nobody picked up, a callback that never came, or bad news sent by text with no options. I was reminded of this recently when I asked a simple question: when a customer who already trusts us calls right now, who actually picks up? The answer told me our values and our phone path were not the same thing.

Every company in our industry says the customer comes first. It is on the website. It is on the wall. It is in the values. One of ours, Customer Obsession, says it plainly: "It starts and ends with the customer."

Saying it is easy. Running a company around it is a different thing. My job is not to answer every call myself. It is to design a company where the right person answers, every time. Here is the framework I use for the question I get from owners all the time: why do customer escalations keep happening?

Where values meet the phone

A value lives or dies in an ordinary moment: a customer who already trusts you picks up the phone and calls.

Think about it from that customer's side. They already said yes to a relationship with you. They call, and the phone rings, and rings, and rings. Then a different person answers, somebody who does not know them, does not know their history, and has to start from zero. That is how you turn a loyal customer into an escalation.

A call center is a reception. Reception matters. It greets new customers, books the first visit and makes sure nobody hears silence. But once a customer is inside a longer relationship with you, they should be talking to the people who own that relationship, not to the front desk.

Keyboards versus voices

In service businesses it is easy to hide behind a keyboard. People type. They text. They update fields. They send messages. What they do not do enough is pick up the phone and talk to the customer. When I look at escalations, that is where most of them come from.

A common example: an appointment cancelled with a text message and nothing else. No new time. No partner offered. No help with rescheduling. Just "your appointment is cancelled." The customer is left alone with the problem. Of course they get frustrated. Of course some of them escalate.

Nobody does that to be rude. A text is fast. It feels done. You can send ten of them in the time one phone call takes. That is exactly why keyboards are so attractive, and exactly why they are dangerous in a service business.

A text tells the customer what happened. A call solves what happens next.

That mentality has to hold in every business unit, not in one team. The phone is not a distraction from the work. In our business, the phone is the work.

Why do customer escalations happen in home services?

When I look at the escalations that reach me, they almost never start with the original problem. A furnace fails, a dryer stops, a breaker trips. Customers understand that things break. That is why they called us.

What they do not forgive is what happens after. Here are the patterns I see again and again.

1. Nobody answers. The customer calls and hears ringing, voicemail or a long hold. The first impression is that nobody is home.

2. The callback does not come. Someone says "we will call you back." Then nobody does. Now the customer is not upset about the repair. They are upset about being ignored.

3. Bad news arrives by text. A cancellation, a delay, a missing part, a price change. Delivered in two lines with no options. The customer has to do all the work of fixing our problem.

4. The handoff. The customer gets passed from the person they know to a person they do not. They repeat the whole story. Every retelling raises the temperature.

5. Nobody owns the customer. The call center thinks dispatch owns it. Dispatch thinks the business unit owns it. The technician thinks the office owns it. When everyone owns the customer, nobody does.

6. A promise gets lost between people. Something was agreed on one call and never made it to the next person. The customer remembers. The company does not.

Look at that list. Almost every item is a communication failure, not a technical one. And almost every item gets worse when people choose the keyboard over the voice.

That is the honest answer to the question. Escalations happen when customers stop feeling that a real person owns their problem.

The live phone call as the center of operations

So what does it mean to run operations around the live phone call? It means you design the company backwards from one moment: a customer is calling right now. Who picks up, how fast, and do they know who this person is?

Most companies design the other way. They build the org chart, the meetings, the reports and the software, and then they fit the phone into whatever time is left. The phone becomes an interruption.

When you flip it, the questions change.

Not "is everyone busy?" but "is someone free to answer?"

Not "did we send a message?" but "did we talk to the customer?"

Not "which department owns this ticket?" but "which person owns this customer?"

This is not new for me. When I started in 2008, I gave my personal number to customers. It was on yard signs and on Google. I had no CRM, only a notebook. I lost clients I never even knew about, because when I missed a call, there was no system behind me. I wrote about that in why most contractors overpay for phones.

A few years later I learned the opposite lesson. When I went away for a month in 2012, half my clients left. They were loyal to me and to the deal, not to the company. I rebuilt everything so clients called the company, not me. I wrote that story in customers go where it's cheaper.

The question I asked recently was the same lesson from a new angle. Our members are customers who have already chosen a longer relationship with us, and we have a membership team for them. These are the people who take care of our members, and they are the voice a member should hear. The relationship has to live in the company. But inside the company, it still has to live with specific people who pick up when the customer calls. A system that answers is not enough. The right person has to answer.

My framework: customers always first, as an operating rule

Here is the framework I use. It is written for owners in the $1 to $5 million range, where you probably have a small office, maybe an answering service or a small call center, and a team that does a bit of everything.

1. Decide who owns each type of customer

Split your callers into two groups. New customers who have never worked with you. Existing customers, members and anyone with an open job.

New callers can go to reception: your office, a call center, an answering service. Existing customers should reach a named person or a small named team who knows them. Write it down. If you cannot say who owns a member's call, nobody does.

2. Make the ring path short and specific

Map what happens, ring by ring, when an existing customer calls. Who rings first? When does it move to the next person? When does it go to overflow?

Most owners have never looked, and the answer is often a surprise. Short ring time, named people first, reception last. The call center is the safety net, not the plan.

3. Let customers interrupt meetings

Make it a written rule: if a customer calls, you can leave any meeting. Including the owner's meeting. Say it out loud to your team, because otherwise they will assume the meeting with the boss is more important. It is not. The customer comes before the CEO. A meeting can wait ten minutes. A customer who hears ringing will not.

4. Deliver bad news by voice

Cancellation, delay, reschedule, a part on back order, a technician who cannot make it: call. Then text a summary if you want. And never deliver a problem without at least one option: a new time, another technician, a partner, a callback with a specific time.

If a visit is at risk, call the evening before, not the morning of. Customers can plan around a change they hear about early. They cannot plan around a surprise.

5. Measure where the calls land

You cannot manage this by feel. Every day, someone should know: how many existing-customer calls went to the wrong place, how many were missed, and how long people waited for a callback.

Routing rules drift. Someone changes a setting, someone goes on vacation, and the calls quietly start going somewhere else. A daily number catches it before customers do.

6. Build an escalation path with clocks

Every escalation path should have a time on it. If a customer asks for a manager, who calls them back, and by when? If that person does not, who is next? Escalations grow in silence. A clock on every step stops the silence.

7. Staff for the call, not for the typing

A fair question always comes up: what if the team is already on the line with another customer? If that happens once in a while, the safety net catches it. If it starts happening all the time, you add people. If the phone is the work, you staff for the phone.

8. Give the keyboard work to software

This is where AI comes in, and I want to be careful about how I say it.

I believe most of the work people do behind keyboards, the data entry, the status updates, the copy-paste between systems, the routine messages, will be done by software. I see it every day in my own company, where AI seats already read our CRM and answer questions that used to mean asking someone to build a report. I wrote about that in the agentic CRM.

The job that stays human is the conversation with the customer. A scared homeowner with no heat. A member who feels let down. A family deciding on a big repair. That is where people are irreplaceable, and that is where I want my people spending their time.

So the goal is not fewer people. The goal is to move people from the keyboard to the customer. Let the bots type. Let people talk.

What "customers always first" is not

A few things I want to be clear about.

It is not "the customer is always right." Customers are sometimes wrong. Putting them first means you pick up and deal with it, live, like an adult. It does not mean you agree with everything.

It is not "answer every call in thirty seconds or you are fired." It is a system. If people miss calls because they are buried in typing and meetings, that is a design problem first.

It is not an anti-call-center rule. A call center matters. It answers when nobody else can, and it books new customers. The point is to use it for what it does best: reception and backup. Not as the default home for customers who already have a relationship with a team.

It is not only for big companies. If you are a $2 million company, this is easier for you than for me. You have fewer people, fewer handoffs and fewer places for a call to get lost. Use that.

How to start this week

If you run a home service company, here is what I would do in the next seven days.

1. Call your own company as a customer. Call as an existing customer. Count the rings. Notice who answers and whether they know you.

2. Draw the ring path on one page. Who rings first, second, third. Where it ends up after hours.

3. Name the owners. One person or small team for existing customers and members. Write their names next to the phone line.

4. Announce the meeting rule. Customers interrupt meetings. Including yours.

5. Ban bad news by text only. Call first, always with an option.

6. Pick one daily number. Existing-customer calls that landed in the wrong place or went unanswered yesterday. Look at it every morning.

7. List the keyboard work. Write down what your office types every day. That list is where software, and later AI, should start.

None of this needs new software. It needs an owner who decides the phone is the center of the business, and then checks every day that it still is.

Where this goes

What strikes me most is how small the fix usually is. One honest question about where a call goes. A shorter ring. A clear owner. A rule that the customer comes before the CEO.

Most operational problems in home services look big from the outside. A wave of escalations, bad reviews, cancellations. But when you trace them back, they often start in one small place: a phone that rang too long, and a person who was typing instead of talking.

AI will take a lot of the typing. Good. That gives us back the one thing customers have always wanted from a home service company: a real person who picks up, knows who they are and owns the problem until it is fixed.

That is what customers always first means to me.

FAQ

Why do customer escalations happen in home services?

Most escalations come from how the company communicates after something goes wrong, not from the original problem: unanswered calls, missed callbacks, bad news sent by text with no options, handoffs that make customers repeat themselves, and no clear owner for the customer.

What does "customers always first" mean in practice?

It means existing customers reach a named person live, the phone takes priority over meetings, including the owner's, bad news is delivered by voice with options, and someone checks every day where customer calls actually landed.

Should a call center handle existing customers?

A call center works best as reception and backup: answering new callers, booking first visits, and covering after hours and weekends. Existing customers and members should first reach the team that owns the relationship, with the call center as the safety net.

Is it OK to text customers about cancellations?

A text is fine as a summary, but not as the only message. Call first, explain what happened and offer at least one option, such as a new time, another technician or a partner. A cancellation by text with no options is a common trigger for escalations.

How can a small home service company reduce escalations without new software?

Call your own company as a customer, map the ring path, name owners for existing customers, let customer calls interrupt meetings, deliver bad news by phone, and track one daily number for calls that were missed or went to the wrong place.

Will AI replace people who talk to customers?

I don't think so. AI is very good at keyboard work: data entry, status updates, routine messages and analysis. The conversation with a worried homeowner is the job that stays human. The goal is to move people from typing to talking.