Communication, Documentation and Customer Service
Core concepts
Technical competence fails commercially if it is not communicated. Know how to translate symptoms into plain language, explain options with cost and consequence, and set realistic expectations about repairs, parts delays and compliance obligations. Documentation includes job sheets, service reports, refrigerant usage and recovery records, commissioning data, risk assessments, permits, and handover instructions. Write objectively: what was observed, what was measured, what was done, what remains. Customer service includes arriving as arranged, protecting the premises, respecting privacy, and confirming satisfaction before leaving. Traps include promising an outcome before diagnosis, discussing one customer's site with another, recording opinions rather than measurements, and omitting the recommendation that protects the customer's compliance.
Traps
Questions often test the appropriate response to a customer who refuses a necessary safety repair. The answer is to explain the risk, document the advice, and follow your organisation's escalation policy rather than simply complying or arguing.
Worked example
A customer asks why a quote is higher than expected. Explain the measured findings, the required compliance work, and the optional efficiency items separately, then provide a written breakdown. This preserves trust and creates a record.
Rule of thumb
Write every report so a colleague who was never on site could understand the system state and the next action.