Give every client account its own IP address, its own browser profile and its own sending budget, sized to that account's network and LinkedIn plan. Warm new accounts up over about three weeks, keep each lead with one sender, and when one account gets a warning, pause that account only. Nothing removes the risk. This keeps it small and contained.
Numbers checked against what CampaignStack enforces, October 2026.
Start with what LinkedIn's agreement says
LinkedIn's User Agreement bans two things every multi-account agency does: using "bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages", and trying "to use another's account (such as sharing log-in credentials or copying cookies)". It also says "You will not share your account with anyone else."
Every tool that runs outreach on a client's account works through that account's session, ours included. So no tool can honestly promise you zero restrictions.
You can't make the activity invisible, so stop trying. Keep each account's risk small, contained to that one account, and owned by the person whose name is on it: they know what runs on it, they agreed to it, and they are the only one who can clear an identity check.
For what a restriction is, how to tell one from a dead session, and how to prove limits to a client, read Will this get my LinkedIn account banned?
Isolate everything that belongs to one account
The rule fits on a sticky note: one account, one person, one device, one budget. Agencies running multiple LinkedIn accounts share each of these by accident, because sharing is easier.
| What to isolate | Why it matters | What goes wrong when it's shared |
|---|---|---|
| IP address | LinkedIn sees where each session comes from | Six accounts on one office or datacenter IP look like one operator |
| Browser profile and device | The fingerprint should be the same on Monday and Friday | Every account looks like it lives on the same machine |
| Sending budget | Limits only mean something per account | A busy client drains a quiet one's allowance |
| Warm-up stage | A new account has no history of tool-driven activity | A fresh account inherits the pace of a warmed one |
| Risk pause | A warning is about one account's behaviour | Five clients get paused for one account's problem |
| Sender of record per lead | A lead knows who wrote to them first | A follow-up from a second account reads as a stranger writing in |
| Client data (leads, do-not-contact list) | Client A's "no" list belongs to client A | Client B messages someone who already told client A to stop |
In CampaignStack, each account gets its own dedicated IP, its own encrypted browser profile, and each client can have its own workspace; the agency section of our ban article explains how that isolation works.
Know what each account can really send
LinkedIn publishes no invitation or message ceiling. Every figure below is ours, the limits CampaignStack enforces per account. The reasoning behind the invitation number is in LinkedIn's real connection request limits.
| Plan on the account | Connection requests, weekly cap | Connection requests, real daily max | Messages per day | Profile views per day | InMail per day |
|---|---|---|---|---|---|
| Free | 100 | 15 | 50 | 40 | 0 |
| Premium | 150 | 22 | 150 | 80 | 10 |
| Sales Navigator | 200 | 29 | 200 | 150 | 25 |
| Recruiter | 200 | 29 | 300 | 200 | 40 |
The daily invitation number is 3% of the account's connections, held between 15 and 50, times 1 for Free, 1.5 for Premium and 2 for Sales Navigator or Recruiter, then capped at the weekly cap divided by seven, rounded up. That's why a Free account with 600 or 6,000 connections still sends at most 15 a day.
Three more rules shape the week. Weekends run at 30% of the weekday send budget, and sends happen between 8 AM and 6 PM on weekdays and 9 AM to 2 PM on weekends, in the account's local time, 45 to 120 seconds apart. And an account under 300 connections gets an outreach budget of zero.
Pick an operating model
There are three common ways to run several client accounts; the extension model splits in two, depending on whose browser it lives in.
| Risk factor | One VA or laptop logs into every account | Extension per account, in the client's browser | Extension per account, in your browser | Isolated cloud profile and dedicated IP per account |
|---|---|---|---|---|
| Accounts share an IP | Yes | No | Yes, unless you add proxies | No |
| Accounts share a device fingerprint | Yes | No | Yes | No |
| Budget enforced per account | Only if the VA keeps count | Per extension | Per extension | Yes |
| Runs when the laptop is closed | No | No | No | Yes |
| Sees the client's own activity | No | Partly | No | Only if it measures it |
| Offboarding | Change passwords and hope | Client uninstalls it | You remove profiles by hand | Disconnect, profile destroyed |
The first model is the one we'd retire today: every account in it looks related, and nothing counts per account unless a human does.
Worked example: six client accounts, one agency
This agency is hypothetical. The accounts are made up; the numbers come from the limits above.
Your sales deck says six client accounts each send 50 invitations a day, five days a week: 6 x 50 x 5 = 1,500 a week. Here is what they can really send in their first week with you, assuming A, B, C and F are fully warmed up.
| Account | Plan and connections | Daily formula | Real day (weekday / weekend) | Real week |
|---|---|---|---|---|
| A | Sales Navigator, 2,400 | 3% = 72, held at 50, x 2 = 100 | 29 / 29 | 200 (7 x 29 = 203, weekly cap is 200) |
| B | Premium, 900 | 3% = 27, x 1.5 = 40 | 22 / 12 | 134 (5 x 22 + 2 x 12) |
| C | Free, 1,800 | 3% = 54, held at 50 | 15 / 15 | 100 (7 x 15 = 105, weekly cap is 100) |
| D | Free, 250 | Under 300 connections | 0 / 0 | 0 |
| E | Free, 1,000, just connected, never automated | 3% = 30, capped at 15/day, warm-up starts at 10% | 3, 4, 5, 6, 7 / 2, 3 | 30 |
| F | Sales Navigator, 3,000, shared by two clients | 3% = 90, held at 50, x 2 = 100 | 29 / 29 | 200, for both clients together |
Add it up: 200 + 134 + 100 + 0 + 30 + 200 = 664 invitations a week. Less than half the deck.
Among the warmed accounts, B is the only one where the weekend bites, since 30% of 40 is 12; A's and C's weekend share still reaches their daily cap. E starts at 10% of 30, which is 3, and gains 4 percentage points per active day, with its weekend also cut to 30%.
Once E is fully warm, about three weeks in, it sends 5 x 15 + 2 x 9 = 93 a week, and the agency's ceiling becomes 664 - 30 + 93 = 727. Still under half of 1,500, and still a ceiling, not a target: scheduled automations stop at 80% of a day's budget, leaving the rest for replies, manual actions and retries.
Each LinkedIn account gets its own budget, IP and browser profile, sized to its own network and plan.
See your accounts' real weekly ceilingOnboard a new client account
Ask three things first. How many connections does it have? Has it run an automation tool before? What else runs on it today?
Under 300 connections, every outreach budget is zero (replies to people who wrote first still go out) and background reads are halved. The same applies when the connection count is unknown and the account was linked less than 30 days ago.
Above 300, an account new to automation starts at 10% of its budget and gains 4 percentage points per active day: about three weeks to full speed. One idle day is free; after that, each idle day multiplies the budget by 0.82. Fresh accounts are often the ones a client wants to start fast, so tell them before they ask why week one looks thin.
The third question is the one people forget. Two automation tools on one account means two systems that each think they own the budget.
Plan for the client's own activity
The client still accepts invitations on their phone, sends a few messages, connects with a dozen people after a conference. It all happens on the same account, so it has to fit inside the same limits as your campaigns.
CampaignStack measures what was done outside it each day, just after midnight in the account's timezone, and leaves that much less room the next day. If that measurement is missing or out of date, it subtracts nothing, so tell the client plainly: on days you run your own push, let us know, or switch the other tool off.
Contain a warning to one account
LinkedIn pushes back on one account, about one kind of action, so respond just as narrowly. Three rate limits in 24 hours on one kind of action (invitations, messages or profile visits), or a single security check, pauses that kind of action on that account for 24 hours.
Replies keep going: a pause on invitations has no reason to stop conversations people started with you. The other five accounts carry on. They share no IP, device or budget with the one that got the warning, so they keep their own pace.
If it becomes a full restriction, only the account owner can clear identity verification, with a government ID. Our restricted account guide covers the first hour.
One sender per lead, one budget per account
A lead contacted from an account stays with that account. A follow-up from a different sender reads as a stranger writing in about the same thing.
The budget belongs to the LinkedIn account, not to the client. Two client workspaces on one LinkedIn account, like F above, draw from one budget, so plan both campaigns against 200 a week in total.
Separate workspaces still keep each client's leads and do-not-contact list apart; our LinkedIn accounts guide shows how accounts, workspaces and senders fit together.
Keep pending invitations under control
LinkedIn caps pending invitations near 400, and an account that never withdraws unanswered ones drifts toward the cap on its own.
Take account C, sending 100 a week. Say 3 in 10 accept within the same week and nobody declines (assumptions for the arithmetic, not rates we're claiming), which leaves 70 a week pending: 70, 140, 210, 280, 350, then 420, past the cap in week six.
A withdrawal ladder stops it. The fuller the pile, the younger the invitations you withdraw, and nothing younger than 7 days is ever touched.
| Pending invitations | Withdraw invitations older than |
|---|---|
| Under 250 | 30 days |
| 250 to 319 | 21 days |
| 320 to 359 | 14 days |
| 360 or more | 7 days |
For account C, the 30-day rule alone would let the pile reach roughly 300. Crossing 250 drops the cutoff to 21 days, roughly 210 pending, so the pile hovers between about 210 and 250, far from 400.
Offboard a client cleanly
When a client leaves, disconnect the account, release its IP and destroy its browser profile, the same day. In CampaignStack, disconnecting destroys the encrypted profile on our server and returns the IP to the pool with a fresh address (security page). Without that step, the client's session still sits somewhere after they've gone.
Gotchas and what to do Monday
Stale pending invitations go unnoticed until new ones start failing. The free account safety check shows one account's pending invitations by age and its weekly volume against the ceiling.
On Monday, list every client account with its plan and connection count, and work out its real weekly ceiling from the tables above. Check that no two accounts share an IP or a browser, and ask each client what else runs on their account. If the total doesn't match what you've promised, change the promise before LinkedIn changes it for you.
Every limit here is also on our safety page, and the agency page shows how it fits a client roster.
FAQ
Can multiple LinkedIn accounts share one IP address?
They can, but it makes separate clients look like one operator. Give each account its own dedicated IP and keep it across reconnects.
Is it against LinkedIn's rules to run a client's account?
Yes. LinkedIn's User Agreement prohibits automation and using another person's account, naming shared logins and copied cookies. The defensible version is a client who knows, agrees, and can clear any check LinkedIn raises.
How many connection requests can one account send per week?
LinkedIn doesn't publish a number. The weekly caps CampaignStack enforces are 100 for Free, 150 for Premium and 200 for Sales Navigator or Recruiter, with a real daily maximum of 15, 22 and 29.
What happens to the other accounts if one gets restricted?
They keep running. Three rate limits in a day on one kind of action, or one security check, pause that kind of action on that one account for 24 hours. A pause on invitations leaves conversations running. Isolation lowers the chance LinkedIn links the accounts, but no tool can promise the others stay untouched.
How long does it take to warm up a new client account?
About three weeks. An account new to automation starts at 10% of its budget and gains 4 percentage points per active day; after one free idle day, each further idle day multiplies the budget by 0.82.
Can two clients use the same LinkedIn account?
They can, but they share one budget: two clients on one Sales Navigator account split 200 invitations a week. Keep them in separate workspaces so their leads and do-not-contact lists stay apart.
Does a Sales Navigator seat raise the limits?
In our limits, yes: a weekly cap of 200 instead of 100 on Free, a real daily maximum of 29 instead of 15, and 25 InMails a day. LinkedIn doesn't say whether a paid seat changes what it tolerates, so keep the same isolation.