First Responder, Military, and Senior Discounts.
klein cooling ac university header graphic link

SECTION 10

CUSTOMER-SUPPLIED DIAGNOSES

10.1 Purpose

The diagnostic process begins with the customer.

Before opening a panel, connecting gauges, checking voltage, or forming a theory, the technician should understand:

What happened?

When did it happen?

What was the equipment doing when it happened?

What changed before it happened?

What has happened since?

The customer may also have a theory about what is wrong.

They may have:

  • Googled the symptoms.
  • Watched YouTube.
  • Asked Reddit.
  • Asked Facebook.
  • Asked their neighbor.
  • Asked their brother-in-law who “does commercial.”
  • Asked ChatGPT.
  • Asked Gemini.
  • Read an error code.
  • Taken measurements.
  • Removed the thermostat.
  • Already purchased the part they believe is bad.

Sometimes they’re wrong.

Sometimes they’re close.

Sometimes they’re exactly right.

But the most valuable thing the customer gives us may not be their diagnosis.

It may be the information that caused them to reach it.

OPERATING PRINCIPLE

Listen to the customer.

Ask the right questions.

Then diagnose the equipment.


10.2 Listen Before You Diagnose

Do not walk into the house already diagnosing.

Listen first.

If the customer says:

“I think it’s the capacitor.”

Do not immediately respond:

“Yeah, probably.”

And don’t respond:

“No. I doubt it.”

Ask:

“What was it doing that made you think capacitor?”

Now the customer says:

“The thermostat said cooling. The fan inside was running. I went outside and the outdoor unit was humming, but the fan wasn’t spinning.”

Now we have information.

The capacitor diagnosis may still be right or wrong.

But the customer just gave us part of the sequence of operation during the actual failure.

That can be considerably more valuable than the word “capacitor.”

OPERATING PRINCIPLE

Do not just ask what the customer thinks is wrong.

Find out what they saw, heard, felt, smelled, measured, or experienced that made them think it.


10.3 Ask Questions That Build the Story

Good diagnostic questions establish a timeline.

Depending on the complaint, ask:

  • When did this start?
  • What exactly was happening?
  • Was the indoor unit running?
  • Was the outdoor unit running?
  • Did anything stop running?
  • Was air coming from the vents?
  • Was the air warm, cool, or changing?
  • Did you see ice? Where?
  • Did you see water? Where?
  • Did you hear anything unusual?
  • Did you smell anything unusual?
  • What was displayed on the thermostat?
  • Was there an error code?
  • Does it happen constantly or intermittently?
  • Does it happen at a particular time of day?
  • Does it happen after the system has been running for a while?
  • What happened immediately before the problem started?
  • Was anything recently repaired, replaced, cleaned, adjusted, or changed?
  • Did you reset the breaker or shut the system off?
  • What happened after you reset it?
  • Has this happened before?
  • What have you already tried?
  • Do you have a picture or video of it happening?

Not every call requires every question.

This is not an interrogation.

Ask the questions that help explain the complaint.


10.4 “My AC Isn’t Working”

Customer:

“My AC isn’t working.”

Technician:

“Okay.”

Excellent.

We have established that an HVAC company was successfully contacted.

Continue.

Ask:

“Tell me what it’s doing.”

Then narrow the complaint.

“Is the thermostat on?”

“Is the indoor fan running?”

“What about the outdoor unit?”

“When did you first notice it?”

“Did anything happen or change before that?”

“Have you reset anything?”

“Has it done this before?”

A technician can begin troubleshooting before the tool bag has even been opened.

OPERATING PRINCIPLE

A good technician knows which tests to perform.

A great technician also knows which questions to ask.


10.5 The Customer Knows Their House

The customer may not know refrigeration theory.

They know their house.

They may know:

“That pipe never made that noise before.”

“The bedroom always cooled until last week.”

“It only happens around four in the afternoon.”

“The outside unit shuts off, but the fan inside keeps running.”

“It started right after the thermostat was replaced.”

