LexisNexis Consumer Center: u put rong info on report then want money to ta...
A LexisNexis Consumer Center customer review by GetHuman user ~marie from November 22nd, 2017
Background on ~marie's case
GetHuman: ~marie - can you tell our other LexisNexis Consumer Center customers when your case took place?
~marie: Yes. It was morning, on November 17th.
GetHuman: Did you reach out to LexisNexis Consumer Center, and if so, how?
GetHuman: And which of these common LexisNexis Consumer Center customer issues best describes the reason you wanted to talk to them?
(Shows ~marie a list of common LexisNexis Consumer Center problems)
~marie: "Setup service" was why I was trying to call.
~marie's review of LexisNexis Consumer Center customer service
GetHuman: So how would you sum up your experience for GetHuman's LexisNexis Consumer Center 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.
~marie: u put rong info on report then want money to take it off im callin fed. trade com. tomro ur blackmailers
GetHuman: Let's quantify your experience contacting LexisNexis Consumer Center. On a scale of 1 to 5, how easy is it go get help on a LexisNexis Consumer Center problem?
~marie: 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?
~marie: I'd give them a three out of five on communication.
GetHuman: And what about LexisNexis Consumer Center's ability to quickly and effectively address your problem?
~marie: For that I would say one out of five.
GetHuman: And finally- any advice for other LexisNexis Consumer Center customers?
~marie: Call them early in the day or late. Don't forget any personal or account information you might need for LexisNexis Consumer Center to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~marie taken from his LexisNexis Consumer Center customer service problem that occurred on November 17th, 2017.