Credit Karma: how to fix the login issues is very bad and fru...
A Credit Karma customer review by GetHuman user GetHuman-20060 from November 27th, 2017
Background on GetHuman-20060's case
GetHuman: GetHuman-20060 - can you tell our other Credit Karma customers when your case took place?
GetHuman-20060: Yes I can. It was middle of the night, on November 25th.
GetHuman: Did you reach out to Credit Karma, and if so, how?
GetHuman: And which of these common Credit Karma customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-20060 a list of common Credit Karma problems)
GetHuman-20060: "Account Access" was why I was trying to contact.
GetHuman-20060's review of Credit Karma customer service
GetHuman: So how would you sum up your experience for GetHuman's Credit Karma 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.
GetHuman-20060: how to fix the login issues is very bad and frustrated, credit karma should add to there site a phone number and stop advertising there self so professional went they not
GetHuman: Let's quantify your experience contacting Credit Karma. On a scale of 1 to 5, how easy is it go get help on a Credit Karma problem?
GetHuman-20060: 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?
GetHuman-20060: I'd give them a one out of five on communication.
GetHuman: And what about Credit Karma's ability to quickly and effectively address your problem?
GetHuman-20060: For that I would say two out of five.
GetHuman: And finally- any advice for other Credit Karma customers?
GetHuman-20060: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Credit Karma to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-20060 taken from his Credit Karma customer service problem that occurred on November 25th, 2017.