Green Tree Servicing: The operator I spoke with had a serious attitud...
A Green Tree Servicing customer review by GetHuman user ~C. L. from November 20th, 2017
Background on ~C. L.'s case
GetHuman: ~C. L. - can you tell our other Green Tree Servicing customers when your case took place?
~C. L.: Yes. It was afternoon, on November 16th.
GetHuman: Did you reach out to Green Tree Servicing, and if so, how?
GetHuman: And which of these common Green Tree Servicing customer issues best describes the reason you wanted to talk to them?
(Shows ~C. L. a list of common Green Tree Servicing problems)
~C. L.: "Overcharge/Strange charge" was why I was trying to call.
~C. L.'s review of Green Tree Servicing customer service
GetHuman: So how would you sum up your experience for GetHuman's Green Tree Servicing 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.
~C. L.: The operator I spoke with had a serious attitude problem. I asked multiple times for her to speak up, she would not. I asked to speak with a supervisor multiple times and was told no.
GetHuman: Let's quantify your experience contacting Green Tree Servicing. On a scale of 1 to 5, how easy is it go get help on a Green Tree Servicing problem?
~C. L.: I'd give them a one 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?
~C. L.: I'd give them a one out of five on communication.
GetHuman: And what about Green Tree Servicing's ability to quickly and effectively address your problem?
~C. L.: For that I would say five out of five.
GetHuman: And finally- any advice for other Green Tree Servicing customers?
~C. L.: Call them early in the day or late. Don't forget any personal or account information you might need for Green Tree Servicing to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~C. L. taken from his Green Tree Servicing customer service problem that occurred on November 16th, 2017.