Rheem Heating & Cooling: I asked a question that any technical assistanc...
A Rheem Heating & Cooling customer review by GetHuman user ~ted from November 28th, 2017
Background on ~ted's case
GetHuman: ~ted - can you tell our other Rheem Heating & Cooling customers when your case took place?
~ted: Yes I can. It was afternoon, on November 23rd.
GetHuman: Did you reach out to Rheem Heating & Cooling, and if so, how?
GetHuman: And which of these common Rheem Heating & Cooling customer issues best describes the reason you wanted to talk to them?
(Shows ~ted a list of common Rheem Heating & Cooling problems)
~ted: "Repairs" was why I was trying to call.
~ted's review of Rheem Heating & Cooling customer service
GetHuman: So how would you sum up your experience for GetHuman's Rheem Heating & Cooling customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~ted: I asked a question that any technical assistance person should be able to answer. All I got was ask your installer. The installer doesn't or won't admit knowing.
GetHuman: Let's quantify your experience contacting Rheem Heating & Cooling. On a scale of 1 to 5, how easy is it go get help on a Rheem Heating & Cooling problem?
~ted: I'd give them a one out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~ted: I'd give them a one out of five on communication.
GetHuman: And what about Rheem Heating & Cooling's ability to quickly and effectively address your problem?
~ted: For that I would say five out of five.
GetHuman: And finally- any advice for other Rheem Heating & Cooling customers?
~ted: Call them early in the day or late. Don't forget any personal or account information you might need for Rheem Heating & Cooling to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ted taken from his Rheem Heating & Cooling customer service problem that occurred on November 23rd, 2017.