LinkedIn: I've been trying to call for * *** days now on...
A LinkedIn customer review by GetHuman user GetHuman-19983 from November 24th, 2017
Background on GetHuman-19983's case
GetHuman: GetHuman-19983 - can you tell our other LinkedIn customers when your case took place?
GetHuman-19983: Yup. It was evening, on November 16th.
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 GetHuman-19983 a list of common LinkedIn problems)
GetHuman-19983: "Complaint" was why I was trying to contact.
GetHuman-19983'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.
GetHuman-19983: I've been trying to call for * *** days now on every time I call it's nothing but a busy signal all I want to do is cancel my free time limited premium account some things of come up I can't afford a piece of bubble gum right now please help me Steven McKee
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?
GetHuman-19983: I'd give them a four 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-19983: I'd give them a three out of five on communication.
GetHuman: And what about LinkedIn's ability to quickly and effectively address your problem?
GetHuman-19983: For that I would say one out of five.
GetHuman: And finally- any advice for other LinkedIn customers?
GetHuman-19983: 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 GetHuman-19983 taken from his LinkedIn customer service problem that occurred on November 16th, 2017.