Most businesses in tourism, retail, and hospitality run customer service on an implicit premise: the customer is right, and the team's job is to solve their problem as fast as possible. That premise works reasonably well for simple failures, a defective product, a mishandled booking, a service that wasn't delivered. But it stops working, and can become dangerous, when what comes in isn't a complaint about a product, but an allegation about a person.
Four scenarios that aren't the same thing
What reaches customer service in these industries isn't a single type of situation. It's worth distinguishing at least four:
What reaches customer service in these industries isn't a single type of situation. It's worth distinguishing at least four:
1. The customer is affected by a company failure
Example: defective product, unfulfilled service, booking error.
What the company shouldn't assume: that a quick fix closes the issue without understanding the cause.
2. The customer reports inappropriate employee conduct
Example: discrimination, offensive treatment, abuse of authority.
What the company shouldn't assume: that the employee is at fault before investigating.
3. The customer behaves inappropriately toward the employee
Example: insults, threats, discrimination, harassment, or assault.
What the company shouldn't assume: that "it's a customer," so it has to be tolerated.
4. An ambiguous situation requiring investigation
Example: conflicting accounts between customer and employee.
What the company shouldn't assume: that either party is right by default.
The first scenario is the only one where the traditional "resolve fast and keep the customer happy" logic applies as-is. The other three need something different: a process that doesn't assume, from the first contact, who's right.
Attending doesn't mean automatically believing
There's a distinction worth making explicit, because it's almost never said out loud inside companies: attending to someone who files a complaint doesn't mean automatically believing them. Attending means taking it seriously, containing the situation, documenting it, and investigating.
That has an immediate practical implication. A business doesn't need to tell a customer "you're right" on first contact to treat them well. It can instead say something like: "What you're reporting is something we take seriously. We need to gather some background to investigate it, and we're going to escalate this case." That response protects the customer, because their report is taken seriously. But it also protects the employee, because they're not condemned without investigation. And it protects the business, because it doesn't commit to a conclusion before having enough information.
The customer doesn't get immunity for being a customer
The same principle works in the opposite direction, and this part tends to be far less developed at most companies. If an employee reports being insulted by a customer over their nationality, skin color, origin, religion, or gender, the company's response shouldn't be "it's a customer, try to manage it." The customer doesn't get immunity for being a customer.
This has real legal weight in the US worth noting briefly: under Title VII, enforced by the EEOC, employers are legally obligated to protect employees from harassment or discrimination by third parties, including customers, clients, and patients. If an employer fails to act on an employee's complaint about customer misconduct, the employee can file a charge with the EEOC. Several US states, including California under FEHA, go further and explicitly require employers to have a complaint procedure covering third-party harassment.
There's also a documented case from a UK employment tribunal that illustrates exactly what goes wrong when a company defaults to "the customer is always right" without investigating: an employee was dismissed based solely on a customer's account, without ever interviewing the employee or seriously scrutinizing the customer's version. The tribunal ruled the dismissal unfair, finding the company had given "little or no regard for the need... to protect himself or his colleagues from unwarranted abuse."
This matters most in high-contact, high-turnover sectors like tourism, retail, and hospitality, where employees deal with strangers constantly, and where commercial pressure to "not lose the customer" can lead to systematically minimizing what happens to the employee.
A business that takes experience seriously doesn't just train staff to "handle difficult customers." It also defines what conduct is unacceptable from a customer, and what an employee should do when it happens. Customer service doesn't mean tolerating any customer behavior. And it doesn't mean automatically siding with the employee without investigating, either. The business has to manage the incident, not pick a side upfront.
From complaints to experience incident management
This way of framing the problem leads to a broader concept than "complaint handling": experience incident management. It covers everything from something relatively minor, a defective product or a booking mistake, to sensitive situations like discrimination, assault, harassment, or threats, without treating them all through the same pipeline.
An incident management process, built this way, should be able to answer, for each case that comes in, a sequence of questions:
- What happened — concrete facts, not interpretations
- Who's involved — customer, employee, both, third parties
- What's the risk level — reputational, legal, physical safety
- Who needs to be involved — customer service, a supervisor, legal, HR
- What needs to be documented — evidence, statements, context
- What response is appropriate — for the person who filed the report, in the short term, without committing to a conclusion
- What follow-up is required — later verification, formal case closure
None of these questions has an automatic answer. That's exactly what distinguishes incident management from traditional complaint handling, where the process is essentially the same regardless of how different the nature of the problem is.
Why this changes how you think about customer experience
There's an idea deeply embedded in most customer service thinking that says, in essence, the customer is always right. It's a useful simplification for resolving product failures quickly, but it becomes a problem when applied without nuance to situations involving a real conflict between people. There are situations where the customer is wrong. And there are situations where they're directly violating an employee. Serious experience management isn't about satisfying the customer at any cost, it's about resolving the situation based on evidence and severity, without assuming upfront which way the scale will tip.
This also points to something rarely said in customer experience content: customer experience can't be analyzed in isolation from the experience of the employee interacting with them. Both happen in the same interaction, at the same time, and a business that only looks at one of the two is seeing half the problem.
FAQ
What's the difference between a complaint and an experience incident?
A complaint usually relates to a product or service failure, with a relatively linear resolution logic. An experience incident can involve conflicts between people, misconduct reports in either direction, and requires an investigation process before defining a response.
How should a business respond to a report without committing before investigating?
It can confirm that the situation is being taken seriously, that background will be gathered, and that the case will be escalated, without stating upfront that either party is right.
What does it mean that the customer doesn't get immunity for being a customer?
It means unacceptable customer conduct toward an employee, like insults, threats, or discrimination, needs to be managed as what it is, not minimized just because the person doing it is a customer. In the US, employers can face legal liability under Title VII if they fail to act.
Why is employee experience part of customer experience?
Because both happen in the same interaction. An employee going through mistreatment without company support can hardly sustain good service, and a business that ignores this is only managing half of the real problem.
