The Problem with Nice
A few years ago, a training session on customer service opened with a participant who had already decided it was a waste of his time. His objection was direct: the whole subject amounted to being told to be nicer, and he did not see why that required a full day. He was not entirely wrong about how customer service training is often framed. He was entirely wrong about what customer service actually requires.
When the group was asked what being nice meant to them, nobody produced a definition. They produced examples, and the examples did not agree with each other. What read as warmth to one person read as condescension to another. What felt like friendly informality in one context felt like a failure to take the situation seriously in another. Nice turned out to be a word that meant something different to everyone in the room and could not be operationalized by any of them.
That is the problem. Nice is a disposition, not a behavior. It cannot be trained, measured, corrected, or consistently delivered. An organization that tells its people to be nicer has not given them anything to work with. The organizations that consistently deliver good service do not do so because they have hired nicer people. They do so because they have defined specific behaviors and trained people to perform them reliably.
What Empathy Looks Like in Practice
Empathy is the word customer service training reaches for most often and defines least precisely. Telling someone to be empathetic is roughly as useful as telling them to be taller. It describes a desired quality without providing any instruction for how to produce it.
Empathy in a customer interaction is not a feeling. It is a set of behaviors that communicate to the customer that their situation has been understood before any attempt is made to resolve it. The behaviors are specific and learnable.
When a customer describes a problem, the first response is not a solution. It is a restatement of what the customer said, in the listener’s own words, that demonstrates the situation was actually heard. “So what you’re dealing with is that the order arrived three days late and the item was damaged, and you have an event this weekend where you needed it.” That restatement tells the customer that the listener was paying attention and understood the scope of the problem. It also gives the customer the opportunity to correct anything that was missed before the conversation moves forward.
The second behavior is acknowledging what the situation cost the customer before moving to what can be done about it. A customer who placed an order for an event that has now been disrupted is not primarily interested in a refund policy. They are dealing with a specific problem in a specific situation and they need evidence that the person on the other side of the conversation understands that before they will be receptive to any proposed solution.
The third behavior is asking what a good resolution looks like from the customer’s perspective before proposing one. “What would make this right for you?” is not a capitulation. It is the most efficient path to a solution the customer will actually accept. Organizations that skip this step frequently spend time and resources on solutions that do not address what the customer actually needed.
Listening Is a Discipline
Most people in customer-facing roles believe they are good listeners. Most of them are not, or not as consistently as the role requires. Listening in a customer interaction means something specific: taking in what the customer says, holding it without immediately constructing a response, and producing evidence that it was heard before speaking.
The most common listening failure is the premature solution. The customer is four sentences into describing a problem and the service representative has already identified what went wrong and is waiting for the customer to finish so they can explain the fix. The fix may be correct. The customer does not feel heard, because they were not heard. They were waited out.
A second common failure is listening for category rather than content. The representative hears enough to identify the type of problem and stops listening in detail. The specific circumstances the customer is describing, the ones that distinguish this situation from the standard version of this problem, go unregistered. The solution that follows addresses the category and misses the case.
Note-taking during a customer conversation is a visible signal that what the customer says is being recorded for use. It slows the listener down enough to actually absorb what is being said rather than processing it in shorthand. It produces a more accurate account of the situation. And it demonstrates to the customer that the conversation is being taken seriously.
When the Customer Is Wrong
Customer service training tends to avoid this situation because it is uncomfortable, but it occurs regularly and the response to it matters. A customer who has an inaccurate understanding of what they purchased, what was promised, or what the product does is not best served by agreement. They are best served by a correction delivered in a way that does not make them feel foolish for having been wrong.
The approach has three steps. First, acknowledge what the customer expected without validating the expectation as accurate. “I can see why you would have read it that way” is not agreement. It is an acknowledgment that the customer’s interpretation was not unreasonable given what they had to work with. Second, provide the accurate information clearly and without defensiveness. “What the policy actually covers is this” states the fact without implying that the customer was careless or difficult. Third, move immediately to what can be done within the actual terms of the situation rather than dwelling on the discrepancy.
The customer who has been corrected and then helped is in a better position than the customer who was told they were right and then handed a solution that did not reflect the actual facts. Agreement that produces a bad outcome is not a kindness.
The Specifics of Communication
Adjusting communication to the customer in front of you is a skill that requires paying attention to more than what the customer says. The customer who uses technical language and asks detailed questions wants a detailed answer delivered at a peer level. The customer who asks vague questions and waits for the representative to fill in the gaps needs a patient and structured explanation that does not assume shared knowledge.
Getting this wrong in either direction costs something. The customer who is over-explained feels condescended to. The customer who is under-explained leaves without understanding what they were told, which means the problem is not actually resolved regardless of what the representative believes was communicated.
Jargon is the most common failure mode in customer communication. Every industry develops internal language that is efficient among people who share it and opaque to everyone else. A customer calling about an account issue does not benefit from hearing that their request requires a back-end reconciliation before the adjustment posts to the ledger. They benefit from hearing that it will take two business days for the correction to show up in their account. The information is identical. The usefulness is not.
Following Through Is Not Optional
The promise made during a customer interaction is a commitment, and commitments have a specific weight in customer relationships. A representative who says they will call back by the end of the day and does not has not merely failed to call back. They have communicated that what they say cannot be relied upon, and that communication reaches into every subsequent interaction.
The follow-through standard worth holding is simple: do not make commitments you cannot keep, and keep every commitment you make. If the callback cannot happen by end of day, say so and offer a realistic time. If circumstances change after the commitment is made, contact the customer proactively to reset the expectation rather than waiting to see whether they will notice.
Customers forgive problems more readily than they forgive being forgotten. A customer whose problem took longer to resolve than expected but who received updates throughout the process tends to come away with a better impression of the organization than a customer whose problem resolved quickly but who had to call three times to find out what was happening.
Staying Focused on What Can Be Done
Every customer interaction involves constraints. There are things the representative cannot do, policies they cannot override, and outcomes that are not available. How those constraints are communicated determines whether the customer experiences the interaction as helpful or as an exercise in being told no.
“I can’t do that” ends a conversation. “What I can do is this” starts one. The substance may be similar, but the orientation is different. The first statement positions the representative as a gatekeeper reporting limitations. The second positions them as someone working within a set of real constraints to find the most useful path available.
This is not a language trick. It requires that the representative actually knows what is available, thinks through the options before responding, and presents them in a way that gives the customer something to work with. It also requires that the representative resist the pull toward the easiest answer, which is frequently the least useful one.
Feedback Is a Form of Information
Customers who tell an organization what is not working are providing information the organization needs and might not obtain any other way. Most customers do not complain. They form a conclusion and act on it quietly by going somewhere else. The customer who takes the time to say that something was wrong is more valuable to the organization’s ability to improve than the customer who says nothing.
Receiving that feedback well requires a specific posture. The representative who hears a complaint and responds with an explanation of why the situation occurred rather than an acknowledgment of what the customer experienced has not received the feedback. They have defended against it. Customers read that response accurately, and it tends to close the conversation rather than continue it.
The posture worth holding is curiosity about the specific detail of what went wrong. “Can you tell me more about what happened?” is not a stall. It is an attempt to understand the situation precisely enough to respond to it usefully. The answer frequently contains information that a general complaint would not have surfaced.
What Leadership Owes the People on the Front Line
The behaviors described in this article do not develop or sustain themselves. They are trained, reinforced, and demonstrated by the people who lead the teams responsible for customer interactions. A manager who addresses customer situations differently than they train their team to address them has not set a standard. They have set a contradiction, and the team will notice which one is real.
Specific, observed behavior gets specific feedback. A manager who tells a team member that they handled the call well has offered an opinion. A manager who tells a team member that they restated the customer’s situation accurately before proposing a solution, and that this is what kept the conversation from escalating, has given them information they can use. The second form of feedback builds skill. The first confirms a general impression without adding anything to what the team member knows about how to repeat what they did.
The standard worth holding across a customer service operation is not niceness. It is consistency, specificity, follow-through, and genuine engagement with the actual situation the customer is describing. Those things can be trained, measured, observed, and improved. Niceness cannot. It is a reasonable starting point and an insufficient destination.