Scope a Dryer Exhaust Duct Survey Before Discussing Changes
Help a technical sales engineer clarify dryer exhaust facts and site access for a survey.
Airflow, product moisture, duct condition, and process changes can all produce the same complaint, a dryer that runs slow and product that comes out wetter than it should. When a customer calls with a theory already formed, the easy move is to agree with it or jump straight to a fix. Your job on that first call is different. Get the facts straight, scope a site survey, and let the survey findings drive any conversation about actual changes.
Why This Conversation Goes Wrong
When a process engineer calls and says the duct is too small, they have usually already ruled out other causes in their own head. Agreeing sounds helpful in the moment. But you have not seen the layout, you have not seen operating data, and you do not know what changed since the dryer was installed. Agree over the phone and you have committed to a theory before you have facts. If the survey later points to something else, a clogged filter, a bad damper, inconsistent readings, your credibility takes the hit, not just the sale.
There is a second way this goes wrong. Some technical sales engineers ask too few questions and schedule a survey with no bounds on it. That wastes a site visit. A survey without a clear agenda turns into walking the plant floor hoping something obvious shows up. You need to know what data to review before you arrive, and you need the right person from the plant standing next to you.
How to Prepare Before the Site Visit
Line up three things before you schedule anything. First, get the change history. Ask what has been added, removed, or modified since the dryer went in. A new filter, a modified damper, or a rerouted section of duct changes airflow more than duct diameter usually does. Second, ask for recent operating data, temperatures, moisture readings, and any log that shows when the drop in performance started. If the slowdown lines up with a specific date, that date points you toward a cause faster than a tape measure will. Third, confirm access. Roof access for exhaust ductwork usually needs a permit, a spotter, or a lockout procedure, and you need to know who owns that process before you show up expecting to climb up there.
You also need to know who from the plant will be present. A maintenance owner who knows the ductwork history is worth more than a manager who only read the ticket. If nobody with hands on the equipment can attend, push the date until someone can.
Rehearsing this kind of call matters because the pull to sound certain on the phone is real, and the habit of asking before answering takes practice, not just good intentions. Browse Manufacturing practice conversations to run this exact scenario against an AI counterpart and see where you commit too early.
What to Say During the Call
Here is a version of how this call should go.
Process engineer Priya says, "Our dryer has slowed down and we think the exhaust duct is undersized. We would like a proposal to replace it."
Sales engineer Daniel says, "Before we talk about duct sizing, I want to understand what you are seeing. What operating readings or product symptoms point you toward the duct, and has anything on the exhaust side changed since the dryer was installed?"
Priya says, "We added a new filter about two months ago, and moisture readings have been inconsistent since then."
Daniel says, "That timing matters. Can you send me the layout drawings and the operating data from before and after the filter change, and tell me what is involved in getting safe access to the roof for the ductwork? I also want your maintenance lead on site for the survey, since they know the install history better than either of us."
Priya agrees to pull the records and says she can have maintenance available the following week.
Notice what Daniel did not do. He did not confirm the duct is undersized, and he did not promise a fix. He asked for the two things that actually narrow the cause, the change timeline and the operating data, and he set conditions for the survey itself, access and the right person in the room.
Mistakes That Undercut Your Credibility
The biggest mistake is validating the customer's diagnosis before you have data. Saying something like that duct probably is undersized over the phone gives the customer permission to stop looking at other causes, and it puts your name on a theory you have not tested.
The second mistake is scheduling the survey without an agenda. Show up and start measuring things at random and you look unprepared, and you will likely miss the one reading that actually explains the slowdown. Set the agenda before the visit. State plainly what you will observe, dimensions, restrictions, airflow readings, and the visual condition of the duct and dampers, and state who on the plant side will review the findings afterward.
The third mistake is treating the survey as your decision to make. The plant owns any change to its process or facility. Your survey documents facts. The plant's engineers and safety owners decide what happens with those facts. If you catch yourself recommending a specific fix before the survey is even finished, stop and redirect the conversation back to what the data shows.
This same discipline, facts before conclusions, shows up in other manufacturing service calls too. Read Escalate a Dust Collector Inspection With the Right Evidence for a case where the wrong move is treating one visual observation as proof rather than a lead worth checking further.
How to Practice and Score This Conversation
If you manage a technical sales engineer, listen for three specific moments in a recording or roleplay of this call. Did the engineer ask for change history before discussing a cause. Did the engineer ask for operating data with actual dates rather than accepting a vague description like it seems slow. Did the engineer name who needs to attend the survey and what access requires, rather than just picking a date and hoping for the best.
Score the call on whether it ends with a scoped agenda instead of a promise. A strong close sounds like a short, specific rundown, spoken out loud, of what will be measured and who reviews the results. A weak close sounds like reassurance, something close to we will figure it out once we get there.
Run this scenario more than once. The pull toward agreeing with the customer's theory does not go away after one good call, it comes back the next time someone sounds confident on the phone. Practicing with an AI counterpart on DealSpeak and reviewing the score against these specific moments builds the habit faster than reading about it does.
The same preparation instinct applies past exhaust ducts. A technical sales engineer who checks part numbers and application details before quoting an electrical contact reorder, as described in Handle an Electrical Contact Reorder With Part and Application Checksis following the same rule, get the facts first.
A dryer exhaust call is won or lost before the site visit ever happens. Ask for the change history, the operating data, and the access conditions, then set a survey agenda that names what gets measured and who reviews it. The plant keeps the decision, and your job is making sure that decision rests on facts instead of a theory formed during a five minute phone call.
Practice these next
Map controls, recipe records, and interlocks before defining a mixer modernization scope.
Clarify substrate, coating, geometry, and acceptance conditions for a thickness measurement review.
A technical sales conversation for documenting machine, fluid, and interface requirements before configuration.
Collect resin, regrind, and operating facts for a bounded material handling test.
Help a technical sales engineer set a factual workshop for a heat exchanger cleaning request.
Use process loads, water conditions, and utility constraints to organize a chiller sizing review.