Citi Cards: had to speak to six reps before being told they...
A Citi Cards customer review by GetHuman user GetHuman-325182 from November 4th, 2017
Background on GetHuman-325182's case
GetHuman: GetHuman-325182 - can you tell our other Citi Cards customers when your case took place?
GetHuman-325182: Yeah. It was middle of the night, on November 2nd.
GetHuman: Did you reach out to Citi Cards, and if so, how?
GetHuman: And which of these common Citi Cards customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-325182 a list of common Citi Cards problems)
GetHuman-325182: "Points Redemption" was why I was trying to call.
GetHuman-325182's review of Citi Cards customer service
GetHuman: So how would you sum up your experience for GetHuman's Citi Cards 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-325182: had to speak to six reps before being told they couldn't unlock my internet access (first rep said that I called wrong number for citi business cards, even though that is the number on the card!)
GetHuman: Let's quantify your experience contacting Citi Cards. On a scale of 1 to 5, how easy is it go get help on a Citi Cards problem?
GetHuman-325182: I'd give them a four 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-325182: I'd give them a five out of five on communication.
GetHuman: And what about Citi Cards's ability to quickly and effectively address your problem?
GetHuman-325182: For that I would say four out of five.
GetHuman: And finally- any advice for other Citi Cards customers?
GetHuman-325182: Call them early in the day or late. Don't forget any personal or account information you might need for Citi Cards to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-325182 taken from his Citi Cards customer service problem that occurred on November 2nd, 2017.