Chase: Not a native speaker and the connection was ter...
A Chase customer review by GetHuman user ~robin byers from November 12th, 2017
Background on ~robin byers's case
GetHuman: ~robin byers - can you tell our other Chase customers when your case took place?
~robin byers: Yup. It was morning, on November 6th.
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 ~robin byers a list of common Chase problems)
~robin byers: "Question" was why I was trying to call.
~robin byers'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.
~robin byers: Not a native speaker and the connection was terrible. But he got it taken care of, that's all I care about. Wish I could do this online. I travel a lot for work, hate having to tell them every time where I am.
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?
~robin byers: 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?
~robin byers: I'd give them a five out of five on communication.
GetHuman: And what about Chase's ability to quickly and effectively address your problem?
~robin byers: For that I would say one out of five.
GetHuman: And finally- any advice for other Chase customers?
~robin byers: 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 ~robin byers taken from his Chase customer service problem that occurred on November 6th, 2017.