“Every time the power flickers, it does this.”

“It runs fine at night.”

“That light was blinking when it stopped.”

These observations matter.

Do not confuse lack of HVAC vocabulary with lack of useful information.

The customer has lived with the equipment.

You arrived twelve minutes ago.


10.6 Start With What Changed

This deserves repeating from Section 08.

If the customer says:

“It stopped cooling right after we changed the thermostat.”

Start at the thermostat.

If they say:

“It started freezing after the filter was changed.”

Check the filter and airflow.

If they say:

“It hasn’t worked correctly since the blower motor was replaced.”

Evaluate the motor installation and configuration.

If they say:

“It started after the power outage.”

Relevant.

If they say:

“My nephew changed some settings yesterday.”

Very relevant.

A recent change does not prove causation.

It does establish a logical starting point.

OPERATING PRINCIPLE

When the customer tells you what changed immediately before the problem started, treat that information as diagnostically significant until testing shows otherwise.

They just handed you a clue.

For free.

Use it.


10.7 Ask What Has Already Been Done

Always determine whether the customer or someone else has already interacted with the system when that information could affect diagnosis.

They may have:

  • Reset breakers.
  • Cycled power.
  • Replaced thermostat batteries.
  • Replaced the thermostat.
  • Changed the filter.
  • Cleaned the drain.
  • Removed thermostat wires.
  • Changed installer settings.
  • Replaced a capacitor.
  • Added refrigerant.
  • Washed the outdoor coil.
  • Opened access panels.
  • Moved wires.
  • Had another company perform repairs.

Do not scold them.

You need the information.

What happened before you arrived affects what you are seeing now.


10.8 Ask What Happened Before the Reset

This is especially important with intermittent and modern equipment.

Customer:

“It wasn’t working, so I flipped the breaker. Now it’s fine.”

Do not stop at:

“Cool.”

Ask:

What was it doing before the reset?

Was there an error code?

Which components were running?

How long had the problem been occurring?

Has this happened before?

How long does resetting it usually restore operation?

A power cycle may change the condition you were called to diagnose.

The fact that the equipment works now does not erase what happened an hour ago.


10.9 Customer Photos and Videos Are Evidence

If the customer has a photo or video:

Look at it.

They may have captured:

  • Ice.
  • Water.
  • An error code.
  • A noise.
  • A blower stopping.
  • A condenser fan continuing to run.
  • Thermostat behavior.
  • Intermittent cycling.
  • Smoke.
  • A condition that disappeared before you arrived.

A 14-second video may show the exact failure that refuses to occur while you are standing there.

Do not insist on live theater.


10.10 Customer-Supplied Error Codes

If the customer reports an error code:

Write it down.

Ask:

  • What code was displayed?
  • Where was it displayed?
  • When did it occur?
  • What was the system doing?
  • Was power reset afterward?
  • Has the code appeared before?
  • Is there a photo?

Then check applicable fault history and manufacturer documentation when available.

Do not dismiss:

“It said E7 last night.”

because it no longer says E7.

That may be one of the best clues you get all day.


10.11 Listen to the Entire Sentence

Sometimes one word changes the call.

Customer:

“I think the capacitor failed again.”

Important word:

Again.

Ask:

“When was it replaced?”

Now the call may involve:

  • A repeat component failure.
  • Incorrect application.
  • Another electrical condition.
  • A motor or compressor problem.
  • Installation issues.
  • Or an unrelated failure.

Likewise:

“It only happens in the afternoon.”

“It started after the maintenance.”

“The breaker trips when the outdoor unit starts.”

Those words matter.

Listen for them.


10.12 Do Not Dismiss Customer Research

Customers research things.

Good.

Klein Cooling literally publishes AC University to help them do it.

Do not respond to customer research with:

“You shouldn’t believe everything online.”

“I’ve been doing this for 20 years.”

“That’s definitely not it.”

before testing anything.

The customer may be wrong.

You may be wrong.

The measurements will help sort this out.


10.13 “Google Says It’s the Capacitor”

