Macy's: Karl Benedict A. was probably the only person w...
A Macy's customer review by GetHuman user ~lam from November 19th, 2017
Background on ~lam's case
GetHuman: ~lam - can you tell our other Macy's customers when your case took place?
~lam: Yup. It was morning, on November 13th.
GetHuman: Did you reach out to Macy's, and if so, how?
GetHuman: And which of these common Macy's customer issues best describes the reason you wanted to talk to them?
(Shows ~lam a list of common Macy's problems)
~lam: "Cancel order" was why I was trying to call.
~lam's review of Macy's customer service
GetHuman: So how would you sum up your experience for GetHuman's Macy's 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.
~lam: Karl Benedict A. was probably the only person who took care of my needs and questions unlike some of the others I have had no luck with. Karl really acknowledges your concerns and goes out of his way doing his best to fulfill them. Karl was kind, patient, and very helpful. If it wasn't for him, I would have given this site * stars. Thank you for taking some time out of your day Karl! I very much appreciated it.
GetHuman: Let's quantify your experience contacting Macy's. On a scale of 1 to 5, how easy is it go get help on a Macy's problem?
~lam: 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?
~lam: I'd give them a one out of five on communication.
GetHuman: And what about Macy's's ability to quickly and effectively address your problem?
~lam: For that I would say one out of five.
GetHuman: And finally- any advice for other Macy's customers?
~lam: Call them early in the day or late. Don't forget any personal or account information you might need for Macy's to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~lam taken from his Macy's customer service problem that occurred on November 13th, 2017.