ScoreSense: This company is a SCAM! Their 'Disclosure' stmt...
A ScoreSense customer review by GetHuman user ~anon from November 17th, 2017
Background on ~anon's case
GetHuman: ~anon - can you tell our other ScoreSense customers when your case took place?
~anon: Yup. It was middle of the night, on November 14th.
GetHuman: Did you reach out to ScoreSense, and if so, how?
GetHuman: And which of these common ScoreSense customer issues best describes the reason you wanted to talk to them?
(Shows ~anon a list of common ScoreSense problems)
~anon: "Fix credit score" was why I was trying to call.
~anon's review of ScoreSense customer service
GetHuman: So how would you sum up your experience for GetHuman's ScoreSense 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.
~anon: This company is a SCAM! Their 'Disclosure' stmt seems to imply u can cancel IF u don't want a membership. But since I didn't realize I was AUTOMATICALLY enrolled I didn't think I had to do anything....until I received this $**.** charge on my account. I have been on the phone with them every day since and still not refunded.
GetHuman: Let's quantify your experience contacting ScoreSense. On a scale of 1 to 5, how easy is it go get help on a ScoreSense problem?
~anon: 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?
~anon: I'd give them a one out of five on communication.
GetHuman: And what about ScoreSense's ability to quickly and effectively address your problem?
~anon: For that I would say three out of five.
GetHuman: And finally- any advice for other ScoreSense customers?
~anon: Call them early in the day or late. Don't forget any personal or account information you might need for ScoreSense to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anon taken from his ScoreSense customer service problem that occurred on November 14th, 2017.