Try Valley
Put your outbound workflow to work.
Saniya Sood
Published:
Updated:
Published June 23, 2026 · Updated November 11, 2026
The short answer: have each client connect their own LinkedIn account (never share passwords or cookies), run every client in a separate workspace with its own ICP, voice, lists and inbox, keep each account inside its own limits (roughly 100 invitations a week, 20 to 25 connection requests a day once warmed up), use a cloud tool with a stable IP per account instead of a browser extension, and review messages before they send.
Valley is an AI outbound platform that finds the people most likely to buy from you - from live buying signals, natural-language search, or your own lists - qualifies them against your ICP, researches each one, and sends personalized messages across email and LinkedIn that get 15-45% reply rates, against a category average of about 2%.
Key takeaways
The account belongs to the client. LinkedIn's User Agreement says members will not share their account, and lists sharing log-in credentials or copying cookies as using another's account. The client connects it; the agency operates the campaign.
Limits are per account, not per agency. Ten client accounts are ten separate sets of limits, and one account's restriction should never touch the others.
Execution model matters most. LinkedIn's terms name browser plug-ins and add-ons; a cloud tool with a dedicated IP per account is the lower-risk model.
One workspace per client stops the most visible agency failure: a message for one client sent in another client's voice.
No tool removes the risk. LinkedIn restricts unauthorized automation, so the job is keeping each account far from the patterns that get flagged.
What LinkedIn's rules actually say
LinkedIn's User Agreement, read November 11, 2026, is the rulebook every client account sits under. Three lines matter to an agency:
Section 2.2: "You will not share your account with anyone else".
Section 8.2: members agree not to "use or attempt to use another's account (such as sharing log-in credentials or copying cookies)".
Section 8.2: members agree not to "Use bots or other unauthorized automated methods to access the Services" to "add or download contacts, send or redirect messages", or to use software "(such as crawlers, browser plugins and add-ons or any other technology)".
Read plainly: an agency logging in with a client's password is the clearest breach, and any automation carries some risk. The safest setup keeps the client as the account owner, keeps activity at human pace, and avoids the execution model the terms name directly. LinkedIn publishes no official daily thresholds, so the numbers in this guide are practitioner safe zones, not LinkedIn rules.
► Try Valley free for 7 days: connect one client account and run it in its own workspace
Give your sales team
an unfair advantage.
Seven steps, in the order an agency sets up a new client.
Step 1. Let the client connect their own account
The client logs in and connects their LinkedIn account to the tool themselves, on their own device. The agency never holds the password and never copies session cookies, which is exactly what section 8.2 describes. If the client leaves, they disconnect the account and nothing of theirs stays with you.
Step 2. Give every client a separate workspace
Each client gets its own ICP, offer, writing style, lead lists and reply inbox. Shared campaigns across clients are how the wrong brand voice reaches the wrong prospect, and how one client's lists leak into another's. It also makes reporting per client a filter, not an export.
Step 3. Warm up new accounts and pace each one
These are the operational safe zones compiled in the safest LinkedIn automation tools guide from practitioner data (SalesTarget.ai, April 2026; Dux-Soup's 2026 safety guide):
Action | Safe zone per account (2026) |
|---|---|
Connection requests | About 20 to 25 a day, ramped from about 10 over two to three weeks |
Messages to existing connections | About 20 to 30 a day |
Profile views | 80 to 100 a day (paid accounts) |
Pending invites | Keep the list short; withdraw unanswered invites after about three weeks |
InMails | Within the plan's credit allowance |
The weekly ceiling is roughly 100 invitations per account on a rolling week (the LinkedIn connection request limit, explained). Message limits are covered in LinkedIn message limits.
Step 4. Run accounts in the cloud, each on a stable IP
Browser extensions act inside the live LinkedIn session on the operator's computer, the model LinkedIn's terms name. Cloud tools run each account from a server, so the operator's laptop can be off and two clients never share one browser. Ask every vendor how IPs are assigned:
Expandi lists a dedicated country-based IP address per account on its pricing page.
HeyReach's Agency plan FAQ says you bring your own proxies (pricing page).
Valley runs outreach from the cloud with a dedicated IP per account and keeps pacing inside the safe zones by default.
Step 5. Start from people who already showed interest
Cold volume to strangers produces the ignored invites and identical messages that look automated. Outreach to people who engaged with a client's post, followed the page, viewed a profile or visited the website looks like a normal follow-up, because it is one. More in buying signals, ranked by how close the buyer is.
Step 6. Review messages and hand replies to a human
Approve each client's messages before they send, at least for the first weeks, and make sure a reply stops the sequence. An automated follow-up landing after a prospect has answered is the fastest way to lose a client's trust.
Step 7. Watch each account's health
Warning sign | What it usually means | What to do |
|---|---|---|
Acceptance rate falling week on week | Targeting or note quality has slipped | Tighten the list to warmer signals; rewrite the note |
Pending invites piling up | Invites to people unlikely to accept | Withdraw the oldest in small weekly batches |
A verification prompt or restriction notice | LinkedIn has flagged the account's activity | Pause all automation on that account, complete the check, restart at a lower pace |
Replies answered late or twice | No clear owner for the inbox | One inbox per client, one person responsible |
Each client message still carries the client's name; make it one they would send themselves.
Give your sales team
an unfair advantage.
How Valley runs client accounts
Each client connects their LinkedIn account once and lives in its own Valley workspace, with its own offer, ICP, writing style, lists and unified inbox. Valley builds the audience from that client's buying signals (post engagers, followers, profile viewers, website visitors), a play or the client's own list, qualifies every prospect against the client's ICP, researches each one and drafts in the client's voice. Messages can be reviewed before sending, a reply stops the sequence, and LinkedIn and email run in the same sequence.
Track record: zero suspensions across 1,000+ accounts and 300+ teams, and 15-45% reply rates vs about 2% from cold outreach. Gallea AI, an AI search agency, booked 15 meetings in 14 days; Butteredtoast, a marketing agency, generated $1M+ in pipeline.
Limits to know: Valley is priced per seat (current prices at joinvalley.co/pricing); Starter covers LinkedIn, and Plus adds 1,000 emails a month if needed. Valley's own site says full white-label is limited: prospects see the client's account and voice. The agency setup is on Valley for agencies, and the tool comparison is in the best outbound tools for agencies.
Setup | Who holds the login | Where it runs | Client separation | Risk |
|---|---|---|---|---|
Shared password in a browser extension | Agency | Operator's browser | None | Highest: breaches 2.2 and 8.2, named execution model |
Cloud tool, agency-supplied proxies | Client connects; agency manages proxies | Cloud | Depends on the tool | Lower; proxy quality is on you |
Cloud tool with dedicated IP and per-client workspace | Client connects | Cloud | Workspace per client | Lowest of the three |
► Book a demo: see how Valley would find, research and message your buyers
FAQ
Is it against LinkedIn's rules for an agency to manage a client's account? Logging in with the client's password is: section 2.2 says members will not share their account, and section 8.2 lists sharing log-in credentials or copying cookies. Having the client connect their own account to a tool avoids that, though LinkedIn's terms still restrict unauthorized automation, so keep activity at human pace.
How many LinkedIn accounts can an agency run safely? There is no agency-wide cap, because limits apply per account. What breaks agencies is one account pushed past its own limits, or several accounts sharing one browser or IP.
How many connection requests per day is safe for a client account? About 20 to 25 a day for a warmed-up account, starting nearer 10 and ramping over two to three weeks, inside a weekly ceiling of roughly 100 invitations. LinkedIn publishes no official daily number.
Does each client account need its own IP? A stable IP per account is the safer setup. Expandi lists a dedicated country-based IP, HeyReach's Agency plan asks you to bring your own proxies, and Valley assigns a dedicated IP per account.
What should an agency do if a client account gets restricted? Stop every automated action on that account, complete whatever verification LinkedIn asks for, tell the client, and restart later at a lower pace with warmer targets. Never move the campaign to another person's account.
Can one agency run LinkedIn and email for each client? Yes. Valley runs both in one sequence per client workspace: email is an add-on on Starter and included on Plus. Email should come from the client's own domain and inbox.
How this page was made: LinkedIn's User Agreement and each vendor's pricing page were read on November 11, 2026; drafted with AI assistance; fact-checked, reviewed and edited by Saniya Sood.
