On April **,**** my LinkedIn account was hacked. A solicitation email was sent to all o...

GetHuman641515's customer service issue with LinkedIn from April 2018

Help with my LinkedIn issue
On April **,**** my LinkedIn account was hacked. A solicitation email was sent to all of my almost *,*** connections. I did my best to alert those who received that communication to tell them that it was a hacked generated email. My account was shut down soon after. That experience is bothersome to me. What I find most troubling is that two LinkedIn members responded to that erroneous email with an obscenity and a homo***ual slur. Jason Fiehrer of Ohio and Greg Ingle of Indiana are the two responsible for the hateful speech. I find it troubling that two individuals would think such hateful speech would be appropriate on the LinkedIn site. I ask what course of action LinkedIn will take to respond to these two individuals? I look forward to your response. Thank you! Ted Toole *****@***.com
I trust that LinkedIn will make this right and come up with a resolution that is fair.
Help with my LinkedIn issue
Do you have a customer issue as well?
We can help you get LinkedIn's attention and get better help faster. Tap below to get started.
Having LinkedIn issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would LinkedIn email you?
This email address isn't valid

LinkedIn

Customer service issue
Reported by GetHuman641515
Apr 30th, 2018 - 3 mons ago
I have an issue with LinkedIn too
Not resolved
Seen by 45 customers so far
Similar issue to 6788 others
0 customers following this
Items needed
Username
Email on Account
Phone Number
Name of Account Holder
Timeline
GetHuman641515 started working on this issue
Apr 30th 1:51pm
GetHuman641515 indicated the issue is not fixed yet.
Apr 30th 6:46pm
GetHuman641515 indicated the issue is not fixed yet.
Apr 30th 7:03pm
GetHuman641515 indicated the issue is not fixed yet.
Apr 30th 11:45pm
GetHuman641515 indicated the issue is not fixed yet.
May 1st 1:36pm
GetHuman641515 indicated the issue is not fixed yet.
May 2nd 4:23pm
GetHuman641515 indicated the issue is not fixed yet.
May 2nd 7:39pm
GetHuman641515 indicated the issue is not fixed yet.
May 2nd 8:22pm
GetHuman641515 indicated the issue is not fixed yet.
May 3rd 12:54am
GetHuman641515 indicated the issue is not fixed yet.
May 3rd 1:26pm
GetHuman641515 indicated the issue is not fixed yet.
May 3rd 2:59pm
GetHuman641515 indicated the issue is not fixed yet.
May 3rd 3:00pm
GetHuman641515 indicated the issue is not fixed yet.
May 4th 8:19am
GetHuman641515 indicated the issue is not fixed yet.
May 4th 10:31pm
GetHuman641515 indicated the issue is not fixed yet.
May 6th 10:55pm
GetHuman641515 indicated the issue is not fixed yet.
May 6th 10:55pm