Macy's Credit Card: I had misplaced my card and needed it replaced...
A Macy's Credit Card customer review by GetHuman user ~Satisfied from November 26th, 2017
Background on ~Satisfied's case
GetHuman: ~Satisfied - can you tell our other Macy's Credit Card customers when your case took place?
~Satisfied: Sure. It was morning, on November 19th.
GetHuman: Did you reach out to Macy's Credit Card, and if so, how?
GetHuman: And which of these common Macy's Credit Card customer issues best describes the reason you wanted to talk to them?
(Shows ~Satisfied a list of common Macy's Credit Card problems)
~Satisfied: "Lower my rate" was why I was trying to call.
~Satisfied's review of Macy's Credit Card customer service
GetHuman: So how would you sum up your experience for GetHuman's Macy's Credit Card 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.
~Satisfied: I had misplaced my card and needed it replaced...store had some problems doing so. Credit dept was xlnt in handling the problem, while not compromising my security.
GetHuman: Let's quantify your experience contacting Macy's Credit Card. On a scale of 1 to 5, how easy is it go get help on a Macy's Credit Card problem?
~Satisfied: 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?
~Satisfied: I'd give them a one out of five on communication.
GetHuman: And what about Macy's Credit Card's ability to quickly and effectively address your problem?
~Satisfied: For that I would say five out of five.
GetHuman: And finally- any advice for other Macy's Credit Card customers?
~Satisfied: Call them early in the day or late. Don't forget any personal or account information you might need for Macy's Credit Card to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Satisfied taken from his Macy's Credit Card customer service problem that occurred on November 19th, 2017.