One Tuesday in Phoenix broke my service call average record in the worst way

I had this Tuesday in Phoenix last March where I ran 9 calls and every single one had some goofy thermostat issue that looked like a bad compressor on paper. The dispatch data showed high pressure faults across the board, but when I actually got there, three of them were just dead AA batteries in the wireless sensors, and two were from a neighbor's new ham radio setup throwing interference. I spent 6 hours driving between the same five zip codes, and my average call time went from 45 minutes to almost 2 hours because I kept double checking my gauges against the readings. What really got me was the last job, a commercial unit near the airport, where the building manager swore the log showed a 14 degree split that just vanished overnight. Turns out their maintenance guy had typed in the wrong date range on the chart, so the whole anomaly was just a data entry glitch from two weeks prior. Has anyone else had a day where the numbers looked cursed but the actual fix was boring and simple, or is it just me and Phoenix heat making me paranoid?

0 comments

0 Comments

No comments yet

Be the first to share your thoughts on this discussion.