Is Customer Friendliness Really Just About Smiling?

Walk into almost any B2B networking event and mention that you help companies grow through customer loyalty. Within seconds, someone will say: 'My team is friendly. They smile, they are calm, they treat people well.' Anne-Marie Vissers hears this constantly. And she believes it. No employee wakes up in the morning thinking about how to make a customer's day worse. That is not the problem.

The problem is what that statement reveals: a fundamental confusion between staff demeanor and system design. Friendliness is visible. A warm tone, a patient reply, a calm voice during a difficult call. Processes are invisible until they break. And when they break, the friendliest employee in the world cannot compensate for the friction the customer is already feeling.

This is not a people problem. It is a structural one. And most companies are not looking at the structure because they are busy pointing to the attitude.

Here is a real example. Anne-Marie needed to place an order for her business through an online-only portal. No phone number. Everything by email or chatbot. She submitted the form with supporting documents on a Thursday.

Friday: she asked whether everything arrived correctly. Answer: the documents were not in the right format. No guidance on what format would work. She figured it out herself and resubmitted the same day.

Friday evening: she asked again whether the new documents were acceptable. Oskar, the support agent, responded calmly and politely. The documents were still not right. He explained that responses take 24 hours, meaning one business day. Fine.

Monday: she followed up after one business day. Oskar replied, politely, that there was a name mismatch. Her passport showed her maiden name, Anne-Marie van der Pas, not her current name. She explained this and sent proof of marriage. Still Monday.

Tuesday: she followed up again. Something else was missing. This pattern repeated six more times before every document was finally accepted. Her product arrived eight days after the first submission.

Oskar was never rude. Not once. But no one ever reached out to her proactively. Every single step required her to initiate contact. The system was running like a tennis rally where only one player keeps serving.

Oskar did everything right within the constraints of his system. He responded within the promised timeframe. He was clear about what was missing. He was patient throughout. And still, Anne-Marie will never go back to that company.

That is the trap. Companies invest in training their people to be warmer, calmer, and more empathetic, while leaving the underlying process completely untouched. The customer still has to repeat themselves. Still has to guess what format is acceptable. Still has to follow up six times to complete a single transaction.

Friendliness does not remove friction. It cushions it slightly. But a customer who has to chase a company seven times in eight days is not thinking about how pleasant Oskar sounded. They are thinking about how much effort it took to give this company their money.

This is what Kunden Erlebnis describes as the difference between surface experience and structural experience. Surface experience is what your employees say and how they say it. Structural experience is what your customer has to do to get what they came for. The second one drives loyalty. The first one is just the packaging.

Most customers do not complain. They just leave. Or they stay but quietly absorb the frustration and reduce how much they buy. This is why relying on formal complaint data gives a false picture of how processes are actually performing.

The better question is: where does the customer have to chase us? Where are they sending follow-up emails asking whether their previous message was received? Where are they calling to confirm something that should have been confirmed automatically? Where are they repeating information they already gave once before?

Anne-Marie Vissers puts it directly: if one customer is experiencing this, there are many more out there having the exact same experience and saying nothing. The one who reaches out is your data point. The ones who say nothing are your real problem.

This is the first phase of the Bewährte 3-Phasen-Methode from Kunden Erlebnis: the baseline measurement. An NPS campaign, direct customer interviews, and structured feedback analysis to surface exactly where the customer journey loses coherence. Not what employees think is happening, but what customers actually experience.

The output is not a report. It is a map of friction points with enough specificity to act on.

Real customer orientation is not a personality trait. It is a design decision. It means building processes where the customer does not have to repeat themselves, where the next step is communicated without being asked, and where different team members share enough context that the customer never feels like they are starting over.

In the Oskar example, the core failure was not Oskar. It was that each interaction started from zero. There was no accumulated record of what had already been explained. There was no proactive step where the company confirmed progress without waiting for the customer to ask. There was no checklist at the start that told the customer exactly what would be needed, in what format.

These are structural decisions. They require someone to have walked the process from the customer's perspective, not from the inside out. This is what Anne-Marie describes as putting on the customer's glasses: looking at every touchpoint from the position of someone who does not know your internal system and should not have to.

When processes are designed from the outside in, employees can actually do their best work. They are not constantly managing confusion caused by gaps between departments. They can focus on the conversation in front of them instead of explaining why the previous step went wrong.