Macy's: Trying to order a chair that can be ordered onl...
A Macy's customer review by GetHuman user GetHuman-402982 from November 24th, 2017
Background on GetHuman-402982's case
GetHuman: GetHuman-402982 - can you tell our other Macy's customers when your case took place?
GetHuman-402982: Yeah. It was middle of the night, on November 23rd.
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 GetHuman-402982 a list of common Macy's problems)
GetHuman-402982: "Cancel order" was why I was trying to call.
GetHuman-402982'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.
GetHuman-402982: Trying to order a chair that can be ordered only by phone. Wait time on regular number was an hour when I hung up after no response other than please continue to hold. the "we will call you" number called back immediately and I was immediatly put on hold.
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?
GetHuman-402982: 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?
GetHuman-402982: I'd give them a four out of five on communication.
GetHuman: And what about Macy's's ability to quickly and effectively address your problem?
GetHuman-402982: For that I would say five out of five.
GetHuman: And finally- any advice for other Macy's customers?
GetHuman-402982: 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 GetHuman-402982 taken from his Macy's customer service problem that occurred on November 23rd, 2017.