TRS Recovery Services: Pressed option to dispute check and was told to...
A TRS Recovery Services customer review by GetHuman user ~fedup from November 16th, 2017
Background on ~fedup's case
GetHuman: ~fedup - can you tell our other TRS Recovery Services customers when your case took place?
~fedup: Sure. It was morning, on November 14th.
GetHuman: Did you reach out to TRS Recovery Services, and if so, how?
GetHuman: And which of these common TRS Recovery Services customer issues best describes the reason you wanted to talk to them?
(Shows ~fedup a list of common TRS Recovery Services problems)
~fedup: "Cancel service" was why I was trying to call.
~fedup's review of TRS Recovery Services customer service
GetHuman: So how would you sum up your experience for GetHuman's TRS Recovery Services 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.
~fedup: Pressed option to dispute check and was told to call another number, called that number and got a bad fax number to send a fax to get a copy of the check I supposedly wrote
GetHuman: Let's quantify your experience contacting TRS Recovery Services. On a scale of 1 to 5, how easy is it go get help on a TRS Recovery Services problem?
~fedup: 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?
~fedup: I'd give them a one out of five on communication.
GetHuman: And what about TRS Recovery Services's ability to quickly and effectively address your problem?
~fedup: For that I would say one out of five.
GetHuman: And finally- any advice for other TRS Recovery Services customers?
~fedup: Call them early in the day or late. Don't forget any personal or account information you might need for TRS Recovery Services to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~fedup taken from his TRS Recovery Services customer service problem that occurred on November 14th, 2017.