Excellent.

Ask why.

Customer:

“Google says it’s probably the capacitor.”

Technician:

“It definitely could be. What was the system doing?”

Then test it.

If the capacitor is rated:

45 µF ±6%

and measures:

18.7 µF

now we have a diagnosis supported by evidence.

If it measures:

44.2 µF

we keep diagnosing.

Google did not win.

Google did not lose.

We tested the capacitor.


10.14 When the Customer Is Right

Tell them.

Customer:

“I think the capacitor is bad.”

Testing confirms failure.

Say:

“You nailed it. It’s rated 45 µF ±6%, and I’m measuring 18.7 µF.”

Do not become professionally threatened because the homeowner correctly identified a failed component.

Your HVAC license remains valid.


10.15 When the Customer Is Wrong

Do not celebrate.

Do not smirk.

Do not say:

“See? That’s why you shouldn’t Google this stuff.”

Show them what you found.

“I can see why you suspected the capacitor. I measured it at 44.2 µF against its 45 µF ±6% rating, so it’s within tolerance. Here’s what I found instead.”

OPERATING PRINCIPLE

Do not prove the customer wrong.

Prove the diagnosis right.


10.16 When the Customer Is Almost Right

Customer:

“The thermostat is bad.”

Finding:

The thermostat is blank because a condensate safety opened.

Don’t say:

“Nope. Thermostat’s fine.”

Explain:

“You were right that the thermostat lost power. What caused it was the drain backing up and opening the safety switch. The thermostat itself is operating.”

Now the customer understands what actually happened.

That’s the objective.


10.17 Customer Terminology

Customers may call the outdoor unit:

  • Condenser.
  • Compressor.
  • Heat pump.
  • AC.
  • Outdoor unit.
  • Outside thing.
  • Big fan outside.
  • That freaking thing beside the house.

All acceptable.

You know what they mean.

Do not derail a useful conversation to announce:

“Technically, that’s the condensing unit.”

Congratulations on knowing the technically correct word.

Continue working.

Clarify terminology only when the distinction actually matters to diagnosis.


10.18 “I Saw It on YouTube”

Fine.

Ask what they saw.

The video may be:

  • Exactly applicable.
  • Generally useful.
  • About completely different equipment.
  • Excellent technical instruction.
  • Twelve years old.
  • A man in flip-flops beating a condenser with channel locks.

Evaluate the information.

Do not evaluate the customer for watching it.


10.19 “ChatGPT Says…”

Also fine.

AI can provide useful information.

It can also lack:

  • Equipment-specific information.
  • Actual measurements.
  • Complete operating conditions.
  • The physical ability to stand in front of this particular air conditioner.

So can a technician who hasn’t tested anything yet.

Customer:

“ChatGPT says low suction means it’s low on refrigerant.”

Response:

“Low charge can cause low suction, but other conditions can too. Let’s get the rest of the measurements and determine what’s actually happening.”

No technological holy war required.


10.20 Reddit, Facebook, Neighbors and Brothers-in-Law

The source does not determine whether information is correct.

Evidence does.

A Reddit comment may be correct.

A Facebook comment may be wrong.

A neighbor may recognize the exact sound their own system made before a failure.

And the customer’s brother-in-law who “does commercial” may actually know HVAC.

Statistically, somebody’s has to.

Listen.

Verify.


10.21 Customer Measurements

Some customers own:

  • Thermometers.
  • Hygrometers.
  • Multimeters.
  • Infrared thermometers.
  • Smart-home sensors.
  • Energy monitors.
  • Refrigerant gauges.
  • Enough tools that we’re beginning to wonder whether they need a job.

Their measurements may be useful.

Ask:

  • What instrument was used?
  • Where was the measurement taken?
  • How was it taken?
  • Under what operating conditions?
  • What exactly was measured?

OPERATING PRINCIPLE

Respect the measurement.

Verify the method.


10.22 The Infrared Thermometer

An infrared thermometer measures surface temperature.

