Have you had the experience recently where you were asked to enter your email address in order to send a LinkedIn invite to someone? You might have received too many LinkedIn IDKs. So, what is an IDK exactly?
When you invite someone to connect with you on LinkedIn or receive an invite from someone, the recipient has a choice of accepting the invite or simply archiving the invite without performing any action. If the invite is accepted, the two of you become immediately connected. If the invite is archived, you can always accept the invitation at a later date. However, after you archive an invitation, there is a popup on the bottom lefthand screen of the desktop version that asks you if you know the person or not. When you respond that you don’t know the person, you are sending LinkedIn an “IDK” about that person.
IDK = I Don’t Know This Person
The “I Don’t Know This Person” (hereafter referred to as “IDK” for short) response seems innocent, right? Because you don’t know them, you’d rather not have them in your network. However, the problem is that LinkedIn looks down on these responses as they created their social networking platform for professionals to connect people who know each other but lost touch, not for open networkers. Therefore, if you receive 5 cumulative IDKs you will need to enter an E-Mail address for every invite you send. This means that if you find an old colleague and want to connect but don’t know their most recent E-Mail address, you will be unable to connect and might have to resort to text messaging.
I personally have never responded with an IDK, but I have received my share of them, even from self-professed LinkedIn LIONs and members of LinkedIn groups for open networkers. I believe it is a unwritten but understood rule that LIONs should never respond with an IDK but merely archive any invite they do not want to connect with. You never know when you may want to connect with that contact if you move to a new place or a new industry, so why not just archive it and keep the potential for connecting open? Couldn’t hurt.
As for people who are not open networkers, as I mentioned in my How to Grow Your LinkedIn Network post, you invite them at your own risk. If you do not want to receive invites, I highly recommend that you state so in your profile and/or contact details. If you do not state so, you can assume that you will receive invites. But even if you receive them, please do not punish the sender but merely archive them if you do not want to connect.
The ultimate setting for those that are annoyed by receiving too many invites from LinkedIn users is to require them to enter your email address in order to contact with you. Note that LinkedIn does realize the increased amount of invite spam and they are very clear that they will continue to restrict users who send out too many low-quality invites.
Hero photo by Gabriel Varaljay on Unsplash
LinkedIn IDK FAQs
LinkedIn allows its users to accept or decline invitation requests they get. If you decline an invitation and sends an “IDK”, that person will not be added to your network and he/she won’t be able to send you another invitation request in the future. Furthermore, the user will not know you responded “I don’t know this person” to his/her invitation. This functionality is part of LinkedIn’s user privacy protection.
IDK stands for “I don’t know this person”. LinkedIn has a feature where users have the ability to accept or decline an invitation. Meaning, users have complete control of the people they want to add to their networks. If a user receives an IDK response from another user, he/she will not be able to send another request to the same person in the future. If there is an excessive IDK’s received by the user, he/she might get restricted from sending requests to other users.
LinkedIn is committed to protecting the privacy of its users. As part of their privacy policy, senders are not notified whenever their connection request is declined by another user. It will only show the user has not accepted the request yet. Also, it won’t allow the sender to send another request to the same user anymore. LinkedIn only notifies users when their invitation request is accepted.
If your LinkedIn account gets restricted, try to find the reason first as to why it got regulated. After that, you can send a complaint to LinkedIn support or get help and suggested actions via LinkedIn help. From the same page, you can submit a support case and politely ask them if they can remove the restriction. Moving forward, you will need to be diligent in complying with LinkedIn user’s agreements to avoid further restrictions.
LinkedIn jail is the term used in the platform whenever a user’s account gets restricted. There are several reasons why your LinkedIn account may be restricted such as an uncommon number of page views; violation of the LinkedIn User Agreement; illegal and inappropriate activity in the site; abusive usage and behavior; and LinkedIn may have detected that your account is possibly hacked or compromised.
The limit of five IDKs before getting restricted has circulated on many websites including from well respected bloggers such as Stacy Zapar. But this appears to be a myth (or at least, it no longer is the case in 2014) Don’t get me wrong, getting too many IDK will get you restricted. But it takes a lot more than five for this to happen. I remember even reading one comment from a LinkedIn moderator in their forum saying that there was no such thing as being restricted after only five IDK.
I’ve joined LinkedIn last year. Like many newbies, I have been restricted. But it took me well over 50 IDK (or spam) before I was requested to plug an email address on further invitations. I don’t know exactly what is Linkedin’s criteria for getting restricted. My guess is that it could either be a ratio of IDK/Spam vs Accepted/Archived, or an absolute number (like 50 for example), or a combination of the two aforementioned.
Hey Jonathan, thanks for chiming in! Indeed, LinkedIn is always changing their platform, and considering that this post was written 6 (!) years ago, it wouldn’t surprise me if there were changes. LinkedIn has become very sophisticated with many things about their platform, and it wouldn’t surprise me if they use a number of factors in a complex algorithm before they start restricting you.
That being said, whether it’s 5 or 50 or 100, IDKs are still something to be avoided that people need to know about, so hoping that the objective of the post is still true today.
Definitely agree with you Neal. Every restriction is always a potential outcome for LinkedIn to suspend your account or even close it altogether.
Wow, I had no idea about this one, Neal ! Thanks for opening my eyes ! Will share this with my network
You’re very welcome Sarah – and thanks for sharing!
Where I can find IDK given to me. What you stated in your post http://windmillnetworking.com/2008/07/25/linkedin-i-dont-know-idk-responses-how-do-i-know-if-ive-received/Â is not working for me. The only option available for sorting sent invitations are “Newest” and “Oldest” .
Yes, the LinkedIn user interface changes all the time, and I think now it is impossible to check up on this status.
I agree that there is a problem in the nomenclature. I don't understand why LinkedIn just isn't more transparent and make it easy to accept, archive, block user, or report user for spam. Done!
The problem is the language of the buttons, they need the following:
“Accept”
“Do not accept”
“Unsolicited spam”
I think most people will recognize the hard language of “unsolicited spam” and if you attempt to connect with them through some thin commonalities, they would merely not accept your invite. This is far better language as I think “archive” comes with the concept of taking up space or creating clutter and no one wants to do that.
I agree that there is a problem in the nomenclature. I don't understand why LinkedIn just isn't more transparent and make it easy to accept, archive, block user, or report user for spam. Done!
The problem is the language of the buttons, they need the following:
“Accept”
“Do not accept”
“Unsolicited spam”
I think most people will recognize the hard language of “unsolicited spam” and if you attempt to connect with them through some thin commonalities, they would merely not accept your invite. This is far better language as I think “archive” comes with the concept of taking up space or creating clutter and no one wants to do that.
I will submit, for your consideration, that if you’re just getting into this open networking arena, that you think twice about putting a little wussy statement at the bottom of your invitation, such as “please don’t IDK me, don’t diss me, don’t get me in trouble with LinkedIn, etc.”
Would you put on your own résumé, “may not play well with others” or “I love mankind, it’s people that suck” ???!!!
This is like a cold sales call, people, and with some of your targets, you may only have one shot to make a favorable impression. Don’t waste your maximum allotted characters for your sales pitch, your request to connect, with garbage like PLEASE DON’T IDK. That’s so amateur, so self-defeating and so like what a “script kiddie” does, who doesn’t have the chops, who doesn’t know his programming or networking stuff. Send that boilerplate, that canned “professionally written” introduction from wherever you swiped it, to File 13, to your mental Trashcan, and leave it there.
[Descending from soapbox now….]
I will submit, for your consideration, that if you’re just getting into this open networking arena, that you think twice about putting a little wussy statement at the bottom of your invitation, such as “please don’t IDK me, don’t diss me, don’t get me in trouble with LinkedIn, etc.”
Would you put on your own résumé, “may not play well with others” or “I love mankind, it’s people that suck” ???!!!
This is like a cold sales call, people, and with some of your targets, you may only have one shot to make a favorable impression. Don’t waste your maximum allotted characters for your sales pitch, your request to connect, with garbage like PLEASE DON’T IDK. That’s so amateur, so self-defeating and so like what a “script kiddie” does, who doesn’t have the chops, who doesn’t know his programming or networking stuff. Send that boilerplate, that canned “professionally written” introduction from wherever you swiped it, to File 13, to your mental Trashcan, and leave it there.
[Descending from soapbox now….]