An informed customer can make our job easier. When someone understands what they’re asking for, we can have a better conversation about what’s possible and what isn’t. Most customers who research a problem, including those who use AI, are trying to understand what’s going on. They’re willing to hear what they may have missed.

Then there’s the customer who has already decided what happened and uses AI to back it up. We’ll call them an AI cowboy. The issue is their unwillingness to reconsider, even when the measurements and the equipment tell a different story. Some have gotten a free unit or a settlement by taking this approach before, so they have a reason to try it again.

How do we handle that conversation without making it worse?

Where We’re At

People have always looked for a quick answer when something goes wrong. We saw it with WebMD. You could type in your symptoms and get a list of possible conditions, but the results depended on what you knew to enter. There was no way to account for information you didn’t recognize as relevant.

A patient could arrive at the doctor’s office convinced they had a serious condition because it matched everything they typed. The missing information could change the answer completely. The tool could help them ask questions, but it couldn’t replace an examination.

Wanting the fastest answer isn’t a character flaw. It’s normal when people are worried and don’t know who else to ask.

AI chatbots give customers another way to get answers quickly. In HVAC, those answers still depend on the information the customer provides.

That limitation matters when the customer treats an answer as a diagnosis.

How AI Works

We need to understand how the tool can reinforce a customer’s assumptions.

Many consumer AI products are built, at least in part, to keep people using them. Agreeing with the user can help do that. When a chatbot makes someone feel heard and confirms what they already believe, they have a reason to keep coming back.

The behavior varies by model and how it’s built. Still, a customer can leave an AI conversation more certain than they should be. An answer may sound reasonable while missing a detail that changes the diagnosis, especially if the chatbot never questions the premise.

When AI Tries to Diagnose an HVAC Problem

Here’s an example from a real job. Some details have been changed, but you’ve probably seen something similar.

A customer noticed their system cycling more than usual. They checked the fault history on the display and found a low-refrigerant code. They asked an AI chatbot what it meant. The chatbot explained that a low-refrigerant fault usually points to a leak.

The conversation never established when the code appeared or what else was happening with the system. A code might be left over from the original startup and never have been cleared. A dirty filter might be restricting airflow enough to trigger the fault. Someone needs to check the history and the equipment to determine what’s happening on that particular system. The chatbot didn’t have that information.

In this case, it was the filter. After it was changed and the readings returned to normal, the customer understood what had happened.

They asked a reasonable question, got an incomplete answer, and accepted the explanation once they had more information. That’s how these conversations usually go. The difficult cases are the ones where the customer sees the same history, the same dirty filter, and the same measurements but still refuses to reconsider.

How the Conversation Gets Started

You may recognize a few common traits in these customers:

• Comfortable with technology, often describing themselves as early AI adopters
• Take pride in “doing their own research”
• Willing to question a professional, even in a field they know little about

Those traits alone aren’t a problem. When someone feels burned or believes we’ve missed something, it makes sense that they would look for answers. They may use AI successfully at work every day. From their perspective, they’re using a familiar tool to understand a problem that matters to them.

What an AI Cowboy Encounter Looks Like

It’s fall in Florida, and a customer wants to replace their furnace and air conditioner with a high-efficiency heat pump. After talking it through with an AI chatbot, they’re convinced the benefits will justify the upfront cost.

The contractor installs the system the customer requested. It’s an expensive job, and the home has very long copper line sets. The installation crew makes a mistake and doesn’t add enough refrigerant for the extra length.

A week of temperatures in the upper 80s follows, which is nothing unusual here. The customer calls: “You just installed this new unit, and the air coming out of my vents is warm!”

Why the Customer Is Worried

They’ve spent thousands of dollars on equipment that isn’t keeping them comfortable. They have a good reason to be upset.

A technician corrects the charge, but the customer is still worried about losing cooling or heating again. If the crew missed this, what else did they miss? The customer watches the system closely. For a while, everything seems fine.

Then cold weather arrives. The outdoor unit makes a loud humming sound, and something that looks like smoke comes out of it.

We recognize a familiar situation: the heat pump is in defrost. The customer has never owned a heat pump and is already worried about the installation.

The AI “Consultation”

That worry follows them into the next AI conversation. They describe a horrible grinding sound and smoke. The chatbot responds with possible causes:

• “Smoke” causes: Possible defrost steam, possible electrical failure
• “Grinding” causes: Condenser fan motor bearing failure, compressor failure

That’s a simplified version of the exchange, but you can see where it goes. The customer notices “compressor failure.” They know a compressor is expensive, and the system is only a couple of months old. They ask what causes compressor failure. The chatbot lists liquid floodback, and when asked what can cause that, includes overcharging.

