5 Things to Tell Your Technician Before a Service Visit

A service visit has a fixed window of time. The technician needs to understand the situation, locate the problem, and fix it — all within that window. When they arrive cold, the first portion of the visit goes to questions and exploration. When they arrive with context, they can move straight to verification and repair.

This is not about doing the technician's job for them. It is about giving them a head start. A homeowner who says the bedroom unit has been dripping for a week gives the technician a different starting point than one who says the aircon is not working. Specifics save time and improve outcomes for both sides.

A problem that started yesterday is different from one that has been building for months. Timeline tells the technician whether they are dealing with a sudden failure or a gradual decline. Sudden changes point to specific failure modes — cooling stopped overnight, or water appeared where there was none before. Gradual changes suggest wear, fouling, or slow leaks.

Be as specific as you can. Did the dripping start after a heavy rain? Did the cooling weaken gradually over weeks or drop off sharply? Did the noise appear after a power trip? These details narrow the diagnostic path before the technician even opens a panel.

In a multi-split system, knowing which indoor units are affected changes the diagnosis entirely. If only one unit has a problem, the cause is likely specific to that unit — a clogged drain, a dirty coil, or a faulty sensor. If all units are underperforming, the issue may sit with the outdoor unit or the shared refrigerant circuit.

Homeowners sometimes report a general complaint — the aircon is not cold — without specifying which rooms. The technician then has to test each unit individually to find the pattern. Telling them upfront that the living room unit is fine but the master bedroom unit drips water saves diagnostic time and keeps the visit focused.

Renovation work — painting, hacking, ceiling work, or even heavy cleaning — can disturb aircon components in ways that are not obvious. Dust from hacking enters the unit and clogs the coil. Ceiling work can shift the drain pipe gradient. Painting near the unit can coat the filter or air intake with fine particles.

If any work happened near the aircon in the weeks before the problem started, mention it. The technician will check for physical disturbance — a shifted drain pipe, a knocked sensor, or debris inside the unit — before assuming a component failure. This avoids misdiagnosis and unnecessary part replacement.

Service history gives the technician context. If the unit was serviced recently and the problem appeared right after, the service itself may be related. A drain not reconnected properly, a filter not seated correctly, or a panel not closed fully can all cause new symptoms. If the unit has not been serviced in a long time, that tells a different story.

Share whatever records you have. A service report, a receipt, or even a text message confirming the last visit date is useful. If you had a chemical wash done and the problem appeared afterward, that narrows the investigation significantly. The technician does not need a full history — just the most recent service and what was covered.

If you are calling for a second opinion, say so upfront. Tell the technician what the previous contractor diagnosed and what they recommended. This is not about challenging either side — it is about giving the second technician a starting point so they can confirm or disagree based on their own assessment.

A technician who knows you were told the PCB needs replacing will check the PCB specifically and either confirm the diagnosis or find a different root cause. Without that context, they may go through the entire diagnostic path from scratch, which takes longer and costs more. Transparency helps everyone.

You do not need to write a report. A short message when you book — or a quick voice note — covering the timeline, affected units, and any recent work is enough. Photos help too, especially for visible issues like water stains, ice on pipes, or error codes on the display.

The goal is to give the technician enough context to arrive prepared. Even partial information is better than none. A technician who knows the bedroom unit has been dripping for a week and the unit was serviced last month has a clear starting point. That head start often means the difference between a resolved visit and a follow-up.