## TL;DR
Correct the facts, not the person. "The record shows X" beats "You are wrong about X." Give them a face-saving path to the right answer, hold firm on what cannot bend, and never argue to win. The goal is the customer accepting reality without humiliation, because a humiliated customer is lost even when you were right.

## The query

```text
how to handle a customer who is always wrong politely
```

## Use this when

- Customers insist on incorrect facts
- Customers demand things that are impossible
- Customers misremember what was promised
- Training agents on difficult conversations

## Not for

- Abusive or threatening customers (different playbook)
- Actual service failures (apologize and fix)
- Policy debates (explain, do not argue)
- Customers who are right (listen)

## Steps

### 1. Check the record before you correct

Verify against the ticket history, the contract, the usage logs. Never correct a customer from memory. "Let me check the record" also buys you a cooling pause.

Expected output: the facts, sourced.

### 2. State the facts impersonally

"The account shows the plan changed on [date]" not "You changed the plan on [date]." Impersonal phrasing lets the customer update their understanding without admitting fault.

Expected output: a correction with no "you" in it.

### 3. Offer the face-saving path

"Easy to miss - the confirmation email went to [address]." "The pricing page changed in [month]; here is the current version." Give them a story where a reasonable person could have been wrong.

Expected output: the customer accepts the facts without a fight.

### 4. Hold the line kindly on what cannot bend

"Here is what I can do: [options]. What I cannot do is [the impossible thing], because [reason]." Kind does not mean soft. Clear boundaries, stated once, end the loop.

Expected output: options offered, boundary stated once.

### 5. Do not relitigate

Once the facts are established and options offered, move forward. If the customer re-argues, restate briefly and return to the options. Arguing to win costs the customer.

Expected output: the conversation moves to next steps.

## Template: the correction

```text
Let me pull up the record on this, [Name].

What I see: [impersonal facts with dates/references].

[Face-saving context: where the confusion likely came from.]

Here is what I can do: [two options]. What I cannot do is [boundary], because [reason].

Which of the options works for you?
```

## Variant phrasings

### customer insists they are right but wrong

Steps 1 through 3. Verify, correct impersonally, save face.

### dealing with difficult customers politely

Full sequence. Step 4 is where most agents cave or snap.

### customer misremembers agreement

Steps 1 and 2. The record is the whole argument.

## Why it works

Being wrong in public triggers defensiveness, and defensiveness makes people double down. Impersonal facts plus a face-saving story let the customer change their mind without changing their self-image. The firm boundary prevents the politeness from becoming capitulation, which would teach the customer that persistence rewrites reality.

## Edge cases

- The customer might actually be right: if the record is ambiguous, say so and investigate. Correcting from a shaky record is how you become the villain.
- Cultural directness differences: some customers expect blunt correction. Read the tone.
- The third round of the same argument: escalate to a lead. Fresh voice, same facts.
- It becomes abusive: switch playbooks. Politeness has limits; abuse ends the conversation.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NOl2y-Bw_kKP3WAVVgr-hQ