The LinkedIn Compliance Field Guide

A Sales Connector field manual for keeping client accounts safe while running outbound at scale.

SECTION 01Foreword

This is not a marketing document. It is the operating manual we hand to every account manager, every white-label partner, and every active client who runs outbound through Sales Connector. Read it once front to back before you touch a campaign. Re-read Act 3 the morning after any account hits a warning.

The voice here is plain and sometimes cautionary. That is on purpose. LinkedIn restrictions are a category of business risk that most outbound teams discover the hard way, usually when a top performer's account goes dark on the morning of a board call.

Sales Connector has moved millions of connection requests through thousands of accounts. The numbers and behaviors documented here are not theoretical. They are the operating envelope that has kept the majority of our accounts in good standing through every major LinkedIn enforcement wave we have observed.

Use this guide. Do not improvise.

ACT 1: WHY THIS MATTERS

SECTION 02Chapter 1: The Thing Nobody Warns You About

Most outbound platforms pitch you on volume. They show you a graph that goes up and to the right, demos that promise hundreds of conversations per week, and dashboards full of green numbers. None of them spend much time talking about what happens to the LinkedIn account underneath those numbers.

Here is what nobody warns you about: the account is the asset. Not the connections, not the campaign, not the templates. The account. And the account is on rented land. LinkedIn owns the land. They write the rules. They enforce the rules unevenly, sometimes silently, sometimes with a 24-hour warning, sometimes with no warning at all. And the rules change.

If you have been running outbound for a while you have probably already met somebody this happened to. A senior AE with a 15-year-old profile, 12,000 connections, and an inbox full of warm conversations. One Tuesday morning they sign in to a screen that says "We have detected unusual activity." Phone verification clears it. Two weeks later the screen comes back, this time with a 7-day cooldown. They wait. They sign in. The account is restricted permanently. The appeal form is reviewed by an automated system that almost always says no.

That account is gone. The connections are gone. The warm inbox is gone. The decade of relationship capital is gone. Every prospect who was mid-conversation now experiences your team as ghosts. They will not know your account got restricted. They will assume you stopped caring. They will move on to a competitor whose AE is still answering messages.

The cost of getting an account restricted is not "we have to make a new account." The cost is the destruction of relationship capital that took years to build, the silent abandonment of every active conversation, and the loss of trust with every prospect who was waiting for a reply. The new account starts from zero. It looks like a bot. The 200 cold prospects who were softening up over six weeks of nurture do not migrate over.

You do not get a do-over. You get a reset.

SECTION 03Chapter 2: What Restriction Actually Costs

A restricted account costs, on average across our client base, somewhere between $40,000 and $250,000 in pipeline depending on the size of the account, the seniority of the seller, and the role of LinkedIn in the seller's prospecting mix. The variance is wide. The number is rarely zero.

The breakdown:

• The 30-90 days of active conversations in the inbox at the moment of restriction. Half never resume even if the account is recovered.
• The 6-18 months of network capital in the connection graph. A connection is a permission slip that surfaces your content in their feed and their job changes in your radar. New accounts rebuild this from scratch.
• The 1-4 weeks of operational disruption while the team figures out what happened, opens an appeal, sets up a replacement, transfers prospects, rewrites templates, and reconfigures Sales Connector under the new identity.
• The opportunity cost of the seller's pipeline run-rate during recovery. A seller producing $80K of pipeline per quarter who goes dark for three weeks loses $20K of pipeline.
• The reputational cost inside your own company, where the seller now has a story they tell at every offsite for three years about why automation cannot be trusted.

It lands hardest on senior reps with legacy networks. Junior reps recover faster because the reset cost is smaller. The irony is that the people most worth protecting are the people most likely to push the limits, because their numbers depend on volume and their seniority gives them the leverage to demand it.

Tell your top performers about this guide. They are the ones who need it most.

SECTION 04Chapter 3: The Difference Between Moving Fast and Moving Recklessly

There is a real difference between moving fast on LinkedIn and moving recklessly. Plenty of reps and platforms do not understand the difference.

Moving fast looks like this. You have warmed up your account on a steady cadence over 4-6 weeks. You are running 25-30 connection requests per day with 8-12 minute jitter, sent only during local business hours. Your templates have personalization variables that produce real per-recipient variation. Your account uses a dedicated IP that nobody else in your organization is logged into. Your automation paces itself even if the queue has 5,000 items waiting. You have daily, weekly, and monthly ceilings. You are watching the lifetime connection count creep toward 30,000 and you have a plan for what happens at 28,000.

Moving recklessly looks like this. You signed up Monday. By Wednesday the rep is asking why the daily cap is so low. By Thursday you have raised it to 50/day. By Friday the template is "Hi (first name), would love to connect" and it goes out 47 times in three hours. By the following Tuesday LinkedIn is asking for phone verification. By the following Friday the account is in a 7-day timeout. The rep is on the phone with their AM blaming Sales Connector. Sales Connector is opening the same conversation we have had hundreds of times: "We did not send 50/day on your behalf. You overrode the safety limit. Here is the audit log."

The cruel part is that for the first 2-4 weeks, recklessness looks like it is working better than discipline. The reckless account sends more and the rep feels validated. By month two or three the reckless account is in trouble and the disciplined account is producing more pipeline at lower risk. The math compounds in favor of discipline. You just have to survive long enough to see it.

