To avoid contacting the same lead twice, you need three guards, each with its own scope. Merge duplicate leads on a stable key (email first, then the LinkedIn profile). Block anyone already active in another campaign before a new campaign picks them up, and keep one sender per person inside each campaign. And keep a do-not-contact list that every campaign, channel and client checks before each send. Most tools handle the first two well inside one workspace. The third is one regulators treat as a duty, and for agencies it's the one that breaks at the client boundary.
You're probably here because a prospect wrote back: "your colleague already messaged me." It's a small line. It tells the prospect your outreach is a machine with no memory, and it tells your client the same thing if they hear about it.
Three problems that share one name
"We contacted them twice" sounds like one bug. It's three, and fixing one doesn't fix the others.
1. The same person twice in your data
This is list hygiene. One human, two rows. Maybe one came from a spreadsheet with an email and the other from a LinkedIn search with a profile URL. Each campaign sees a stranger.
The fix is to match on a key that belongs to one person. Email is the usual one. lemlist is explicit about it: "Duplicates are determined by email address." And it says why it ignores names: "Names are not used for deduplication due to their lack of uniqueness." That's the right call. Two John Smiths at two companies are not a duplicate.
The trouble starts when your sources don't share a key. A LinkedIn-sourced lead often has no email yet. A purchased list often has no profile URL. Each record passes every duplicate check, because there's nothing to compare. Before you import, add whichever key is missing, or accept that some overlap will slip through.
Scope: the record. Get this right and the next two layers have something to work with.
2. Two campaigns, or two senders, on one person
This is coordination. The record is clean, but two campaigns in the same account both decide this person fits. Or one campaign runs three LinkedIn seats and two of them write to the same VP.
Most outreach tools have a setting for this, and some turn it on by default:
- Instantly's "Check for duplicates across all Campaigns or Lists" is the default. Uncheck it and "The same lead can be added to multiple campaigns/lists".
- lemlist gives you three levels at import, from "Don't import leads that are already in this campaign" up to "Don't import leads that are already part of any campaign in your lemlist team".
- HeyReach lets you "rule out leads that received a Connection Request, InMail, or a message from any other campaign in the same Workspace", and each lead is checked "before it reaches each step".
- Smartlead has "Ignore the leads that exist in another campaign".
- HubSpot keeps it simplest: "Each contact can only be enrolled in one sequence at a time."
Read the small print on what "active" means. lemlist's middle option "excludes only leads with active statuses". So someone who finished campaign A last week can be imported into campaign B today. Sometimes that's what you want. Often it isn't, and you need your own cooldown rule on top.
Senders need a rule too. Pick one owner per person per campaign, ideally the seat already connected to them, and keep it for every step.
Scope: the workspace. That's where these settings live.
3. A person who said stop
This one isn't hygiene. It's an objection, and regulators treat it as a duty. What follows is what the regulators say, not legal advice.
The UK's ICO says an objection to direct marketing "is an absolute right and there are no exemptions or grounds for you to refuse." It says "it will be preferable to suppress their details", and that "Suppression involves retaining just enough information about them". The ICO says you must comply "without undue delay and at the latest within one month". GDPR Article 21(3) puts it in one line: "the personal data shall no longer be processed for such purposes." In the US, the FTC's CAN-SPAM guide says: "You must honor a recipient's opt-out request within 10 business days."
Notice the contrast with layer 1. Merging away a duplicate is fine. Deleting someone who objected is a mistake: you lose the record that keeps them out of the next import. You keep just enough to block them.
Some tools get this layer right. lemlist: "Unsubscriptions apply globally across all campaigns, not only the campaign where the action was triggered." And its do-not-contact status "blocks the contact from being reached on all channels across all campaigns." Instantly has a toggle that adds unsubscribed leads to its blocklist.
Scope: everyone you send for. Which, for an agency, is where it gets awkward.
The agency trap: the client boundary
Most tools stop at the workspace or the client account. Instantly calls its global blocklist "a workspace-wide feature that blocks specific email addresses or domains from being imported or contacted." HeyReach's rule covers "any other campaign in the same Workspace." lemlist's widest import option covers "your lemlist team."
Smartlead says it most plainly, and credit to them for writing it down:
"Global" refers to blocking across your own campaigns that aren't assigned to a client
And then: "it does not automatically apply across your client sub-accounts", so "you currently need to add a separate block list entry for each client individually".
That design isn't wrong. Client data should stay apart. But it means "global" usually means "global inside one client." A person who unsubscribed from client A's campaign is a fresh record in client B's workspace, run by the same agency, maybe from the same team.
Whether that's a legal problem across separate clients is a question for your lawyer. The practical fix doesn't need one:
- Keep one agency-level opt-out file: email, LinkedIn profile URL, date, which client it came from.
- Push it into every client workspace's blocklist before each launch, and on a fixed day each week.
- Treat a "stop" said to any of your clients as a stop for the agency, unless you've decided otherwise on purpose.
It's manual. It's also the layer where a mistake costs the most.
A worked example
This is an illustration with round numbers, not client data.
An agency runs two campaigns for one software client in the same week. Campaign A targets heads of sales: 600 people. Campaign B targets founders and CEOs of a similar account list: 450 people. Because founders at small companies often run sales themselves, 90 people land on both lists.
Without a cross-campaign check, 90 people get two opening messages in the same week, from two senders, about the same product. Some get a LinkedIn request from one seat and an email from another. The plan said 1,050 contacts. The client reached 960 distinct people.
With the check on, campaign B skips the 90 people already in A and picks up 90 others. Zero people get two openers. The client reaches 1,050 distinct people.
On this list, the check buys 90 extra prospects at the same send volume, and nobody writes back "your colleague already messaged me."
CampaignStack skips people already in another campaign of the same workspace by default, and a LinkedIn reply cancels every other planned touch to that person in that workspace.
Run two campaigns without overlapA checklist for each layer
Record:
- Match on email, then on the LinkedIn profile URL.
- Never merge on a name alone.
- Fill in the missing key before importing a new source.
Workspace:
- Turn on the cross-campaign check and leave it on. Turn it off on purpose, for a retargeting campaign.
- Decide what "already contacted" means: in progress only, or anyone in the last 90 days.
- One sender per person per campaign.
- When someone replies on one channel, stop the other campaigns too.
Everyone:
- One opt-out file, checked by every campaign, channel and client.
- Keep opt-outs; don't delete them.
- Process them fast. The ICO's outer limit is one month; the FTC's is 10 business days.
How CampaignStack handles each layer
CampaignStack runs LinkedIn and email outreach, and agencies usually give each client its own workspace. Here's what it does at each layer, and where it stops.
The record. When a lead comes in, it's matched against existing records on email and LinkedIn profile, and for people found on LinkedIn also on LinkedIn's own member number. A vanity URL (the readable /in/jane-doe kind) is never enough on its own to merge two existing records, because people can change them.
The workspace. Every workflow (the sequence of steps a campaign runs) has a setting called "Exclude leads active in other workflows", on by default. Its helper text says: "When enabled, leads being worked in other campaign workflows won't be sourced into this one. Disable for retargeting campaigns." It skips anyone being worked in another workflow of the same workspace, and anyone who already went through one. A workflow also never picks up its own leads a second time.
Senders. Inside a workflow, the first account that sends to a person keeps that person for the rest of that workflow. An account already connected to them is preferred.
Replies. When a lead replies on LinkedIn, every other planned touch to them in that workspace is cancelled, in any campaign, on any channel. You'll see those steps marked "Superseded - lead replied first". A booked meeting cancels every touch in the workspace too.
"Never contact these people". This list "Applies to every campaign and signal agent in this workspace" (a signal agent is an automation that reaches out when it spots a trigger, such as a job change). You can add people by hand or from a CSV, add a whole lead list, or write filter rules, including current or past company. A single campaign can't lift a workspace exclusion.
The do-not-contact register. This one covers every workspace on CampaignStack, keyed on email and LinkedIn URL. It's filled by one-click email unsubscribes and by verified objection or erasure requests sent through our public data request form. It's checked when a campaign picks someone up and again before each send. If the check can't run, the send is blocked rather than sent. It also stops that person from being added as a new lead.
What to watch out for
Set exclusions before launch. Adding someone to "Never contact these people" later stops them from being picked up by any new sourcing. But a person already enrolled in a sequence is re-checked at send time only against filter rules and the register. A name you add mid-campaign may still get the next step.
The cross-campaign check runs when a workflow picks people up, not as a lock at send time. And if you turn it off for a retargeting campaign, overlap is back on purpose. Check that the retargeting list is the one you meant.
Only a LinkedIn reply cancels other campaigns. An email reply doesn't. If someone answers your email, stop their LinkedIn steps yourself.
Two client workspaces don't coordinate with each other. In CampaignStack, nothing stops client A's workspace and client B's workspace from contacting the same person, except the register, and the register holds only unsubscribes and verified objections. A "please stop" written in a LinkedIn reply doesn't land there by itself. The agency-level opt-out file from earlier still applies.
Messages you send by hand check less. A hand-typed LinkedIn message checks the register and the people you added to "Never contact" one by one. It doesn't check people from a CSV upload or a lead list, or company and filter rules. An email you send by hand checks the register only.
Spreadsheets and LinkedIn can still split one person. Someone imported from a spreadsheet and the same person found on LinkedIn can end up as two records, if nothing ties them together. Add the profile URL to your CSV when you have it.
Takeaway
Treat "we contacted them twice" as three questions: is it the same record, the same workspace, or a person who said stop? Turn on the cross-campaign check in every client workspace this week, and set exclusions before the next launch. Then build one opt-out file for the whole agency, because most tools stop at the client boundary, and even CampaignStack's register only carries unsubscribes and verified objections.