LinkedIn channel
Profile visit · invite · DM · InMail with weekly safety caps and warmup.
- ·Unipile (recommended) and PhantomBuster supported
- ·Profile visit · invite · DM · InMail step types
- ·Hard 100-invites-per-week safety cap enforced
- ·Per-account warmup ramp on connect day 1
- ·Cookie health monitoring + auto-pause on disconnect
- ·Replies land in the shared Unibox queue
Why LinkedIn outreach gets accounts banned
LinkedIn does not publish their cap, but every account dialled past ~100 invites in 7 days starts seeing reduced visibility. Hit it twice and the account quietly stops being shown to second-degree connections — or gets restricted entirely.
- Connection acceptance rate dropped below 15% suddenly
- InMails sent but recipient never sees them
- Account flagged as 'restricted' with no warning
- Profile views dried up overnight
The detail.
The quiet 100/week wall — handled
LinkedIn does not publish their invite cap, but every account dialled past ~100 invites in a 7-day window starts seeing reduced visibility. Autocloz refuses to dispatch beyond that threshold by default, so your account stays inside the safe zone without you having to count.
Visit · invite · DM · InMail — one builder
Drop a LinkedIn step into any sequence, alongside email, call, SMS, or WhatsApp. Branch on connection acceptance, message read, or reply. The compliance gate fires before every action so a junior SDR cannot accidentally torch the team’s LinkedIn presence.
Replies stay where you can see them
InMail and connection-request replies federate into the shared Unibox, AI-tagged for intent, threaded against the same lead as their email and call activity. One queue for every channel.
Bring your own — or pick from the supported set.
The rules that keep your account alive.
Every rule below is enforced before any outbound action. The compliance gate either passes or it doesn’t dispatch.
- Hard cap at 100 invites per rolling 7-day windowWhy: Above this, LinkedIn quietly de-prioritises your profile in search and second-degree results.
- Day 1 limit of 5 invites; ramp to 20 over 14 daysWhy: Fresh accounts that immediately blast 50 invites get auto-flagged within 48 hours.
- Min-gap of 30 minutes between invitesWhy: Burst patterns are the most-cited signal in LinkedIn enforcement reverse-engineering posts.
- Auto-pause on cookie disconnectWhy: A logged-out cookie still being used is a banned-IP signal; we stop dispatching the moment we detect it.
- Always personalise the invite noteWhy: Identical-text invites at scale are the single biggest ban predictor — the AI personalisation engine fixes this for free.
A real sequence using this channel — day by day.
- Day 0Profile visitTriggers the 'who viewed me' notification — soft warm-up
- Day 1Connection invitePersonalised note · within weekly cap · same TZ as prospect
- Day 4Direct messageOnly after acceptance · feels like a conversation, not a pitch
- Day 8Follow-up DMDifferent angle · share an asset (case study, video)
- Day 14InMail (if not connected)Last touch — only if invite still pending after 14 days
“Three of my SDRs got their LinkedIn accounts restricted last year using another tool. Three months on Autocloz, zero restrictions, higher acceptance rate.”
Specific to this channel.
Will my LinkedIn account get banned?+
Not with default Autocloz settings — we cap below LinkedIn's enforcement threshold. The accounts that get banned are doing 100+ invites per day; we never let you go past 20.
Do I need LinkedIn Sales Navigator?+
Not required. Autocloz works with your existing LinkedIn account; a Sales Navigator seat simply widens who you can reach.
Can I use multiple LinkedIn accounts?+
Yes — one channel-account row per LinkedIn profile, owned by the operator who logs in to that profile. Each gets its own pacing budget.
What about LinkedIn Premium / Recruiter?+
Both supported — they raise the InMail ceiling but don't change the invite cap. We honour whichever ceiling your seat carries.