Front line support is unlikely to be able to help you here. This doesn't seem like a particularly common occurrence. Here's how things typically go with weird cases like this:
1.) Support agent gets the case and says 'Uh, what do I do with this?' Escalation to team lead. 2.) Team lead reviews case and doesn't know what to do. Team lead escalates to manager. 4.) Manager reviews the case and tries to figure out the right team to send this to 5.) Manager sends it to a team. Team reviews the case. If it's the right team, they'll start investigating. 6.) If it's not the right team, the manager has to figure out another team that could be responsible for the case. 7.) Repeat 5&6 until the right team is identified
This all takes time. And assumes that the original customer support agent actually understands the issue for the security issue it is. Many frontline customer support agents are not particularly technical, so the agent may not even understand they have a security event on their hands.
Or, a PM who knows the right people to go to, offers help and things get quickly escalated.
If you were being snarky, it seems like this LinkedIn employee is trying to do the right thing. They probably don’t run support/there’s no reason to take cheap shots when they offer to help.
The problem comes when there’s no escalation path for the few cases that actually do need it. Looking at you Google.
I’ve never used LinkedIn support, so couldn’t say whether they would handle something like the OPs issue correctly.
The company actually ONLY hired people directly recommended by employees or trusted business partners. 100% of all unsolicited resumes were ignored and destroyed (yet had a paper trial for legal and EEOC compliance).
It looked like trying to scoring internet points at the expense of the person offering help.
We shouldn't be punishing the gear on the cog that is helping turn the machine in the direction it needs to go.