It does not directly measure the temperature of the air moving through the center of a supply register.

If the customer says:

“My supply air is 51 degrees.”

while holding an infrared thermometer:

Do not laugh.

Explain what the instrument measures.

Then obtain the measurement needed using an appropriate method.

Education beats humiliation.

Every time.


10.23 “The Other Company Said…”

Another company’s diagnosis is information.

Customer:

“The other company said the TXV is bad.”

Do not immediately agree.

Do not immediately disagree.

Ask:

  • What was the original complaint?
  • What did they test?
  • What readings were provided?
  • Did they perform a repair?
  • Did they add refrigerant?
  • Did anything change afterward?
  • Is there an invoice or diagnostic report?

Then perform our own diagnosis.

See Section 13 — Previous Technicians & The Last Guy.


10.24 Customer-Supplied Parts

Sometimes the customer already purchased what they believe is the failed component.

The part sitting on the kitchen table does not establish the diagnosis.

Diagnose first.

If company policy allows installation of the customer-supplied component, verify compatibility and explain applicable terms before installation.

Do not install an incorrect component because:

“Amazon says it fits.”

Amazon is not currently standing in the attic.


10.25 “Can You Just Replace It?”

Customer:

“I know it’s the thermostat. Can you just replace it?”

Respect the request.

But distinguish between:

a customer-requested component replacement

and:

a component Klein Cooling diagnosed as failed.

If we have not diagnosed it, do not pretend we have.

Where appropriate:

“We can absolutely discuss replacing it. Before I tell you that’s the repair you need, I’d like to verify that it’s actually the problem.”

That’s not arguing with the customer.

That’s protecting them.


10.26 Do Not Turn Diagnosis Into a Contest

The objective is not to establish who knows more about HVAC.

We should know more about HVAC.

This is literally our job.

There is no trophy for proving it in the customer’s living room.

The objective is:

Find the problem.

If the customer gives you useful information:

Use it.

If their theory is correct:

Great.

If it is wrong:

Explain why.

If neither of you knows yet:

Keep diagnosing.


10.27 Do Not Weaponize Technical Language

Technical knowledge should make complicated things clearer.

Do not use jargon to establish superiority.

Customer:

“I think it’s low on Freon.”

Technician:

“Actually, the evaporator saturation temperature relative to sensible and latent load—”

Stop.

You know what they meant.

Obtain the measurements.

Then explain the findings in understandable language.


10.28 When Their Information Changes Your Theory

Good.

That’s what information is supposed to do.

Example:

You are investigating an intermittent no-cool.

The system currently operates.

Customer says:

“When it stops cooling, the outdoor fan is still running.”

That matters.

Do not ignore it because you already developed another theory.

OPERATING PRINCIPLE

Do not become loyal to your first diagnosis.

Become loyal to the evidence.


10.29 When You Disagree

When your diagnosis differs from the customer’s:

Explain:

What you tested.

What you measured.

What those measurements are compared against.

Why the evidence supports your conclusion.

Example:

“You thought it might be low on refrigerant, and that can cause some of the symptoms you described. I found the return airflow restricted. Here’s the static pressure before and after correcting it, and here are the refrigeration readings afterward.”

That is different from:

“Nah. Charge is good.”

Remember Section 07.

Good is not a measurement.


10.30 Never Fake Certainty

If a customer asks a question you cannot answer yet:

Say so.

“I’m not sure yet. Let me verify that.”

Do not bluff because the customer appears knowledgeable.

Do not become more confident because you feel challenged.

Do not invent an explanation to regain authority.

See Section 12 — The “I Don’t Know” Policy.

OPERATING PRINCIPLE

We do not protect credibility by pretending to know.

We protect it by finding out.


10.31 The Customer May Know More About This Particular System Than You Do

They may have:

  • Owned it for 15 years.
  • Experienced the same fault before.
  • Watched previous repairs.
  • Read the service manual.
  • Recorded months of temperature data.
  • Worked in HVAC.
  • Be an electrician.
  • Be an engineer.
  • Be the person who designed the freaking board.

