Chase: After the usual automated phone prompts I waite...
A Chase customer review by GetHuman user ~achasecustomer from November 21st, 2017
Background on ~achasecustomer's case
GetHuman: ~achasecustomer - can you tell our other Chase customers when your case took place?
~achasecustomer: Sure. It was afternoon, on November 15th.
GetHuman: Did you reach out to Chase, and if so, how?
GetHuman: And which of these common Chase customer issues best describes the reason you wanted to talk to them?
(Shows ~achasecustomer a list of common Chase problems)
~achasecustomer: "Dispute a Charge" was why I was trying to call.
~achasecustomer's review of Chase customer service
GetHuman: So how would you sum up your experience for GetHuman's Chase 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.
~achasecustomer: After the usual automated phone prompts I waited a few seconds while the line rang and a lady answered. She was helpful and answered my question but something didn't sit right with me. Maybe she was just too nice when I'm used to bad customer service. She also had quite a bit of an accent.
GetHuman: Let's quantify your experience contacting Chase. On a scale of 1 to 5, how easy is it go get help on a Chase problem?
~achasecustomer: 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?
~achasecustomer: I'd give them a three out of five on communication.
GetHuman: And what about Chase's ability to quickly and effectively address your problem?
~achasecustomer: For that I would say four out of five.
GetHuman: And finally- any advice for other Chase customers?
~achasecustomer: Call them early in the day or late. Don't forget any personal or account information you might need for Chase to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~achasecustomer taken from his Chase customer service problem that occurred on November 15th, 2017.