Do this now (Act 1)

• If you do not know your account's lifetime connection count, log in and check. It is at the top of the My Network page.
• If you do not know which IP your account has been logging in from, check the active sessions in account settings. If there are more than two distinct IPs in the past 30 days, you have a problem worth investigating.
• If you have a top-performing rep who has been pushing the daily cap for any reason, send them a copy of this guide and have them read Act 1 before you let them touch their campaign settings again.
• Look at your last 10 connection request templates. If any two of them are identical, you have a structural problem we will address in Act 2.

ACT 2: HOW SC STAYS SAFE

SECTION 05Chapter 4: The Numbers, In Plain English

The hardest part of compliance is that LinkedIn does not publish the numbers. The thresholds are inferred from years of pattern observation across thousands of accounts. The numbers below are our operating envelope. They are deliberately conservative. They are not the limits at which LinkedIn flags you. They are the limits at which we are confident you almost never get flagged.

Daily connection requests: 25-30 per account. This is the safe ceiling. Some accounts can sustain 35-40 for short periods. Almost no account can sustain 50+ without consequences. The lower end of the range is for newer accounts and DACH/EU accounts. The higher end is for established US-based accounts in good standing with stable acceptance rates.

Weekly connection requests: 100 per account. This is an absolute cap. Even if your daily numbers add up to more, you should not exceed 100 connection requests in any rolling 7-day window. LinkedIn's enforcement systems appear to look at weekly totals as much as daily totals. Five days at 30/day is 150/week and is too much. Five days at 20/day is 100/week and is fine.

Inter-action jitter: 8-12 minutes between actions. Every connection request, every message, every profile view should be separated by at least 8 minutes of randomized delay, ideally drawn from a non-uniform distribution that mimics human attention spans. We add additional jitter at the cluster level: every 4-6 actions there is a longer 20-40 minute pause. The combination is what makes the activity pattern look human.

Operating window: local business hours only. All automated activity runs between 8am and 6pm in the account holder's stated local time zone. We do not send during evenings, weekends, or holidays. Real humans do, occasionally. Real humans operating LinkedIn at high volume from 2am on a Saturday do not exist, and LinkedIn knows this.

Lifetime connection cap: 30,000. This is the hard wall. LinkedIn does not allow any account to exceed 30,000 first-degree connections. We will go deep on what to do as you approach this number in Chapter 7.

IP threshold: 7 distinct IPs in 90 days triggers review. This is one of the most important and least-discussed compliance metrics. We will go deep on the proxy infrastructure question in Chapter 8.

Message volume: 50 messages per day, 250 per week. This includes connection request messages, follow-ups, and InMail responses. Messages get less scrutiny than connection requests but are not unlimited. New accounts should stay below 30/day for the first 60 days.

Profile views: 100-150 per day. This is generous and rarely the binding constraint. Profile views are the lowest-risk action LinkedIn tracks.

Search results pagination: stop at page 100. LinkedIn's search has soft limits past page 100 (1,000 results) for free accounts and past page 100 (2,500 results) for Sales Navigator. Pushing past these tends to produce empty result sets and sometimes triggers review. Filter your search instead of paginating deeper.

Acceptance rate floor: 25%. If your acceptance rate falls below 25% over a rolling 7-day window, your targeting or your message is wrong, and LinkedIn's systems are noticing. We pause and re-tune at 30%, hard-stop at 25%. Acceptance rate is one of the strongest behavioral signals LinkedIn weighs. A high acceptance rate buys you grace. A low one accelerates restrictions.

Reply rate floor: 8% on follow-up sequences. Lower than this and your messages look unwelcome. We pause and re-tune.

These are the numbers. Memorize the first three: 25-30 per day, 100 per week, 8-12 minute jitter. If those three are right, almost everything else falls into place.

SECTION 06Chapter 5: What SC Never Does

A field guide is as much about what you do not do as what you do.

We never send identical templates without variables. Every connection request template has at least three personalization variables. We will refuse to run a campaign whose templates do not vary across recipients. LinkedIn's pattern detection on identical message bodies is one of the most reliable triggers for review.

We never send during off-hours. No 2am sends. No 11pm sends. No Saturday sends unless the account is in a region where Saturday business activity is normal. The platform clock matches the rep's stated local time. If a rep is traveling, we adjust to their actual location.

We never burst. Bursting means sending 15 actions in 20 minutes followed by 4 hours of silence. This is the single fastest way to look like a bot. Our cadence is paced across the day in clusters of 4-6 actions separated by 20-40 minute lulls.

We never run from a shared IP. Every account runs through dedicated infrastructure. Two clients sharing an IP looks to LinkedIn like one entity running two accounts, which is a violation.

We never bypass connection request limits. If LinkedIn's UI says you have hit the weekly limit, we stop. We do not retry. The weekly limit message is itself a flag, and continued attempts past it accelerate restriction.

We never ignore a phone verification screen. A phone verification is a Tier 1 warning. We pause, alert the client, and do not resume until the client has logged in manually and signed back in. We then resume at 60% volume for 7 days.

We never run multiple campaigns into the same target. If a client has overlapping campaigns, we deduplicate the audiences. Hitting the same prospect from two campaigns at once is the appearance of automation and irritates the prospect.

