Ocwen: All I wanted to do was make a principal-only pa...
A Ocwen customer review by GetHuman user ~ColoradoRock from November 18th, 2017
Background on ~ColoradoRock's case
GetHuman: ~ColoradoRock - can you tell our other Ocwen customers when your case took place?
~ColoradoRock: Yes I can. It was afternoon, on November 12th.
GetHuman: Did you reach out to Ocwen, and if so, how?
GetHuman: And which of these common Ocwen customer issues best describes the reason you wanted to talk to them?
(Shows ~ColoradoRock a list of common Ocwen problems)
~ColoradoRock: "Refund" was why I was trying to call.
~ColoradoRock's review of Ocwen customer service
GetHuman: So how would you sum up your experience for GetHuman's Ocwen 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.
~ColoradoRock: All I wanted to do was make a principal-only payment on a current loan. It is not possible to do that on their ****'s-style web site. To do it over the phone I had to give them my account info today, and then call back again tomorrow (another ** mins wait?) to tell them how to apply the payment. Ridiculous.
GetHuman: Let's quantify your experience contacting Ocwen. On a scale of 1 to 5, how easy is it go get help on a Ocwen problem?
~ColoradoRock: I'd give them a two 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?
~ColoradoRock: I'd give them a one out of five on communication.
GetHuman: And what about Ocwen's ability to quickly and effectively address your problem?
~ColoradoRock: For that I would say four out of five.
GetHuman: And finally- any advice for other Ocwen customers?
~ColoradoRock: Call them early in the day or late. Don't forget any personal or account information you might need for Ocwen to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ColoradoRock taken from his Ocwen customer service problem that occurred on November 12th, 2017.