Frigidaire: I purchased a Fridgidaire stove in October of...
A Frigidaire customer review by GetHuman user ~ladysaunders724 from November 27th, 2017
Background on ~ladysaunders724's case
GetHuman: ~ladysaunders724 - can you tell our other Frigidaire customers when your case took place?
~ladysaunders724: Yup. It was middle of the night, on November 18th.
GetHuman: Did you reach out to Frigidaire, and if so, how?
GetHuman: And which of these common Frigidaire customer issues best describes the reason you wanted to talk to them?
(Shows ~ladysaunders724 a list of common Frigidaire problems)
~ladysaunders724: "Refund or cancel order" was why I was trying to call.
~ladysaunders724's review of Frigidaire customer service
GetHuman: So how would you sum up your experience for GetHuman's Frigidaire 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.
~ladysaunders724: I purchased a Fridgidaire stove in October of **** and * months later I am having a issue with the product and I'm getting a run around to get the item repaired under the * year warranty!!
GetHuman: Let's quantify your experience contacting Frigidaire. On a scale of 1 to 5, how easy is it go get help on a Frigidaire problem?
~ladysaunders724: I'd give them a three 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?
~ladysaunders724: I'd give them a one out of five on communication.
GetHuman: And what about Frigidaire's ability to quickly and effectively address your problem?
~ladysaunders724: For that I would say one out of five.
GetHuman: And finally- any advice for other Frigidaire customers?
~ladysaunders724: Call them early in the day or late. Don't forget any personal or account information you might need for Frigidaire to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ladysaunders724 taken from his Frigidaire customer service problem that occurred on November 18th, 2017.