Managing LinkedIn limits during hiring spikes
How to split target lists across SDR accounts, pace each LinkedIn profile from its own history, and keep pending invites healthy when you hire.
Get startedShort answer
To scale outbound during a hiring spike, split the target market across the LinkedIn accounts your team already uses. Give each account its own lead group, keep send volume close to that account's normal activity, and prune stale pending invitations. LinkedIn does not publish exact limits, so the safe number is whatever an account can do without sudden spikes.
Why one account breaks under a hiring spike
Northwind adds two SDRs in January. The founder has been sending a steady trickle of connection requests from his own profile for a year. On the first Monday with the new team, all three campaigns point at the founder's account because that's where the leads already live. By Wednesday the account is asking for human verification and the week's sends stop.
LinkedIn does not publish exact invite or message limits. It watches for changes in behavior. An account that suddenly sends many more requests than its own recent average looks automated, even if the total is modest for someone else. The same jump on three accounts, each from its own profile, looks like three people doing their jobs.
The fix is not a secret number. It's separation. Each LinkedIn account needs its own leads, its own send history and its own pace. When one account gets limited, the other accounts keep working and the pipeline does not stop.
All volume on one profile
- Founder's account carries the new SDR campaigns
- Sends jump from the account's normal trickle to a burst
- One restriction stops every sequence at once
Volume split by account
- Each SDR sends from the profile they own
- Each account stays near its own recent pace
- A limit on one account leaves the others running
Split the market before you split the work
If two SDRs message the same prospect, the second message looks careless. The prospect sees two people from Acme asking for the same call. That is the overlap problem, and it gets worse when you add accounts.
Pick one split rule and write it down. Geography is easy to explain. Industry works when each SDR knows the language of a vertical. Company size works when your pitch changes for a small shop and a large company. Relationship source works when one SDR owns everyone from a conference list and another owns everyone from a partner community.
The rule matters less than the boundary. Every lead needs one owner. A lead that belongs to two groups will eventually get two invites.
Write the rule as a sentence the team can repeat. If nobody can say who owns a lead without checking a spreadsheet, the split is too complicated.
- 1
Export the master list
Use the LinkedIn profile URL as the unique key. Keep company, title and source columns so you can audit the split later.
- 2
Choose one split rule
Write it as a sentence the team can repeat. For example, Dana owns all agency leads in North America. Marcus owns agency leads everywhere else.
- 3
Assign each segment to one account
Create a separate lead group per account. Do not let a campaign point at two groups that share a lead.
- 4
Run a duplicate check
Compare profile URLs across groups before the first send. Fix duplicates by hand, not by guessing which SDR should win.
Geography
- Split rule
- Teams cover different regions or time zones
- Works when
- Accounts move or prospects travel
Industry
- Split rule
- Each SDR can speak the vertical's language
- Works when
- Large companies sit in several industries
Company size
- Split rule
- Your pitch changes between small and large accounts
- Works when
- Accounts near your size cutoff get argued over
Relationship source
- Split rule
- You have warm paths from events, groups or partners
- Works when
- Lists become uneven and one SDR gets a thin group
Set pacing from the account's own history
A new SDR account and a founder account with years of activity should not send at the same pace. The founder has a history. The new account has none. LinkedIn can see both.
Start each account below its recent normal activity, then increase only after a week with no warnings and a healthy acceptance pattern. Space actions across the day. A batch of requests sent in ten minutes looks different from the same number spread over a morning.
Keep a simple log. You are looking for the point where an account gets a warning, a verification prompt or a drop in acceptances. That point is the ceiling for now. Cut back below it before you try again.
Do not copy one account's pace to another. The account that has been active for years is not a template for the account that just left onboarding.
If LinkedIn asks you to verify you are human or blocks an action, stop adding volume for that account that day. Return to the last pace that ran without a warning, then wait before you increase again.
Paste this job
account,week,connection_requests_sent,accepts,pending_invites,warning_or_prompt,notes Dana,2025-W02,,,no, Marcus,2025-W02,,,no, founder,2025-W02,,,no,
Keep the pending invite pool from silting up
A pending invitation is a request someone has not answered. A few are normal. A large pile suggests you are sending requests to people who do not recognize you, or that your note is not giving them a reason to accept.
Track your pending invitations and the share that get accepted. If pending requests keep growing while acceptances stay flat, adding more SDRs will just create more unanswered requests. The problem is upstream in the targeting or the opening line.
Review pending invites on a schedule. Withdraw the oldest ones first. Then look at which segment produced them. If one industry or title produces most of the stale requests, fix the targeting or the note before you send more.
- Open the sent invitations view for each account once a week.
- Withdraw requests that have gone unanswered for a few weeks, oldest first.
- Compare pending requests by lead group. A bad segment is easier to fix than a bad account.
- Do not withdraw and resend to the same person in the same week. Pick one path.
Handle replies without letting accounts collide
When several SDRs work the same market, replies need one owner. A prospect who replies to Dana should not get a follow-up from Marcus two days later. That feels like a handoff gone wrong.
Decide the handoff before the campaign starts. If the original sender owns the conversation, everyone else leaves it alone. If a specialist takes over, the original sender introduces them in the same thread. Do not send a fresh connection request from the specialist's account.
Put every reply in one place, even if the sending accounts are separate. The person running the team needs to see interested replies first, not scroll through five inboxes to find them.
Example
- Prospect
Thanks for the note, Dana. I handle agency partnerships, not the sales team you mentioned.
- You
Got it, Priya. I'll bring in Marcus, who covers partner conversations for us. He can answer the terms question without making you repeat yourself.
- Suggested reply
Hi Priya, Dana passed this to me. You asked about partner terms for smaller agencies. I can walk you through how we set that up. Would Thursday morning work?
Doing this with Kinlead
Kinlead turns the split into campaign structure. Each lead group holds the leads for one segment, and a campaign points at that group. Teams can import a CSV of LinkedIn profile URLs or export leads when they need to audit the boundary.
Each teammate connects their own LinkedIn account through Unipile, so sends come from their profile. You set daily invite and message limits per account and choose a send window in the lead's time zone. Kinlead sends at most one action every 5 minutes per LinkedIn account.
Settings shows pending invitations and acceptance rate with warnings. Stale pending invitations are withdrawn automatically. Start with lead groups and point each campaign at one group.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? Managing LinkedIn limits during hiring spikes.md