Kenmore: I spoke with * different people including * sup...
A Kenmore customer review by GetHuman user ~sues2u2 from November 22nd, 2017
Background on ~sues2u2's case
GetHuman: ~sues2u2 - can you tell our other Kenmore customers when your case took place?
~sues2u2: Yeah. It was middle of the night, on November 19th.
GetHuman: Did you reach out to Kenmore, and if so, how?
GetHuman: And which of these common Kenmore customer issues best describes the reason you wanted to talk to them?
(Shows ~sues2u2 a list of common Kenmore problems)
~sues2u2: "Warranty claim" was why I was trying to call.
~sues2u2's review of Kenmore customer service
GetHuman: So how would you sum up your experience for GetHuman's Kenmore 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.
~sues2u2: I spoke with * different people including * supervisors. * of the people spoke English without a foreign accent. All * had thick accents that made it hard to understand although the * supervisor tried to enunciate clearly. Im still waiting for help with my problem * days later even though the last supervisor said they would call back.
GetHuman: Let's quantify your experience contacting Kenmore. On a scale of 1 to 5, how easy is it go get help on a Kenmore problem?
~sues2u2: 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?
~sues2u2: I'd give them a four out of five on communication.
GetHuman: And what about Kenmore's ability to quickly and effectively address your problem?
~sues2u2: For that I would say three out of five.
GetHuman: And finally- any advice for other Kenmore customers?
~sues2u2: Call them early in the day or late. Don't forget any personal or account information you might need for Kenmore to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~sues2u2 taken from his Kenmore customer service problem that occurred on November 19th, 2017.