Chase Home Finance: the most miserable sob's on the face of the ear...
A Chase Home Finance customer review by GetHuman user ~chasevictim from November 1st, 2017
Background on ~chasevictim's case
GetHuman: ~chasevictim - can you tell our other Chase Home Finance customers when your case took place?
~chasevictim: Yeah. It was afternoon, on October 27th.
GetHuman: Did you reach out to Chase Home Finance, and if so, how?
GetHuman: And which of these common Chase Home Finance customer issues best describes the reason you wanted to talk to them?
(Shows ~chasevictim a list of common Chase Home Finance problems)
~chasevictim: "Extension" was why I was trying to call.
~chasevictim's review of Chase Home Finance customer service
GetHuman: So how would you sum up your experience for GetHuman's Chase Home Finance 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.
~chasevictim: the most miserable sob's on the face of the earth. cant speak english, are DENSE, spend time with "sing-song" disclaimers, refuse to listen
GetHuman: Let's quantify your experience contacting Chase Home Finance. On a scale of 1 to 5, how easy is it go get help on a Chase Home Finance problem?
~chasevictim: 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?
~chasevictim: I'd give them a three out of five on communication.
GetHuman: And what about Chase Home Finance's ability to quickly and effectively address your problem?
~chasevictim: For that I would say five out of five.
GetHuman: And finally- any advice for other Chase Home Finance customers?
~chasevictim: Call them early in the day or late. Don't forget any personal or account information you might need for Chase Home Finance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~chasevictim taken from his Chase Home Finance customer service problem that occurred on October 27th, 2017.