LinkedIn: I have had an issue with not being able to acce...
A LinkedIn customer review by GetHuman user ~Lisa Fenton from November 26th, 2017
Background on ~Lisa Fenton's case
GetHuman: ~Lisa Fenton - can you tell our other LinkedIn customers when your case took place?
~Lisa Fenton: Yes. It was late at night, on November 19th.
GetHuman: Did you reach out to LinkedIn, and if so, how?
GetHuman: And which of these common LinkedIn customer issues best describes the reason you wanted to talk to them?
(Shows ~Lisa Fenton a list of common LinkedIn problems)
~Lisa Fenton: "Refund a Charge" was why I was trying to contact.
~Lisa Fenton's review of LinkedIn customer service
GetHuman: So how would you sum up your experience for GetHuman's LinkedIn 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.
~Lisa Fenton: I have had an issue with not being able to access my account for ** months. No one is resolving this and I have provided LinkedIN with my personal detailed information of DL and SS Number. This is the worse customer experience I have had.
GetHuman: Let's quantify your experience contacting LinkedIn. On a scale of 1 to 5, how easy is it go get help on a LinkedIn problem?
~Lisa Fenton: 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?
~Lisa Fenton: I'd give them a one out of five on communication.
GetHuman: And what about LinkedIn's ability to quickly and effectively address your problem?
~Lisa Fenton: For that I would say three out of five.
GetHuman: And finally- any advice for other LinkedIn customers?
~Lisa Fenton: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for LinkedIn to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Lisa Fenton taken from his LinkedIn customer service problem that occurred on November 19th, 2017.