Coordinating LinkedIn connection requests across a remote team
Give every remote rep their own LinkedIn account and a shared lead list, then cap volume per account so no two reps message the same buyer twice.
Get startedShort answer
To run LinkedIn outreach across a remote team, keep the lead lists separate from the LinkedIn accounts that send. Each rep connects their own profile, leads sit in shared groups with one active campaign per group, and daily volume is capped per account so two reps never message the same buyer.
Splitting the lead list so two reps never touch the same person
Write your target profile down before anyone searches. Job titles, company size, the trigger you actually care about (a new office, a funding round, a job post for a role you serve). If two reps read founder differently, one of them spends the week on leads the other would never touch.
Then pick one split model and keep it for a quarter. Changing the model every month means you can't compare one rep's results with another's, and the reps stop trusting the list.
Region
- Split model
- Reps own named cities or countries and learn the local buying habits
- Where it holds up
- A company with offices in two regions gets worked twice
Industry vertical
- Split model
- Each rep learns one sector's language and objections
- Where it holds up
- A conglomerate that fits two verticals lands on two lists
Named accounts
- Split model
- Large targets get one owner and a written plan
- Where it holds up
- Small accounts wait because nobody owns the long tail
Round robin on a shared list
- Split model
- New leads spread evenly with no thinking required
- Where it holds up
- Nobody builds expertise, and handoffs lose the thread
Keeping volume inside limits LinkedIn doesn't publish
LinkedIn does not publish exact daily or weekly limits for invitations, messages or profile views. Anyone quoting a fixed number is guessing. Set your own ceiling per account below what feels aggressive, then move it based on what the account tells you.
Send windows matter more on a remote team. A rep in Berlin writing to a buyer in Denver at 9am local time is writing at 1am Denver time. Key the window to the lead's time zone and the odd hours disappear without anyone maintaining a list of offsets.
Watch the pending pool. An account with hundreds of invitations nobody accepted looks like it is broadcasting, and it blocks that rep from reaching better-fit people. Withdraw invites older than two or three weeks and keep the pool small enough that a rep can name the people in it.
- 1
Set a starting ceiling per account
Pick a number you could defend as something a person might type by hand in a working day. Your acceptance rate over the first two weeks tells you whether it was too high.
- 2
Write the send window in the lead's time zone
Business hours in the prospect's city, not the rep's. This matters most for teams spread across three or more time zones.
- 3
Clear stale invitations weekly
Withdraw requests older than two or three weeks. Those people saw the request and passed, and they hold space that could go to a better-fit lead.
- 4
Review acceptance rate before raising volume
If acceptance drops after a change, put the ceiling back. Raise it only after a stretch where the number holds.
Handling replies and handoffs when half the team is asleep
Replies are where remote teams lose deals. A prospect answers at 6pm their time, the rep is asleep, and by morning the thread has gone quiet. Someone else on the team could have answered, but nobody knew who owned it.
Decide before launch who handles a reply. Either the rep who sent it owns it, or a shared inbox gets triaged twice a day by whoever is online. Write the rule into your playbook so nobody is asking in chat at midnight.
When a prospect asks about price or timing, answer the question they asked. A reply that dodges 'what does it cost' to talk about value reads like a bot, and the prospect stops answering.
Example
- You
Hi Dana, I saw Northwind opened a second office in Leeds. We help agencies your size keep onboarding for new hires in one place. Worth a short look?
- Prospect
Maybe. We're mid-migration on our HR tool, so the timing is bad. What does pricing look like?
- Suggested reply
Fair enough, waiting until the migration settles makes sense. Pricing depends on headcount, and you would sit in the 40 to 60 band. I can send a one-page summary to keep for when the migration closes.
- Prospect
Send it. Ping me in September if I go quiet.
- You
Sent. I'll come back the first week of September unless you get there first.
Whoever answers, log the outcome where the whole team can see it. The next rep who touches that account should know a migration is running and a September date is set.
Doing this with Kinlead
Kinlead keeps leads in groups and campaigns separate from the LinkedIn account that sends, which is the split above. A Pro admin invites teammates by email and chooses which workspaces each person can open. Each teammate signs in with their own login, works inside the shared workspace, and connects their own LinkedIn through Unipile. Kinlead never stores the LinkedIn password. Each teammate uses one extra seat, priced like an extra LinkedIn account.
The admin builds lead groups from a CSV of profile URLs, from a lead search on LinkedIn's standard search, or with the Steal Customers agent that reads comments on competitor posts. Any campaign can point at any group, so the overlap check is a look at which live campaigns use which group.
Sending runs at most one LinkedIn action every 5 minutes per account, inside daily invite and message limits you set and inside a send window in the lead's time zone. Stale pending invitations are withdrawn automatically, and Settings shows pending invitations and acceptance rate with warnings. When LinkedIn pushes back on an account, Kinlead pauses invites on it and emails you. Replies from every campaign land in one unified inbox, classified by intent, interested replies first.
To hand a conversation over, set the campaign to hand off at the first reply, or let the AI reply until there is interest or until a meeting is booked with your link. Queued messages can be read and edited on the Actions page before they send. Pro is $49 a month after a 7-day free trial, and extra LinkedIn accounts are $40 a month each.
- 1
Create the workspace and seats
The admin invites each rep by email and picks the workspaces they can open. Each rep signs in with their own login and connects their own LinkedIn.
- 2
Build the lead groups
Import a CSV of profile URLs or run a lead search against your target profile. Keep one group per segment so campaigns can point at them.
- 3
Point one campaign at one group
Set the goal, tone and your sales playbook, then check that no other live campaign uses the same group.
- 4
Set limits and send windows
Choose the daily invite and message limits per account and the window in the lead's time zone.
- 5
Triage replies twice a day
Open the unified inbox in the morning and the afternoon, interested replies first, and hand off anything that needs a human.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? Coordinating LinkedIn connection requests across a remote team.md