Guide
How to stop your recruiting team from messaging the same LinkedIn candidate twice
The most reliable way to stop two recruiters messaging the same LinkedIn candidate is to make "already contacted" visible at the moment someone is about to write, rather than in a separate document they have to remember to open. Shared sheets and ATS notes work if everyone logs every message. Team LinkedIn Recruiter contracts have some built-in visibility for colleagues on the same contract, but not every Recruiter plan has it. A browser extension such as YellowSync marks contacted profiles directly on LinkedIn.
Why it happens
Two recruiters on the same team search for the same role, find the same strong profile, and each send a message a few days apart. Neither did anything wrong: the first message lives in one person's inbox, and nothing on the profile tells the second person that a colleague already reached out. The problem grows with team size, with the number of open roles that overlap, and with how many tools people search from (LinkedIn, Recruiter, Sales Navigator, sourcing lists).
This is called candidate collision.
What it costs
- The candidate receives two messages from the same company without any coordination, which can read as disorganised.
- If the two messages describe different roles or tones, the candidate may not know who to answer.
- Employer brand takes the hit: candidates talk, and a poor first impression is hard to undo.
- Recruiter time is spent twice on the same person.
The real options, with honest trade-offs
1. A shared spreadsheet
How it works: everyone adds a row (candidate link, who, when) after messaging, and checks the sheet before messaging.
Pros: free or already included in your office suite, no setup beyond agreeing on columns, anyone can understand it.
Cons: it depends entirely on discipline. The check and the entry are manual steps outside LinkedIn, so they are the first thing skipped on a busy day. Profile links come in several formats, which makes searching the sheet unreliable. A sheet that holds candidate names and links is also personal data you now have to manage.
2. Notes, tags or activity in an ATS
How it works: the contact is logged as a note, tag, status or activity on the candidate record in your applicant tracking system.
Pros: one system of record for the whole pipeline, searchable, with permissions and history you may already rely on.
Cons: what an ATS records varies a lot. Some ATS let you log outreach as notes or tags and some also record messages sent through the ATS itself, but messages typed directly in LinkedIn are usually only recorded if someone logs them or a connector captures them. Check what your own ATS does. The record also sits in the ATS, so the recruiter has to leave LinkedIn to look it up before writing.
3. LinkedIn Recruiter's own features
What LinkedIn documents:
- In its InMail FAQ for Recruiter, LinkedIn's help center describes a warning on team Recruiter contracts when a colleague on the same contract contacted the candidate in the same calendar month. It isn't available on Recruiter Lite or on every team plan, and it doesn't cover regular LinkedIn or Sales Navigator.
- On its candidate profiles page, LinkedIn describes a Messages tab with message history, a Recruiting activity tab showing activity that recruiters on the same contract have taken on the profile, and tools such as notes, reminders, tags and custom fields. Which of these you get, and how much of a teammate's activity is visible, depends on your Recruiter plan and contract.
Pros: built into the tool, no extra install, and on a team contract it works across the seats on that contract.
Cons: it depends on your plan. The documented warning applies to team Recruiter contracts, only for colleagues on the same contract, and only for contact in the same calendar month. It isn't available on Recruiter Lite, where there are no colleagues on the contract, or on every team plan. Teammates who work from regular LinkedIn or Sales Navigator accounts are outside it. Check in LinkedIn's help center how it behaves for your plan and message types.
4. A browser extension such as YellowSync
How it works: when a teammate sends a message to someone on LinkedIn, LinkedIn Recruiter or Sales Navigator, YellowSync marks that profile in yellow on every computer in the team that has the extension. Hovering the mark shows who made the contact and when. Marks expire (180 days by default, configurable by the organisation), so old outreach does not block new outreach.
What it does not do: YellowSync only marks profiles. It does not send messages, connect, visit profiles, scroll, scrape or export anything on your behalf, and it does not block the message button. You decide whether to write.
Pros: the information is on the profile, where the decision is made. No manual logging, and it covers colleagues using different LinkedIn products.
Cons: it is a Chrome extension, so each teammate must install it in Chrome. The shared list refreshes within a minute, not instantly. It detects that a message was sent, not that it was delivered. Profile and Recruiter identifiers use different formats, so the same person seen through two different views is not always recognised as one. Marks come only from people on your team using the extension, so contact made outside it (another browser, a phone) is not seen. It costs 9.40 EUR per computer per month after the free trial.
Privacy: the extension converts each profile identifier into a keyed hash on your computer before it reaches YellowSync's server. The server stores that hash, the author and the date, not candidate names and not message content.
How to choose
- Small team, few overlapping roles: a disciplined shared sheet may be enough.
- Everything already runs through an ATS: use its notes or tags and agree one convention.
- Everyone is on one team Recruiter contract: start with the built-in warning and activity views, and learn their limits. On Recruiter Lite, or on a team plan without the warning, use something else.
- Mixed products, high overlap, little time for logging: a marker on the profile removes the manual step.
The tools can be combined. See the side-by-side comparison.
Habits that help with any option
- Decide who owns a candidate for a role, and what happens when two roles overlap.
- Set an expiry: after how long is it fine to contact someone again?
- Record the contact when you send it, not at the end of the day.
- Do not store more candidate data than you need to answer one question: "has someone on my team already written to this person?"
Frequently asked questions
What is the simplest way to avoid messaging the same candidate twice?
Make past contact visible where recruiters work, before they write. A shared sheet or ATS notes can do it if everyone logs every message; a browser extension such as YellowSync marks contacted profiles on LinkedIn without manual logging.
Does LinkedIn Recruiter warn me when a colleague already contacted a candidate?
Only on some plans. LinkedIn's help center describes a warning on team Recruiter contracts when a colleague on the same contract contacted the candidate in the same calendar month. It isn't available on Recruiter Lite or on every team plan, and it doesn't cover regular LinkedIn or Sales Navigator.
Does YellowSync send messages or collect candidate data?
No. YellowSync only marks profiles. It never sends messages, connects, visits profiles, scrapes or exports data. Its server stores a keyed hash of the profile identifier, the author and the date, not candidate names or message content.
How long should a contacted flag last?
There is no universal rule; it is a team policy. YellowSync marks expire after 180 days by default and the organisation can change this, so old outreach does not block new outreach.