Define Heat Exchanger Cleaning Criteria Before Recommending a Method

A reliability engineer calls with a heat exchanger that lost performance and asks a technical sales engineer to name a cleaning method on the spot. Answering that question directly is the fastest way to give bad advice, because the right method depends on facts nobody has stated yet. Material, process fluid, fouling type, access, and disposal rules all shape what a safe and effective cleaning actually looks like, and none of that shows up in a one line request.

Why this conversation goes wrong

When a customer asks which cleaner to use, they usually want an answer that closes the ticket, not a discovery process. A sales engineer under time pressure feels pulled toward giving one anyway. But heat exchanger cleaning is not a single decision you can make from a product sheet. The metallurgy of the tubes and shell changes what chemistry is safe to use. The process fluid on each side tells you what kind of fouling likely formed, scale, coking, biological growth, or general process residue, and each of those calls for a different approach. The deposit itself, confirmed by inspection or lab analysis rather than guesswork, determines whether mechanical cleaning, chemical cleaning, or some combination will actually restore performance. Skip past these facts and recommend a method anyway, and you risk damaging stainless steel with the wrong chemical, missing a deposit that needs an entirely different technique, or promising a result the plant has no way to verify afterward. The conversation goes wrong the moment you treat the request as a product lookup instead of an engineering question that needs site specific facts.

How to prepare before you get on the call

Before you respond to a request like this, get clear on what you need to know and who on the plant side can supply it. Five things matter most.

1. The exchanger material, tube and shell metallurgy included, because that alone rules out entire categories of cleaning chemistry.
2. The process fluid on both sides, since fluid chemistry drives what kind of fouling forms.
3. Direct evidence of the deposit, inspection photos, a lab report, or a description from the last time the unit was opened, rather than assumptions carried over from a similar job somewhere else.
4. The history of the last cleaning, who did it and whether that work was documented, because a missing report is itself a finding worth raising.
5. The plant roles who need to sign off, process engineering, maintenance, and environmental or safety staff typically all have a stake, since disposal of spent cleaning fluid and the shutdown permit both touch people outside the reliability group.

Walk into the conversation with these five points in mind and you ask sharper questions instead of guessing at what matters. You also stop yourself from filling gaps with assumptions that feel reasonable but have no basis in what this specific unit is doing.

What to say

Keep the exchange focused on facts, not on being helpful in the moment.

Reliability engineer Jo opens with the direct question. "Our exchanger lost performance. Can your team just tell us which cleaner to use?"

Sales engineer Morgan does not answer with a product name. "I want to get you the right recommendation, not just a fast one. Can you tell me the exchanger material, the process fluid on each side, and what the deposit looks like? Do you have inspection photos or a sample history?"

Jo answers with what is available. "The bundle is stainless steel. As for deposit evidence, the last cleaning contractor did not leave a report."

Morgan treats the missing report as useful information rather than a dead end. "That gap matters, because it means we are working without a documented baseline. Who can confirm the fluid chemistry on both sides, and who owns the shutdown permit? I would like to set up a review with process, maintenance, and environmental staff so we can define what a successful cleaning actually looks like before anyone names a method."

That last line does the real work. Morgan is not refusing to help, and is not stalling either. Morgan is defining what a good outcome means before committing to how to get there.

Mistakes to avoid

The most common mistake is naming a cleaning method to keep the call moving, then trying to attach conditions to it afterward. Once you have said a product or process out loud, the customer anchors on it, and any caveats you add later sound like backpedaling. A second mistake is accepting secondhand descriptions of the deposit as fact. If nobody has looked at the fouling directly, say so plainly, and ask for a photo or a sample rather than working from someone's memory of what it probably looks like. A third mistake is skipping the ownership question entirely. A reliability engineer can describe the performance problem, but the environmental team may own disposal rules for spent fluid, and maintenance may own the shutdown schedule. Recommend a method before those people are in the room, and you will likely have to redo the whole conversation once someone flags a conflict later. A fourth mistake is letting a missing record pass without comment. When Jo mentions that the last contractor left no report, that is not a throwaway detail, it is a sign the plant has no documented baseline, and it belongs in your recap word for word. Finally, avoid closing the call with a vague promise to follow up. Close it with a specific list of who needs to attend the next review and what each person needs to bring.

How to practice and score it

Run this scenario twice, once playing it the way Morgan should not, jumping straight to naming a method, and once the way Morgan does, holding the line on facts before recommendations. Comparing the two versions side by side makes the difference obvious fast. Score your own performance, or have a manager score it, against a short set of checks. Did you ask about material, fluid, and deposit evidence before naming any method. Did you ask for two concrete records, such as inspection photos or a sample history, rather than accepting a verbal description at face value. Did you name the plant roles, process, maintenance, environmental or safety, who need to be in the review. Did your closing recap list the unknowns explicitly instead of quietly filling them in with assumptions. A sales engineer who scores well here sounds less like someone selling a cleaner and more like someone running a technical review, which is exactly the reputation you want with a reliability team.

DealSpeak's Manufacturing practice conversations give you scenarios like this one, where you rehearse the exchange with an AI counterpart and see where your questions or your recap fell short. The same discipline carries over to related situations, including how you Verify a Hose Assembly Reorder Before It Reaches Maintenance and how you Respond to a Hydraulic Cylinder Repair Dispute Without Assigning Fault.

A heat exchanger cleaning request tests whether you can slow a customer down without frustrating them. Get the facts first, name the owners who need to sign off, and the method you eventually recommend will actually hold up in the field.