The short answer: To stop two teammates messaging the same lead, keep each lead with one sender, allow one live campaign per lead, and stop the lead everywhere when it replies. Our tool does all three: a lead goes to the sender with the most weekly room left and stays there, and a reply ends the lead in every campaign.

We make a tool that runs one campaign from several people’s LinkedIn accounts, so this is the problem it exists to solve. This page says what it does and where it can’t see.

How does a lead stay with one teammate?

When a campaign has several senders, each lead is given to the sender with the most weekly capacity left, and keeps that sender for the whole sequence. The person hears from one account, and the connection request, the follow-up and the reply all come from the same name. Sender rotation explains the choice.

If a sender is disconnected or paused, its leads wait. Leads it hasn’t contacted yet can be given to another sender, one at a time. Leads already contacted stay, so the same person follows up once the account is back.

Can two campaigns message the same person?

No. A lead can be live in only one campaign at a time, and the database enforces it. A lead added to a second campaign while it is live in the first is skipped, and the campaign shows the reason. One lead per workspace also means importing the same person twice updates the lead and doesn’t create a second one, even from two lists.

What happens when a lead replies?

The lead stops in every campaign, and the reply shows in the shared inbox and on the lead’s timeline. Nobody gets a follow-up after answering. Any teammate in the workspace can answer as the sender the lead was talking to. The inbox covers every sender’s replies in one place.

What if someone already talked to the lead?

Campaigns exclude leads who are already in a conversation with one of your senders. That option is on by default and covers the 30 days before the account was connected. Two more options are off by default: skip people contacted in an earlier campaign, and skip people the same sender contacted before. A blacklist for people and companies applies before every step.

A request a teammate sent by hand that is still pending is treated as sent, and the lead waits for acceptance as normal.

How does a manager set this up?

  1. Connect every teammate’s own account, one sender each.
  2. Import the list once and check the skipped count and its reasons before launch.
  3. Choose all the senders in one campaign, not one campaign per person.
  4. Leave the already-in-a-conversation exclusion on.

Run one campaign from several accounts walks through it. At $29 per sender a month, 5 senders are $145 and 10 are $290, with members free.

What can’t it catch?

We only see accounts connected to the workspace. A teammate who messages a lead from an account that isn’t connected, or by hand before sync runs, isn’t visible to us at once. Sync polls about every 15 minutes in working hours, so a reply or a hand-sent message can take that long to appear.

The honest boundary

The rules above stop duplicates inside one workspace. They don’t coordinate with anyone outside it, such as a sister team using another tool. Talk to them about shared lead lists first.