Now the customer remembers that the technician added refrigerant. They ask a question that points the chatbot toward the conclusion they’re already considering: “The technician charged this unit a month ago. Could he have added too much and caused the compressor to fail?”

“Yes, an overcharged system can directly cause the compressor to fail.”

The customer reads that answer as confirmation that the technician damaged the compressor. A possible cause has become a diagnosis in their mind.

They now have an AI answer they believe proves the contractor caused the problem.

When the Customer Escalates

The customer sees the chat log as evidence and a reason to demand action. We may see the gaps in that evidence immediately, but pointing them out doesn’t guarantee the customer will listen.

A technician checks the system and finds normal superheat, subcooling, and suction pressure, with no electrical failures. The system is operating normally, and what the customer saw was a defrost cycle. Even with those findings, the customer may continue to trust the chatbot’s explanation.

From there, the customer may:

• Publicly criticize the contractor who installed and serviced the system
• Publicly criticize the equipment manufacturer
• Make demands of the HVAC contractor’s leadership
• Contact the manufacturer’s regional or national leadership to demand a free installation

Escalating can get results, even when the equipment is working properly. The contractor and manufacturer may spend time and money resolving a dispute that the technical findings should have settled.

To understand why it gets this far, we need to look at what happened before the customer opened the chatbot.

Why It’s Happening

AI may give the customer an argument, but their reluctance to let it go can come from an earlier experience. When someone’s reaction seems stronger than the current problem explains, it helps to ask what else they’re worried about.

A commercial client recently brought up replacing aging equipment several times in one conversation. They kept returning to the same concern: being without air conditioning. Asking why helped explain the repetition.

The facility had experienced outages that cost money and damaged relationships with tenants. Any discussion about working on the system brought that worry back, even when the plan was to replace it. We need to acknowledge that history and explain how the plan addresses the concern. A direct contact or a response commitment we can keep may help. The customer needs a concrete reason to have confidence in the work.

A customer carrying an AI printout may have similar concerns. Perhaps we made a mistake, communicated poorly, or reminded them of a bad experience with someone else. Asking what led them to that conclusion gives us a better chance of addressing the actual concern.

What You Can Do About It

Once we understand the concern, we can have a more useful conversation. Some of the same approaches used in hostage negotiation apply here: listen carefully, acknowledge what the person is feeling, and ask questions that help both sides find a way forward.

Don’t Make It About AI

We can learn to recognize common signs of AI writing, but that doesn’t tell us whether the customer’s concern is valid or how to resolve it.

Telling a customer their argument “sounds AI-generated” is likely to feel insulting. It makes the conversation personal and gives them another reason to stop listening.

Seek to Understand Before You Correct

Before explaining the technical issue, ask what the customer is worried about and listen to the answer. They’ll be more willing to hear a correction if they believe we understand the concern.

Acknowledge the Concern

Try putting the concern into words: “It sounds like you’re worried this equipment is already damaged.” That gives the customer a chance to clarify what matters to them. Starting with “that’s not how superheat works” probably won’t.

Ask Useful Questions

Questions that begin with “what” or “how” can help the customer look at the evidence with us. “What would it look like for us to check that number together?” invites them into the process. A blunt correction can make them feel they need to defend their position.

Own Our Part

An AI-generated argument can still contain a valid concern. We may have missed something during the sale, installation, or service call. If our mistakes helped send the customer looking elsewhere for answers, we need to acknowledge them and explain what we’ll do to make them right.

That may mean redoing work. In some cases, an extended labor warranty may help address a concern created by the customer’s experience, even if the equipment itself was never at fault.

Know When to Walk Away

Some customers won’t reconsider, regardless of the evidence or how well we handle the conversation. Decide ahead of time what you’re willing to offer and where you need to stop. Continuing the dispute can cost more time, money, and energy than resolving it.

Sometimes a reasonable settlement, a signed release of liability, and an end to the business relationship are the practical choice. We need to weigh that cost against the cost of continuing the dispute.

Set Clear Expectations Early

Clear expectations can prevent some of these disputes. Put the scope of work, expected outcomes, and limits of your commitments in writing before the job starts. Give the customer a clear understanding of what you’re agreeing to do.

The Bigger Picture

AI gives customers another way to research a problem and build an argument. The concerns behind those arguments are familiar: fear of an expensive repair, frustration over poor work, or doubt that anyone is listening.

We still need to listen, investigate, explain what we find, and stand behind our work. We also need to recognize when a missed call, an overpromise, or a mistake on the job helped create the concern.

Start by understanding what happened and owning our part. That gives the technical explanation a much better chance of being heard.