Rheem Heating & Cooling: Nobody answered. This number must be out of ord...
A Rheem Heating & Cooling customer review by GetHuman user ~Nope from November 19th, 2017
Background on ~Nope's case
GetHuman: ~Nope - can you tell our other Rheem Heating & Cooling customers when your case took place?
~Nope: Yup. It was middle of the night, on November 13th.
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 ~Nope a list of common Rheem Heating & Cooling problems)
~Nope: "Technical support" was why I was trying to call.
~Nope'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.
~Nope: Nobody answered. This number must be out of order because it kept ringing and after ** minutes it stopped and disconnected. Terrible service!!!
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?
~Nope: I'd give them a four 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?
~Nope: I'd give them a five out of five on communication.
GetHuman: And what about Rheem Heating & Cooling's ability to quickly and effectively address your problem?
~Nope: For that I would say two out of five.
GetHuman: And finally- any advice for other Rheem Heating & Cooling customers?
~Nope: 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 ~Nope taken from his Rheem Heating & Cooling customer service problem that occurred on November 13th, 2017.