Chase Credit Cards: been calling this number for a week and it keep...
A Chase Credit Cards customer review by GetHuman user ~anonymous from November 28th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Chase Credit Cards customers when your case took place?
~anonymous: Yes. It was morning, on November 23rd.
GetHuman: Did you reach out to Chase Credit Cards, and if so, how?
GetHuman: And which of these common Chase Credit Cards customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Chase Credit Cards problems)
~anonymous: "Dispute a Charge" was why I was trying to call.
~anonymous's review of Chase Credit Cards customer service
GetHuman: So how would you sum up your experience for GetHuman's Chase Credit 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.
~anonymous: been calling this number for a week and it keeps giving me the same message, "we are sorry, we are experiencing some technical difficulties please call again"
GetHuman: Let's quantify your experience contacting Chase Credit Cards. On a scale of 1 to 5, how easy is it go get help on a Chase Credit Cards problem?
~anonymous: I'd give them a five 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?
~anonymous: I'd give them a five out of five on communication.
GetHuman: And what about Chase Credit Cards's ability to quickly and effectively address your problem?
~anonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other Chase Credit Cards customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Chase Credit Cards to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Chase Credit Cards customer service problem that occurred on November 23rd, 2017.