Michael Kors: The representative's comment is as follows:* "I...
A Michael Kors customer review by GetHuman user GetHuman-44397 from November 17th, 2017
Background on GetHuman-44397's case
GetHuman: GetHuman-44397 - can you tell our other Michael Kors customers when your case took place?
GetHuman-44397: Yeah. It was morning, on November 8th.
GetHuman: Did you reach out to Michael Kors, and if so, how?
GetHuman: And which of these common Michael Kors customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-44397 a list of common Michael Kors problems)
GetHuman-44397: "Change order" was why I was trying to call.
GetHuman-44397's review of Michael Kors customer service
GetHuman: So how would you sum up your experience for GetHuman's Michael Kors 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.
GetHuman-44397: The representative's comment is as follows:* "I apologize for your disappointment.*Nomita Momin: Please feel free to email your questions to our Corporate office at *****@***.com or call *-***-***-****.
GetHuman: Let's quantify your experience contacting Michael Kors. On a scale of 1 to 5, how easy is it go get help on a Michael Kors problem?
GetHuman-44397: I'd give them a two 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?
GetHuman-44397: I'd give them a three out of five on communication.
GetHuman: And what about Michael Kors's ability to quickly and effectively address your problem?
GetHuman-44397: For that I would say one out of five.
GetHuman: And finally- any advice for other Michael Kors customers?
GetHuman-44397: Call them early in the day or late. Don't forget any personal or account information you might need for Michael Kors to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-44397 taken from his Michael Kors customer service problem that occurred on November 8th, 2017.