Over the years I've heard plenty of customer service stories from friends and colleagues, and a couple of recent ones keep rattling around in my head. I've blended and changed the details, but the shape of them is real.
The first one is simple. A manager asked IT for a webcam and speakerphone in a shared conference room. It wasn't her team's room. People from across the organization booked it every day, and it just happened to be the one room on the floor without the setup every other room already had. She called the helpdesk, and instead of getting help, she got transferred to a supervisor whose main concern was figuring out whose budget it should come out of. Maybe her department should pay for it, never mind that her department didn't own the room and half the building used it. Maybe it belonged to facilities. Either way, he talked to her like she didn't understand how the world works. In the end he did put in a ticket, so technically the request was logged. Practically, she hung up feeling like a nuisance for pointing out a gap that affected everyone who used that room.
The second one bothers me more. An employee sent an email to her project team, and autocomplete pulled in someone with a similar name from another part of the organization. Within the hour, a reply came back with a director from that person's division copied on it. It was abrupt and confrontational. Why was she being included in this? She had her own work to do. And by the way, this had been forwarded to the sender's manager. The sender replied with one line saying it was an honest mistake.
A misaddressed email is about the lowest-stakes error in modern office life. When someone answers it by copying leadership and threatening escalation, one of two things is usually happening. Either something else is going on in that person's life, or they have never learned how to communicate when they are irritated. My guess is usually the second. Nobody ever showed them that you can set a boundary without setting a fire. A two-line private reply would have fixed it in thirty seconds: "Hi, I think I was added by mistake. It happens to me sometimes too. Have a great day!" Done, and nobody's reputation takes a hit, including theirs.
Everyone Has Customers
On the surface these two stories have nothing in common. One is an IT department and the other is a coworker. But they are the same failure. Both are customer service problems, and both happened inside an organization where nobody was buying anything.
We tend to think of customer service as something retail stores and call centers do. In reality, almost everyone has customers. If you work on a helpdesk, your customers are the employees who need things to work so they can do their jobs. If you are a colleague, your customers are the people who depend on you, send you messages, and occasionally make mistakes that land in your inbox. Every one of those interactions either builds a little trust or spends some.
I have spent most of my career leading technology organizations, and the lesson I keep relearning is that technology is rarely the hardest problem. People are. The equipment was never the issue. It costs a few hundred dollars. What the supervisor really spent was a manager's trust. She will think twice before calling IT again, and she will probably tell a few colleagues why. That reputation is far more expensive to fix than the hardware.
What Apple Figured Out
So what would a better version of that call have looked like? Apple has spent two decades answering that question. Every Apple Store employee learns a five-step service model built on the company's name: Approach, Probe, Present, Listen, and End. Carmine Gallo wrote about it in The Apple Experience, and companies far outside retail have borrowed it since. None of it requires a storefront. It works just as well on a helpdesk line, and it would have changed that conference room call from start to finish.
It starts with the approach. The first ten seconds set the tone, and there's a world of difference between "Thanks for calling, let's figure this out" and "What do you need?" One tells the manager she's in the right place. The other tells her she's an interruption. From there, a good agent probes before deciding whose problem it is. Why does she want the equipment? Because remote attendees can't see or hear what happens in that room, and every group that books it hits the same wall. Once you understand that, a nuisance request becomes a problem worth solving, and you might discover three other rooms with the same gap.
Then you present a solution, even when the final answer isn't yours to give. Someone does have to pay for the equipment, but in a room the whole building uses, it was never going to be one department's bill, and sorting that out is the organization's job, not hers. "I'll route this to facilities as a shared room issue, and here's your ticket number" costs nothing and changes the whole experience. Along the way, you listen, which Apple considers the hardest step because it means talking less. Most of us are just waiting for our turn to explain policy. The supervisor on that call did plenty of explaining and very little listening.
Finally, you end well. People remember how an experience starts and how it ends, so you tell them what happens next and when they'll hear back, and then you follow up. A closed ticket with no word to the customer isn't a good ending. It's just a quiet one.
But all of that assumes someone picks up the phone or walks over in the first place. In my experience, that's where most fall short.
Notice the People Around You
There's a principle I've lived by for most of my career, and it's one I've tried to teach everyone who has worked for me: be aware of your environment. Customer service doesn't start when the phone rings or a ticket comes in. It starts when you notice someone who needs help before they ask.
Over the years I've seen plenty of families wandering a building looking a little lost, sometimes in places where I don't even work. I walk up and ask if they're looking for somewhere in particular. If I know where it is, I don't point down the hall and wish them luck. I walk them there, and I make some small talk along the way so the trip feels less awkward. It takes a few minutes. It also tells them that even though everyone around them is busy, they matter.
I can't count the number of times I've walked into a meeting and had someone ask, "Hey, did you help out the Smith family the other day?" Sometimes I remember them and sometimes I don't. But my colleagues would tell me it made a real impact, and that the family appreciated someone taking time out of their schedule to get them where they needed to be and taking a genuine interest in who they were. That's the whole point. A few minutes of your day can be the thing someone remembers about your entire organization.
Jesus told a story about this. In the parable of the Good Samaritan, a man lies beaten on the side of the road. A priest sees him and passes by on the other side. So does a Levite. Both were respected men, and both probably had somewhere important to be. It was the Samaritan, the outsider, who stopped, cared for the man, and paid for his recovery out of his own pocket. The ones who walked past weren't villains. They were just busy.
That kind of attention used to be common, and it has become rare. Somewhere along the way we stopped looking up. Many of us move through the day buried in our phones or wrapped up in our own to-do lists, and we miss the person right in front of us who needs a hand. Most people aren't unkind. They just aren't paying attention.
The best organizations don't leave this to chance. Apple puts a greeter at the front door of every Apple Store for exactly this reason, so nobody walks in and stands there wondering where to go. You don't need a job title to do the same thing in your own building.
The good news is that awareness can be learned. Put the phone in your pocket when you walk the halls. Make eye contact. Ask the question. The people known for great service usually aren't doing anything heroic. They simply notice.
Don't Walk Past It
Noticing isn't only about people. It's also about the problems everyone else has learned to step around.
Think about a streetlight that has been out on your road for months. Dozens of people drive under it every night. Everyone notices. Almost nobody calls it in, because surely someone else already has. And the few who did call, and never saw anything change, quietly decided not to bother again.
Psychologists call the first part the bystander effect: the more people who see a problem, the less responsible any one of them feels for it. The second part is how apathy settles into neighborhoods, churches, and organizations alike. It almost never starts with people who don't care. It starts with people who cared, spoke up, and didn't hear back.
In technology, we have a name for what happens next: shadow IT. People don't start working around the system the first time they hear no. They do it when no is all they ever hear. Often the requests are small, the kind of thing that takes minutes, but they sit for weeks or get turned down without an alternative. People still have work to do, so they buy their own tools, build their own spreadsheets, and quietly route around the official process. The rest simply stop asking. Whether they build workarounds or give up, these people aren't troublemakers. They are responding to a system that taught them asking doesn't work.
I often tell technology teams to think of themselves as the stage crew at a concert. IT is the sound engineer and the lighting tech, not the producer. The crew's job is to make the person on stage sound and look great. If the sound and lights don't work together and the singer can't perform, nobody gets paid, including the crew. Support teams exist to serve the mission, not to guard the gate. The fix isn't blame. It's someone willing to notice again, raise it one more time, and answer with a solution instead of a no.
That doesn't mean you can never say no. I've had to tell colleagues and customers no plenty of times. But I've tried never to let it be a flat no. When I couldn't do what someone asked, I came back with three or four alternatives for them to consider. It's the same idea behind Apple's Present step: nobody should walk away empty-handed. Maybe not this tool, but this one. Maybe not this week, but here's what we can do today. A no with options still tells people you're on their side. A no by itself, repeated often enough, teaches them to stop coming to you. Even when the answer to the original request is no, your job is to keep looking for a way to be part of the solution.
The Army taught me a different standard. In basic training, if I walked past a piece of trash on the ground, I was wrong. It didn't matter who dropped it. And if my drill sergeant walked past that same piece of trash after me, I'd be doing push-ups. The lesson stuck. Australian Army General David Morrison put it well: "The standard you walk past is the standard you accept."
That's true of a helpdesk call, a dark streetlight, and a family wandering the hallway. You don't have to own every problem you see. But you do have to stop walking past it. Pick up the trash, raise the issue again, walk the family to the right door. Those small acts are how a culture of service gets built, one person at a time.
I like to encourage people to think like a superhero. Superheroes don't wait to be asked, and they don't stop to figure out whose department the problem belongs to. They're always scanning the room for someone who needs help, and when they spot it, they step in. You don't need a cape for that. You just need to keep your head up and decide that the problem in front of you is yours to do something about.
When They Come In Hot
Not every conversation starts friendly. Sometimes the person on the other end is already frustrated before you say a word, and usually there is a reason. They submitted a ticket two weeks ago and never heard back. They called three times and nobody picked up. They were bounced between departments, each one sure it belonged to someone else. By the time they reach you, they aren't angry at you. They are carrying everything that happened before you.
The instinct is to defend yourself or the process. Resist it. What works better is slowing down, lowering your voice a notch, and naming the gap out loud. "You've been waiting two weeks and nobody has gotten back to you. That shouldn't have happened." You aren't admitting personal fault. You are telling them you see the same problem they see. Most of the heat goes out of a conversation the moment someone feels heard. Proverbs 15:1 put it this way thousands of years ago: "A soft answer turneth away wrath: but grievous words stir up anger."
From there, skip the debate over who dropped the ball and do what Apple trains its people to do: present a solution. Give them a name, a time, and a commitment you can keep. Then keep it. One follow-up call that happens when you said it would does more to rebuild trust than any apology.
This cuts both ways, too. The person in the email story had a legitimate point. Nobody wants to be pulled into a thread that has nothing to do with them. Her problem wasn't the complaint. It was the delivery. James 1:19 is good advice for all of us in that moment: be swift to hear, slow to speak, and slow to wrath. Good customer service isn't just something we owe the people we serve. It is also how we should carry ourselves when we are the ones who feel wronged.
The Three-Email Rule
Here's a rule I've followed for years. If I have to send more than three emails to get clarity on something, we don't have an email problem. We have a communication problem, and the fix is usually a phone call.
By the third round, someone isn't explaining something clearly, or there's a missing piece of context that neither side realizes is missing. Each reply adds a little more friction and a little less goodwill. Five minutes on the phone clears up what a week of back-and-forth couldn't, because you can hear tone, ask a follow-up question in real time, and actually get to the bottom of it.
What I've noticed in the modern workplace is that email often isn't being used to communicate at all. It's being used to cover our backsides. We build a paper trail, copy the right people, and word everything so that if something goes wrong, it can't land on us. That's exactly what happened when the person who received the stray email copied a director and forwarded it to the sender's manager. It wasn't about solving anything. It was about documentation and leverage.
When communication becomes a weapon, trust is the first casualty. People stop asking questions because every question might end up in someone's file. If you find yourself drafting a carefully worded email with three people on the cc line, stop and ask whether a phone call would serve the other person better. Most of the time, it will.
Being Right Isn't the Point
Here's what strikes me about both stories. The supervisor was probably right that the equipment had to be funded by someone. The person who got the stray email was right that it didn't belong in her inbox. Both of them were technically correct, and both of them lost. One lost a manager's trust in IT. The other lost a little standing with the leadership she copied to make her point.
Customer service was never about being right. It's about leaving the other person a little better off than when they found you. Organizations that understand this build trust that carries them through the inevitable bad days. Organizations that don't end up with workarounds, side channels, and people who quietly stop asking for help.
Whether you lead a technology team, answer the helpdesk line, or just happen to be standing in the hallway when someone looks lost, the job is the same. Look out for the interests of others, not just your own.
Apple built its stores around a simple truth: people remember how they were greeted and how they left. The same is true of every helpdesk call, every email, and every lost family in the hallway.
Nobody is going to remember the ticket number. They will remember how you made them feel when they called. So go be someone's superhero today.