Chase: I called with an issue on my mortgage account a...
A Chase customer review by GetHuman user ~ImAnonymous from November 15th, 2017
Background on ~ImAnonymous's case
GetHuman: ~ImAnonymous - can you tell our other Chase customers when your case took place?
~ImAnonymous: Yes. It was afternoon, on November 9th.
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 ~ImAnonymous a list of common Chase problems)
~ImAnonymous: "Card Issue" was why I was trying to call.
~ImAnonymous'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.
~ImAnonymous: I called with an issue on my mortgage account and was on hold for ** minutes and then talked to someone who didnt even know how to work her computer. I got no help, getting transferred * times and spending well over an hour and a half on the phone. I gave up and sent the CEO a letter, copying the Better Business Bureau.
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?
~ImAnonymous: I'd give them a three 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?
~ImAnonymous: I'd give them a two out of five on communication.
GetHuman: And what about Chase's ability to quickly and effectively address your problem?
~ImAnonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other Chase customers?
~ImAnonymous: 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 ~ImAnonymous taken from his Chase customer service problem that occurred on November 9th, 2017.