Describe the equipment and symptom
Start with the unit type, refrigerant, operating conditions, and what the system is doing.
Built for HVAC technicians and students
Better troubleshooting starts with a better process.
ProfessAir helps you verify readings, challenge assumptions, and work through HVAC problems without jumping straight to parts changing.
Requires a ChatGPT account to use the current GPT version.
Diagnostic session
Guided
T
The unit is not cooling. Suction pressure is low.
P
What refrigerant is the system designed for, and what are the indoor and outdoor conditions?
01 Verify unit specifications
02 Gather temperatures and pressures
03 Compare readings to conditions
04 Choose the next safe test
VerifyMeasurements before conclusions
LearnUnderstand why each step matters
DiagnoseReduce guesswork and unnecessary parts
How it works
A second set of eyes without taking over the diagnosis.
ProfessAir is designed to guide the thinking process, not replace it.
Enter your actual readings
Pressures, temperatures, voltage, current, airflow, and completed checks matter more than guesses.
Work the next safe step
ProfessAir asks focused questions and helps you choose the next measurement that separates possible causes.
Why ProfessAir
Built to fight the parts-cannon mindset.
A symptom is not a diagnosis. ProfessAir pushes for equipment specifications, operating conditions, and measurements before recommending a direction.
- One or two focused questions at a time
- Safety-first troubleshooting
- Explanations that teach the reason behind each step
- Clear summaries of readings, checks, causes, and next actions
“The goal is not to give technicians the answer. It is to make getting the answer on their own better.”
— ProfessAir missionMade from field and classroom experience
ProfessAir is an independent educational project built to help HVAC technicians and students become more confident, systematic troubleshooters.
Help shape the project
Use it. Stress-test it. Tell us what broke.
Real feedback is how ProfessAir gets better. Share what worked, what was confusing, and whether the troubleshooting process led to the correct repair.
Ready to troubleshoot?