GE Appliances: The person was was competent in the subject mat...
A GE Appliances customer review by GetHuman user ~jersey girl from November 28th, 2017
Background on ~jersey girl's case
GetHuman: ~jersey girl - can you tell our other GE Appliances customers when your case took place?
~jersey girl: Yes. It was late at night, on November 22nd.
GetHuman: Did you reach out to GE Appliances, and if so, how?
GetHuman: And which of these common GE Appliances customer issues best describes the reason you wanted to talk to them?
(Shows ~jersey girl a list of common GE Appliances problems)
~jersey girl: "Repairs" was why I was trying to call.
~jersey girl's review of GE Appliances customer service
GetHuman: So how would you sum up your experience for GetHuman's GE Appliances 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.
~jersey girl: The person was was competent in the subject matter. She gave me some options for a difficult problem but she gave me a definitive answer so I could stop wasting time looking for something that was not there.
GetHuman: Let's quantify your experience contacting GE Appliances. On a scale of 1 to 5, how easy is it go get help on a GE Appliances problem?
~jersey girl: I'd give them a five 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?
~jersey girl: I'd give them a four out of five on communication.
GetHuman: And what about GE Appliances's ability to quickly and effectively address your problem?
~jersey girl: For that I would say five out of five.
GetHuman: And finally- any advice for other GE Appliances customers?
~jersey girl: Call them early in the day or late. Don't forget any personal or account information you might need for GE Appliances to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jersey girl taken from his GE Appliances customer service problem that occurred on November 22nd, 2017.