We never run concurrent first-degree connections and InMails to the same person. Pick one channel per attempt.

We never auto-endorse, auto-like, or auto-comment. Sales Connector does not run engagement automation. The platforms that do are the ones whose accounts get banned in waves.

We never scrape beyond what the user can see. We pull only data rendered to the user during active browsing. We do not fetch hidden fields, call private APIs, or scrape from places LinkedIn does not show. The technical fingerprint of out-of-band scraping is detectable.

We never bulk-import a CSV without warmup. New audiences ramp in batches: 10 prospects day 1, 15 day 2, 20 day 3, then full cap. This protects acceptance rate.

SECTION 07Chapter 6: What SC Always Does

The mirror image of the never list. These behaviors run on every account, every day, with no exceptions.

We always warm up new accounts. A new account does not run automation for the first 14 days. The rep logs in manually, builds out the profile, accepts incoming connections, sends 5-10 connection requests per day by hand, posts content, and engages. Days 15-21: 50% of target volume. Days 22-28: 75%. Day 29 onward: full volume.

We always pace. Even when the queue has 5,000 items, even when the client is anxious, we never accelerate to clear backlog. Pacing applies regardless of demand.

We always rotate templates. Every campaign has at least 3 variants, randomized per recipient, not round-robin.

We always honor opt-outs. Anyone who replies negatively is removed from all current and future campaigns, across all clients. Sales Connector maintains a global suppression list. If a prospect tells one client to stop, they are off-limits to every other client running through us.

We always log every action. Audit trail at the action level. If a question comes up about what was sent on whose behalf at what time, we have the answer.

We always hold a daily ceiling. No matter what override the client requests, we hold a ceiling we believe is safe. We will negotiate the ceiling but will not violate it.

We always check the acceptance rate weekly. Monday review on every campaign. Below 30% we tune; below 25% we pause.

We always alert on Tier 1+ warnings. Any phone verification, any unusual activity message, any restriction notice fires an alert to the AM and the client within 30 minutes.

We always have a recovery playbook. Every account has a documented plan for what happens at each tier of restriction. We do not improvise during incidents.

SECTION 08Chapter 7: The 30,000 Wall

LinkedIn's 30,000 connection cap is a hard ceiling. There is no way to raise it. Every connection request you accept counts against it. Every connection that disconnects from you frees up a slot. There is no algorithmic finesse that gets you past 30,000.

This wall is mostly a problem for senior reps with long-tenured accounts and for company-owned accounts that have been used for outbound for years. New accounts have decades before they have to think about it. But if you are running outbound on a network of 22,000+, you need to plan for the wall starting now.

Here is the staged plan we run for clients approaching the wall.

At 25,000 connections. This is the early warning. Begin auditing your network. Use LinkedIn's "My Network" filter to identify connections you have never messaged, who have never engaged with your content, whose company no longer exists, or who are clearly not relevant to your current ICP. Build a list. Do not delete yet, but build the list. Sort by "connected on" ascending to find the oldest, often least-relevant connections.

