Kohls.com: The woman that answered my call was not helpful...
A Kohls.com customer review by GetHuman user ~anonymous from November 25th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Kohls.com customers when your case took place?
~anonymous: Sure. It was afternoon, on November 20th.
GetHuman: Did you reach out to Kohls.com, and if so, how?
GetHuman: And which of these common Kohls.com customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Kohls.com problems)
~anonymous: "Complaint" was why I was trying to call.
~anonymous's review of Kohls.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Kohls.com 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.
~anonymous: The woman that answered my call was not helpful at all. Asked to speak to a supervisor and she kept telling me that I could not and the answer would be the same. Waited ** minutes and supervisor never answered. Phone was hung up on Kohls end. During the wait I heard talking to other people.
GetHuman: Let's quantify your experience contacting Kohls.com. On a scale of 1 to 5, how easy is it go get help on a Kohls.com problem?
~anonymous: 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?
~anonymous: I'd give them a one out of five on communication.
GetHuman: And what about Kohls.com's ability to quickly and effectively address your problem?
~anonymous: For that I would say four out of five.
GetHuman: And finally- any advice for other Kohls.com customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Kohls.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Kohls.com customer service problem that occurred on November 20th, 2017.