Do not assume incompetence based on which side of the invoice someone is standing on.

You are responsible for the diagnosis.

You are not required to be the smartest person in the house.


10.32 AC University Customers

A customer may quote our own website to us.

Good.

That’s why we built it.

Customer:

“Your article says airflow problems can affect refrigerant readings.”

Do not become annoyed because they read the article.

Explain how that principle applies—or does not apply—to their equipment and the measurements you obtained.

Publishing educational material and then resenting educated customers would be an extraordinary business strategy.


10.33 Make It Safe for Customers to Tell Us What Happened

This matters.

We do not want a customer afraid to say:

“I Googled it.”

because another technician rolled their eyes.

We don’t want them hiding:

“I changed the thermostat myself.”

because they expect a lecture.

We don’t want them withholding:

“I reset the breaker four times.”

because they think they’ll look stupid.

Those details may be critical.

The technician’s attitude directly affects the quality of information the customer is willing to provide.

OPERATING PRINCIPLE

Customers who feel respected give us better information.

Better information helps us diagnose better.


10.34 What We Want From the Customer

We want to know:

What happened.

When it happened.

What changed.

What they saw.

What they heard.

What they smelled.

What they felt.

What they measured.

What error codes appeared.

What someone else told them.

What they researched.

What they already tried.

What they think is wrong.

Then we combine that history with what the equipment tells us.

THE KLEIN COOLING DIAGNOSTIC EQUATION

Customer history + technician questions + actual measurements + proper testing = better diagnosis.

Not quite as catchy as superheat.

Considerably more useful.


10.35 The Klein Cooling Customer Interview Test

Before moving past the customer interview, ask yourself:

Do I actually understand the complaint?

Do I know when it started?

Do I know whether it is constant or intermittent?

Do I know what the equipment was doing during the failure?

Did I ask what changed before it started?

Did I ask what the customer already tried?

Did anyone else work on the equipment recently?

Was power reset?

Were there error codes?

Does the customer have photos or videos?

What made the customer think their diagnosis was correct?

Did I listen to their observations—or only their conclusion?

If you cannot clearly explain what the customer is experiencing:

You probably aren’t finished asking questions.


10.36 The Klein Cooling Customer-Supplied Diagnosis Test

When the customer gives you their own diagnosis, ask:

Did I listen before responding?

What evidence caused them to reach that conclusion?

Is their theory reasonable to test?

Did I test it rather than automatically accept or reject it?

If they’re wrong, can I explain why using actual evidence?

If they’re right, am I willing to simply tell them they’re right?

Am I correcting terminology that does not need correcting?

Am I becoming defensive because the customer knows something?

Am I diagnosing the equipment—or trying to win an argument?

If you’re trying to win:

Stop.

There is no prize.


10.37 Final Customer-Supplied Diagnosis Standard

Listen before you touch the equipment.

Ask questions.

Build the timeline.

Understand exactly what the customer experienced.

Ask what changed.

Ask what has already been done.

Ask what happened before the breaker was reset.

Look at their pictures.

Watch their videos.

Write down their error codes.

Consider their measurements.

Listen to their theory.

Then:

Verify it.

Do not dismiss a diagnosis because it came from Google.

Do not accept a diagnosis because it came from Google.

Do not dismiss it because it came from another HVAC company.

Do not accept it because it came from another HVAC company.

Do not correct harmless terminology.

Do not embarrass customers for trying to understand equipment they own.

Do not become defensive when they know something.

If they’re wrong:

Show them why.

If they’re partially right:

Explain the rest.

If they’re right:

Tell them they’re right.

And never forget:

The customer was there when the system failed.

You probably weren’t.

Their observations matter.

Their history matters.

Their questions matter.

Our measurements matter.

Our testing matters.

OPERATING PRINCIPLE

The customer gives us the history.

The equipment gives us the measurements.

The technician’s job is to ask the right questions, listen to both, and connect the two.

END OF SECTION 10