At 27,000 connections. Begin decommissioning. Disconnect 50-100 connections per week. Spread it out. Mass disconnection is a signal LinkedIn watches. We use the same pacing logic as outbound: small batches with jitter, in-business-hours, with variation in the disconnect motion (some via the My Network page, some via the connection's own profile). We aim to disconnect about 1,000 over a 4-6 week window, which is enough to buy real headroom.

At 28,500 connections. Slow new connection requests. Drop daily volume to 15-20. The math is simple: if you are sending 25/day and getting 30% acceptance, you are adding 7-8 connections/day or 50+/week. At 28,500 you have 1,500 slots. If you do nothing, you hit the wall in 30 weeks. Slowing new requests buys time for the decommissioning to catch up.

At 29,500 connections. Stop new connection requests entirely. Switch the campaign to InMail-only or message-only-to-existing-connections mode. Continue decommissioning at 100/week. LinkedIn's UI starts to throw errors near 30,000 even if you try to send requests, and those errors compound into review triggers.

At 30,000 connections. Hard stop. Every new acceptance that pushes you over a recent disconnect creates strange edge-case states that LinkedIn does not handle well. Run the account in InMail and existing-network mode for 60-90 days while you work the count back down to 28,000, and then resume slow growth.

There is a second strategic option at the wall: open a new account for outbound and preserve the 30,000-connection legacy account for relationship management and content. This is what most senior reps eventually do. It is not a defeat; it is a recognition that the legacy account has become a different asset class than the prospecting account.

If you are at 28,000 today, start the decommissioning conversation now. The plan is gentler when you have time. The plan is brutal when you don't.

SECTION 09Chapter 8: The 7-IP Threshold and Why Proxy Infrastructure Matters

This is the section almost every compliance guide skips. It is one of the most important.

LinkedIn fingerprints accounts not just by what they do but by where they do it from. The "where" includes the IP address, its reputation, its geography, its consistency over time, and its relationship to other LinkedIn accounts. An account that has logged in from 17 different IPs in a month, half of which are data center ranges, is a dead account walking.

The threshold we observe in practice: around 7 distinct IPs in a rolling 90-day window triggers heightened scrutiny. We treat 7 as a hard ceiling and engineer around 3-4 as a target. A real human logs in from home, work, occasionally a coffee shop, occasionally their phone. That is 3-4 IPs over a quarter.

Why does this break for outbound teams? Three reasons.

First, the rep runs Sales Connector on their work laptop, logs in to LinkedIn from their phone at lunch (cellular IP), opens LinkedIn on their personal laptop in the evening (home IP), travels for a sales conference (3 hotel IPs in a week), and comes back to the work IP, while Sales Connector is also touching the account from its dedicated IP. Six IPs across two weeks.

Second, agency setups. An agency running outbound for a client logs in from the agency office plus three different remote-work locations across staff, plus the client's own occasional logins. This pattern is one of the most common reasons agency-managed accounts get flagged faster than self-managed ones.

Third, VPN sloppiness. Reps who toggle a corporate VPN produce wild IP geography. LinkedIn sees a rep in Austin one minute and Singapore the next. This pattern alone can trigger phone verification.

What proxy infrastructure does for you. Sales Connector runs every client account through dedicated proxy infrastructure. We use residential IPs, geographically pinned to the rep's stated location, with high consistency over time. We do not use shared data center proxies under any circumstance.

Sales Connector's contribution to the IP fingerprint becomes one stable IP that matches the rep's geography. The rep adds their own home and work IPs as human-driven sessions. The total trail stays at 3-4 IPs.

If you are running outbound without dedicated proxy infrastructure, you are running on borrowed time. LinkedIn's IP fingerprinting has become significantly more sophisticated since 2023, and the cost of getting this wrong has gone up.

If you are an AM or WL partner running multiple client accounts, the rule is tighter: each client account gets its own proxy IP. Two of your clients sharing an IP looks to LinkedIn like one fraudulent operator running two accounts. We provision proxy infrastructure 1:1 with accounts, not 1:N with clients.

SECTION 10Chapter 9: The 4 Tiers of Restriction Warnings

LinkedIn's enforcement is graduated. There are four distinct tiers, and the response to each is different. Knowing which tier you are at is the difference between recovery and loss.

Tier 1: Phone Verification

What it looks like. A login screen asking for a phone number to receive an SMS code. Sometimes asks for a re-entered password. Account is otherwise functional.

What it means. Something anomalous: a new IP, a velocity spike, a templated-message pattern, or a spike in connection requests. The lightest possible touch.

What to do.

1. Stop all automation immediately. Pause the campaign.
2. Rep logs in manually and completes verification.
3. Do not resume automation for 48 hours.
4. Resume at 60% of prior volume for 7 days.
5. Audit the prior 14 days. Look for a burst, an off-hours session, low acceptance rate, or a new IP. Find the cause.
6. Document in the compliance log.

What not to do. Do not skip verification. Do not resume while the screen is up. Do not assume "one-time thing." Tier 1 warnings repeat unless you address the root cause.

Tier 2: Unusual Activity Notice

What it looks like. A more prominent warning, often with a forced password reset or temporary feature limitation (e.g., connection requests disabled for 24-72 hours).

What it means. The system has high confidence the activity does not match normal user behavior. Things are getting serious.

What to do.

1. Stop all automation for a minimum of 7 days. Non-negotiable.
2. Rep logs in manually and addresses the screen.
3. Full 30-day audit: connection volumes, acceptance rates, templates, IP usage, setting overrides.
4. Reset recovery email; ensure 2FA is on.
5. Resume at 40% volume for 14 days, 70% in week 3, full in week 4.
6. If on Sales Navigator, verify the seat is in good standing.

What not to do. Do not resume at full volume assuming the warning has cleared. Tier 2 often precedes Tier 3 if behavior does not change. If a template was flagged, resuming it will accelerate to Tier 3 within days.

Tier 3: Temporary Restriction

What it looks like. Account temporarily restricted with a defined duration (24 hours, 7 days, 30 days). May be partial (cannot send connection requests) or total. Duration is set by LinkedIn and not negotiable.

What it means. Activity has been determined to violate LinkedIn's User Agreement or Professional Community Policies. One step short of permanent restriction. Appeals are reviewed by automated systems and rarely succeed at this tier.

What to do.

1. Stop all automation. Disable the campaign so it cannot auto-resume.
2. Wait out the restriction. Do not log in repeatedly; some restrictions extend with repeated attempts.
3. If there is an appeal option, use it only if honest. Cookie-cutter appeals are denied immediately.
4. The day the restriction lifts: rep logs in, posts content, accepts legitimate connections, behaves human before any automation resumes.
5. Resume at 25% volume. Do not exceed 50% for the first 30 days.
6. If the cause was templated messaging, rewrite the templates entirely.
7. Begin preparing a backup outbound plan. This account may not survive a future incident.

What not to do. Do not panic-message prospects who were mid-conversation; threads resume if the account comes back. Do not contact LinkedIn support outside the appeal mechanism. Do not log in from a new IP during the restriction.

Tier 4: Permanent Restriction

What it looks like. Account restricted with no end date. Single appeal mechanism. Reviewed once. Final.

What it means. The account is gone. Recovery rates from this tier are in the low single digits, mostly only when the account was demonstrably compromised by a third party.

What to do.

1. Submit an honest appeal if you have genuine cause (compromise, mistaken identity, verifiable evidence the activity was within terms).
2. Do not submit boilerplate appeals.
3. If denied, accept the loss. Continued attempts to circumvent (new IP, similar account) trigger broader IP-level and identity-level restrictions affecting any new accounts you create.
4. Rebuild a new account using the warmup protocol. Communicate the change to active prospects through email.
5. Conduct a full post-mortem with the AM and the rep. What was the cause? What signs were missed? What changes prevent the next account from following the same path?

What not to do. Do not create a new account from the same IP and device fingerprint. Do not reuse the same recovery email, profile photo, or full name combination if a plausible variant exists. Do not import the same templates and pacing; they caused the previous restriction.

SECTION 11Chapter 10: The 5 Most Common Causes of Restrictions

In aggregate across our client base, the same five patterns produce most restrictions. If you avoid these five, you avoid 90% of the risk.

1. Templated messaging without variation. The single most common cause. A rep writes one connection request message, decides it is "the one," and runs it without rotation across hundreds of recipients. LinkedIn's content pattern detection flags it within 100-300 sends. Variation is not optional. Three template variants minimum, real personalization variables, periodic rotation.

2. Volume spikes. A rep ramps from 5/day to 50/day overnight because they got excited about a new audience or because the AM raised the cap. Volume is allowed to grow, but it must grow gradually. The platform's anomaly detection looks at first and second derivatives of volume, not just absolute volume.

3. Low acceptance rate. When a rep targets the wrong audience, sends weak messaging, or pushes a list past its useful end, acceptance rates fall below 25-30%. LinkedIn interprets low acceptance as evidence of unwanted contact and accelerates restriction. Acceptance rate is a steering signal: low acceptance means stop and tune.

4. IP and device sprawl. Covered in Chapter 8. More than 7 IPs in a quarter, or shared IPs across accounts, or use of low-reputation data center proxies. The LinkedIn account is a stable identity in their model. Wild IP patterns break the model.

5. Off-hours and burst patterns. Sending at 3am, sending all 30 daily requests in a 90-minute burst, or sending on holidays. Real users do not exhibit these patterns. Bots do.

The other 10% of restrictions are mostly caused by a sixth-place cluster: aggressive scraping, third-party tool conflicts, account sharing across multiple users, and reports from prospects who flagged the message as spam or as a fake account.

Do this now (Act 2)

• Open your campaign settings and confirm: daily cap is 30 or below, weekly cap is 100 or below, jitter is 8 minutes or higher, operating window is local business hours only.
• Open your message templates. Count the unique variants in rotation. If it is fewer than 3, fix this today.
• Open your acceptance rate dashboard for the past 7 days. If it is below 30%, you are working with the wrong audience or wrong message and you should pause and tune.
• Check the IP audit for your account in LinkedIn settings. If you see more than 4 IPs in the past 30 days, talk to your AM about consolidating to a stable proxy.
• Look at your lifetime connection count. If it is over 25,000, schedule the decommissioning plan from Chapter 7.

ACT 3: APPLY

SECTION 12Chapter 11: International Nuances

The numbers in Act 2 are calibrated to the United States. LinkedIn enforces unevenly across regions.

United States and Canada. Default numbers apply. 25-30/day, 100/week, 8-12 minute jitter. Highest tolerance for outbound activity.

United Kingdom and Ireland. Default numbers apply, but acceptance rate floors are higher in practice (35% target) because UK prospects respond more slowly to cold connection requests.

European Union, DACH (Germany, Austria, Switzerland). Reduce daily volume by 30%. Run at 18-22/day, 70-80/week. GDPR enforcement is stricter and prospect tolerance for cold outreach is lower. Accounts here get flagged at volumes that are routine elsewhere. Acceptance rate target is 40%.

European Union, other (France, Italy, Spain, Benelux, Nordic). Reduce daily volume by 15-20%. Run at 22-25/day. GDPR considerations apply but enforcement and tolerance are slightly higher than DACH.

UAE and Saudi Arabia. Default numbers apply, but operating window is Sunday-Thursday. Friday and Saturday are weekends; sending on Friday is an off-hours pattern.

India. Default numbers apply. High volume tolerance. Acceptance rates are typically 40-50% when targeting is good, which buys grace.

Japan and South Korea. LinkedIn is used very differently in these markets. Cold connection requests are culturally unusual. Reduce daily volume by 50-60%, run at 10-15/day, and lean heavily on warm introductions and content engagement. Acceptance rates of 15-20% are normal here even with strong targeting. If your campaign is heavily focused on Japan or Korea, talk to your AM about a fundamentally different cadence.

Australia and New Zealand. Default numbers apply. Enforcement is similar to UK.

Brazil, Mexico, Argentina, and other Latin America. Default numbers apply. High tolerance for outbound. Acceptance rates can be very high with good Portuguese or Spanish messaging.

Singapore, Hong Kong, and Southeast Asia. Slightly more conservative (22-25/day). Enforcement calibrated similarly to EU.

GDPR note. For accounts targeting EU residents, the legitimate interest balancing test under GDPR Article 6(1)(f) applies. This is separate from LinkedIn's own terms. Sales Connector provides templates and audience configurations that align with legitimate interest standards (clear opt-out language, no special category data, business-context messaging, minimal data retention), but the legal responsibility sits with the rep and their company. Talk to your legal team before running heavy EU campaigns.

SECTION 13Chapter 12: The Daily Compliance Hygiene Checklist

Five minutes a day, every working day. This is the discipline.

Daily (Monday through Friday, first 5 minutes):

• Confirm last 24 hours of campaign activity ran within configured limits. The audit log should show 25-30 connection requests, no off-hours sends, jitter intact.
• Check for any new warnings or notices on the account. Open LinkedIn, log in, look at the home screen and the notifications area. Any change in tone or new banner is a signal.
• Glance at the inbox. Any prospect replies that need same-day response should be flagged for the rep.
• Note the live connection count. Compare to yesterday. If the daily delta is wild (15+ new connections in a day), check the campaign settings.
• Note acceptance rate for the past 7 days. If it has moved more than 5 percentage points down, plan a tune.

End of day (Monday through Friday, last 2 minutes):

• Confirm that automation has paused for the evening (it should auto-pause at the end of the configured window, but verify).
• Skim the day's outgoing log. Look for any anomalies (a duplicate template send, a request to a person already in your network, a request to a flagged opt-out).
• Note any escalations to address tomorrow.

SECTION 14Chapter 13: The Weekly Review

Twenty minutes, every Monday.

Pull the weekly numbers.

• Connection requests sent: should be ≤100.
• Acceptance rate over the rolling 7 days: should be ≥30% (≥40% for DACH/EU).
• Reply rate on follow-up sequences: should be ≥8%.
• Total messages sent: should be ≤250.
• Number of distinct IPs the account logged in from: should be ≤4 over the last 30 days.
• Number of restriction warnings (any tier): should be 0.

Tune.

• If acceptance rate is below 30% (below 40% in DACH), pause the lowest-performing campaign and review the audience and the message. Most often the audience is too broad or the message is too generic.
• If reply rate is below 8%, review the follow-up sequence. Most often the second touch is too sales-y or sent too quickly.
• If total weekly volume is creeping above 100, drop daily caps by 5 and re-evaluate next week.

Audit templates.

• Pull the templates currently in rotation. Count the variants. Confirm at least 3 are active.
• Pull the last 100 connection request bodies sent. Spot-check for personalization variable failures (a "Hi {firstName}" that did not interpolate is one of the worst possible visible patterns).
• Note any templates underperforming on acceptance rate. Schedule a rewrite.

Forecast the wall.

• Note current connection count.
• If it is over 25,000, confirm the decommissioning plan is on track.
• If it is over 28,000, confirm caps are being reduced.

SECTION 15Chapter 14: The Monthly Compliance Audit

One hour, first Monday of every month, ideally with the rep, AM, and any WL partner involved.

Account health review.

• Pull the full month's audit log.
• Confirm no off-hours sends, no burst patterns, no template duplications, no IP anomalies.
• Note any near-misses: warnings that resolved on their own, a day where volume was 5% over cap, a 24-hour stretch where acceptance rate dipped under 25%. Patterns of near-misses are predictive of incidents.

Audience review.

• Are we still targeting the right audience? Has the campaign exhausted its primary audience? Is the audience drifting into low-fit territory because the high-fit prospects are already connected?
• Audience exhaustion is a top-3 cause of acceptance rate decline. The fix is not "send more"; the fix is "rebuild the audience."

Template review.

• Are we still running the templates we wrote 3 months ago? They get stale. Stale templates produce lower acceptance and higher spam reports.
• Refresh at least one template per quarter. Aim for one per month if you have the bandwidth.

Identity and security review.

• Confirm 2FA is on.
• Confirm the recovery email is current.
• Confirm the proxy IP is stable and matches the rep's stated geography.
• Confirm no unauthorized devices in the active sessions list.

Pipeline impact review.

• What is the campaign actually producing? Pipeline, meetings, replies?
• A campaign that is "compliant" but producing nothing is a waste of the account's daily budget. Compliance is not the goal; safe pipeline is the goal. Compliance is the constraint that lets you reach pipeline.

SECTION 16Chapter 15: Emergency Response: "My Account Got Restricted, What Now?"

If you are reading this section because something just happened, take a breath. Most outcomes are recoverable if the response is correct. Most outcomes get worse with panic.

Step 1: Identify the tier.

Look at exactly what the screen says. Is it asking for phone verification? That is Tier 1. Is it warning of unusual activity or forcing a password reset? Tier 2. Is it announcing a temporary restriction with a duration? Tier 3. Is it announcing a restriction with no end date? Tier 4.

Do not skip this step. The response varies dramatically by tier.

Step 2: Stop all automation.

Open Sales Connector and pause every campaign on the affected account. This is non-negotiable regardless of tier. If automation is still running while a warning is up, the situation will get worse.

Step 3: Notify.

The rep tells the AM. The AM tells Sales Connector support if the account is on a managed plan. The AM, the WL partner, and the client all need to know. Do not try to handle this silently. Sales Connector has seen every variant of this and can advise.

Step 4: Apply the tier-appropriate response.

Refer back to Chapter 9 for the detailed response per tier. The summary:

• Tier 1: pause 48 hours, resume at 60% volume.
• Tier 2: pause 7 days, resume at 40% volume, audit fully.
• Tier 3: pause for full restriction duration, resume at 25% volume, rewrite templates, prepare for backup plan.
• Tier 4: appeal once if honest cause exists, rebuild from new account if appeal fails.

Step 5: Conduct a post-mortem.

Within 14 days of the incident, even if the account fully recovers, sit down with the AM and the rep and figure out what happened. Pull the audit log for the 30 days before the warning. Look for the change. There is almost always a specific change: a new template added, a cap raised, a new audience imported, a new IP introduced. Identify it. Document it. Add it to your team's compliance log.

Emergency response flowchart.

Account warning detected
        |
        v
Identify tier (read the screen exactly)
        |
        +--- Tier 1: Phone Verification
        |        |
        |        +--> Pause automation (48 hr)
        |        +--> Rep verifies manually
        |        +--> Resume at 60% for 7 days
        |        +--> Audit prior 14 days
        |
        +--- Tier 2: Unusual Activity
        |        |
        |        +--> Pause automation (7 days minimum)
        |        +--> Rep handles screen requirements
        |        +--> Full 30-day audit
        |        +--> Resume at 40% for 14 days
        |        +--> Ramp to 70% week 3, full week 4
        |
        +--- Tier 3: Temporary Restriction
        |        |
        |        +--> Pause for full restriction duration
        |        +--> No login attempts during restriction
        |        +--> Decide on appeal (honest only)
        |        +--> Rewrite templates entirely
        |        +--> Resume at 25% post-restriction
        |        +--> Prepare backup outbound plan
        |
        +--- Tier 4: Permanent Restriction
                 |
                 +--> Submit honest appeal if applicable
                 +--> Accept loss if appeal denied
                 +--> Begin new-account rebuild
                 +--> New IP, new device fingerprint
                 +--> Full warmup protocol
                 +--> Communicate change to active prospects
                 +--> Conduct post-mortem

SECTION 17Chapter 16: When to Consider a Second Account

A single LinkedIn account has natural ceilings. The 30,000 connection wall is one. The daily and weekly volumes are another. There are legitimate and illegitimate reasons to run more than one account.

Legitimate reasons:

• The primary account is near 30,000 connections and is now a relationship-management asset rather than a prospecting asset.
• The rep has two genuinely distinct professional identities (e.g., founded a new company while remaining connected to a previous one).
• The rep is testing a new market or persona where the existing account's network is irrelevant.
• The rep has had a Tier 3 or Tier 4 restriction event and is rebuilding while preserving the original account if it survives.

Illegitimate reasons we will not support:

• Running the same campaign on two accounts to double volume. This is a violation of LinkedIn's terms and a fast path to restriction on both accounts.
• Creating a fake persona. LinkedIn's terms require accurate identity. A fake account that produces results is one report away from termination.
• Spreading suspicious activity across accounts to dilute the signal. The platform's identity-linking is sophisticated; the second account's behavior contributes to the first account's risk profile.

If you have a legitimate reason, the setup:

• Distinct LinkedIn account with the rep's actual identity. LinkedIn's policy is one account per real human; a second account for the same human must be tied to a genuinely distinct context.
• Distinct dedicated IP. Never share infrastructure between accounts even if owned by the same person.
• Distinct device fingerprint. Different browser profile, different cookies, different session.
• Independent warmup as if new, full protocol from Chapter 6.
• Separate campaigns with no audience overlap.
• Independent compliance logs and weekly reviews.

The honest answer is that most reps do not need a second account. They need a better-tuned single account. A second account doubles the operational overhead, doubles the compliance attack surface, and rarely doubles the pipeline.

SECTION 18Chapter 17: For AMs and WL Partners Running Multiple Client Accounts

If you are managing more than one client's LinkedIn outbound, the compliance challenge multiplies.

One AM, one client account, one IP, one session. Do not log into Client A's account from the same browser session as Client B's. Use separate browser profiles, separate proxy IPs, and separate password manager entries per client.

Provisioning checklist for a new client account.

• Dedicated proxy IP, geo-pinned to client's stated location.
• Dedicated browser profile or sandboxed environment.
• Client-specific 2FA and recovery email (their address, never yours).
• Documented warmup schedule, with the client's awareness and consent.
• Compliance log scoped to that client.

Cross-client contagion.

If a single client's account gets hit with a Tier 3 or Tier 4 restriction, audit your other clients immediately. If you ran any operational shortcut for Client A (a shared IP, a shared template, a shared scraping tool), that shortcut is probably present on Clients B, C, and D. Pause the highest-risk accounts, audit, and resume only when clean.

Pricing the risk.

Account management at scale has compliance overhead built into the cost. If your pricing does not reflect 2-4 hours per month of compliance work per client, you are pricing as if compliance is free. You are absorbing the risk and will eventually pay it back in lost client accounts.

Communication discipline.

Tell every client about this guide on day one. Make them sign off that they understand the daily caps, the weekly caps, and the warmup period. Document the acknowledgment. The client who insists on a 60/day cap and signs the waiver cannot claim ignorance when the account gets restricted. The client who never read the guide will absolutely claim it was your fault.

SECTION 19Chapter 18: The Long-Run Discipline

LinkedIn is not the same platform it was in 2020 or 2022 or 2024. The enforcement systems get more capable every year. The patterns that worked two years ago are increasingly the patterns that get accounts restricted today. Anyone who tells you "the rules" as if they are static is selling you something.

The long-run discipline is to stay paranoid and stay paced. The numbers in this guide are conservative on purpose, because the cost of being slightly too aggressive is asymmetric: a small win on volume, a catastrophic loss on the account.

We tell every client the same thing: the rep who runs at 25/day for three years produces more pipeline than the rep who runs at 50/day for six months and then gets restricted. Slow and steady actually wins this race, because the race has a high mortality rate at high speed.

Stay paranoid. Stay paced. Read the audit log every day. Watch the acceptance rate every week. Audit the templates every month. When the system gives you a warning, take it seriously the first time. When it gives you a second, plan for the third.

The accounts that last are the accounts that respect the operating envelope. The discipline is not glamorous. It is just the work.

Do this now (Act 3)

• Block 5 minutes on your calendar every weekday morning for the daily checklist.
• Block 20 minutes on your calendar every Monday for the weekly review.
• Block 1 hour on the first Monday of every month for the compliance audit.
• Print a copy of the emergency response flowchart in Chapter 15 and tape it next to your monitor or save it as the cover image of the rep's onboarding doc.
• If you are an AM or WL partner, email the link to this guide to every client today and ask them to confirm they have read Act 1.

SECTION 20Appendix A: The Numbers, In One Page

Hard ceilings (do not exceed):

• 100 connection requests per account per rolling 7-day window
• 250 messages per account per rolling 7-day window
• 30,000 lifetime connections per account
• 7 distinct login IPs per account per rolling 90-day window

Operating targets:

• 25-30 connection requests per account per day (US/UK/Canada/AU)
• 18-22 connection requests per account per day (DACH)
• 22-25 connection requests per account per day (other EU)
• 10-15 connection requests per account per day (Japan/Korea)
• 8-12 minute jitter between actions
• 20-40 minute lulls every 4-6 actions
• 100-150 profile views per day (rarely binding)

Acceptance rate floors:

• 30% in US/Canada/UK/AU (pause and tune below 30%)
• 40% in DACH and most EU (pause and tune below 40%)
• 25% absolute floor anywhere (hard stop, full audit)

Reply rate floor on follow-up sequences:

• 8% (pause and tune below this)

Operating window:

• Local business hours of the rep, 8am-6pm Monday-Friday
• Sunday-Thursday for UAE/KSA
• Adjusted to actual rep location during travel

Warmup schedule for new accounts:

• Days 1-14: manual only, 5-10 connection requests/day by hand
• Days 15-21: 50% target volume
• Days 22-28: 75% target volume
• Day 29 onward: 100% target volume

Post-warning resumption schedule:

• Tier 1: 60% volume for 7 days, then full
• Tier 2: 40% volume for 14 days, then 70% for 7 days, then full
• Tier 3: 25% volume for 30 days, then 50% for 30 days, then re-evaluate
• Tier 4: full new-account warmup

Weekly review checks:

• Volume within caps
• Acceptance rate within floor
• Reply rate within floor
• IP count within ceiling
• No restriction warnings

Decommissioning trigger:

• 25,000 connections: build decommission list
• 27,000 connections: begin decommissioning at 50-100/week
• 28,500 connections: drop daily volume to 15-20
• 29,500 connections: stop new requests, InMail-only mode
• 30,000 connections: hard stop, work back to 28,000 over 60-90 days

SECTION 21Appendix B: Glossary

Acceptance rate. The percentage of sent connection requests that are accepted by recipients. Measured over a rolling 7-day window. The single most important behavioral signal LinkedIn weighs.

Burst pattern. Sending many actions in a short period followed by long silence. The most common bot-like pattern.

Dedicated proxy. A proxy IP that is not shared with any other LinkedIn account or any other Sales Connector client. The opposite of a shared data center proxy.

Decommissioning. The deliberate, paced disconnection of unused or low-value connections to free up capacity within the 30,000 lifetime cap.

Geo-pinning. Keeping a proxy IP located in the same city or region as the rep's stated location, so login geography stays consistent over time.

Jitter. Randomized delay between automated actions. The opposite of fixed-interval sends.

Operating window. The hours during which automation is permitted to run. Always local business hours of the rep.

Phone verification (Tier 1). LinkedIn's lightest-touch warning, asking for SMS verification on login.

Residential IP. An IP address allocated to a residential ISP customer. Higher reputation than data center IPs for LinkedIn purposes.

Tier 1 through Tier 4. The graduated tiers of LinkedIn restriction warnings, from phone verification (Tier 1) to permanent restriction (Tier 4).

Unusual activity notice (Tier 2). LinkedIn's mid-tier warning, often accompanied by forced password reset or feature limitation.

Warmup. The 4-week graduated ramp from manual-only activity to full target volume on a new account.

WL (white-label) partner. A Sales Connector partner who runs Sales Connector under their own brand for their own clients.

This guide is maintained by Sales Connector and revised quarterly as enforcement patterns evolve. The current version applies to operations as of mid-2026. If you are reading a copy that is more than 6 months old, ask your AM for the latest version. The numbers and protocols in older versions may no longer reflect the current operating envelope.