· By the AgentSDR team
The short version
LinkedIn is the channel where over-eager automation is punished most visibly: an account that gets restricted loses access to its network and its conversations, not just a campaign. The people who run LinkedIn outreach for a living converge on the same habits: small daily numbers, activity inside working hours, small bursts with real pauses, and a steady rhythm rather than spikes.
There is one honest caveat to put first. LinkedIn does not allow automation, and no safe volume makes that untrue. This guide explains how to keep activity modest and what we know about what triggers restrictions, and it ends with how AgentSDR’s LinkedIn campaigns pace themselves. It is not a way to guarantee an account is safe, because nobody can.
What LinkedIn says
LinkedIn’s help centre states that it does not permit the use of third-party software, including crawlers, bots, browser plug-ins or browser extensions, that scrapes, modifies the appearance of, or automates activity on the platform. It lists using bots or other unauthorised automated methods to add or download contacts or to send or redirect messages as a violation, and says members who use these tools risk having their accounts restricted or shut down. Read it for yourself on LinkedIn’s page, Prohibited software and extensions.
LinkedIn does not publish the thresholds its systems use, and they change over time. Treat every number you see online, including numbers in this guide, as a conservative starting point to be tested against your own account, not as a guaranteed allowance.
Invitations a day
Connection requests are the activity LinkedIn watches most closely, because they are what spammers do. Three habits keep that activity looking ordinary:
- A low daily ceiling. Think in tens, not hundreds. A person working through their own prospect list by hand might send a few dozen requests on a busy day.
- Relevance.Requests that are ignored or marked “I don’t know this person” hurt an account more than the raw count does. Target tightly.
- A short or empty note. A connection note is capped at 300 characters. Many people send the request with no note and put the pitch in the first message after acceptance.
An acceptance rate that stays healthy is the best sign you are targeting well. If it falls and you keep sending, you are teaching the platform that your requests are unwelcome.
Free vs Premium
Free accounts get a considerably smaller invitation allowance than paid ones, and LinkedIn may count it weekly rather than daily. Premium and Sales Navigator accounts have more room, but more room is not a licence to fill it. The practical advice is to size daily volume to the account type and never copy a number meant for one onto the other.
| Account | Sensible approach |
|---|---|
| Free | Very few invitations a day; the weekly allowance runs out fast. Spread them out. |
| Premium or Sales Navigator | A few dozen a day at most, in small runs, with the pacing below. |
| Brand new or recently restored account | Start lower than you would for an established one and raise it slowly. |
Messages, profile views and searches
Invitations get the attention, but the other actions count too.
Follow-up messages
Messages to people who accepted look more natural than invitations, but a burst of identical messages sent within seconds does not. Send them in small groups, vary the wording, and keep sequences short: an acceptance message and two or three spaced follow-ups is plenty. Stop the moment someone replies.
Profile views
Opening a profile is how a tool finds the person behind a lead, and viewing many profiles quickly is a known way to trip limits. Keep lookups to a handful per run.
Searches
Pulling leads from LinkedIn search results is the other activity that gets accounts limited, and heavy searching is one of the faster ways to have an account restricted. Cap how many leads you pull a day and consider building lists elsewhere and importing them.
Hours and delays
Working hours
A real member is active in the daytime of their own time zone. An account that sends invitations at 3 a.m. or on every day of the week looks different. Restrict automation to the account owner’s working hours and working days.
Randomised delays
Fixed intervals are a signature. Use a random wait between invitations, measured in tens of seconds, and a longer random rest between small runs. The pattern you are imitating is a person who sits down, sends a few requests, and goes back to other work.
Runs, not floods
Dividing a day’s volume into many small runs spreads activity through the day. Three or four invitations per run with half an hour or more between runs sends the same total as one big burst without looking like one.
What triggers restrictions
No one outside LinkedIn knows the exact rules, but these behaviours are consistently reported to put accounts at risk:
- Sending far more invitations than the account normally does, or suddenly changing volume.
- Many invitations ignored, withdrawn, or reported as unknown.
- Large bursts of actions in a few minutes, or actions at perfectly even intervals.
- Activity at all hours and on all days.
- Heavy searching and profile viewing.
- Identical messages sent to many people.
- Running the account from several tools or locations at once, which can force sign-outs and verification prompts.
If an account is limited
LinkedIn usually warns before it restricts: a message that you have reached a limit, a verification prompt, or a temporary block. Stop outreach immediately, do not try to push past the warning, and resume at a lower volume after a break. A formal restriction can require identity verification or an appeal, and a permanent ban cannot always be reversed.
Targeting and messaging matter as much as volume
Volume limits are only half of account safety. LinkedIn’s systems, and the people you contact, react to how welcome your activity is. Two accounts can send the same number of invitations and have very different outcomes, because one wrote to people who wanted to hear from it and the other did not.
Target narrowly
A tight list, with a clear reason you are writing to each person, produces more acceptances and fewer reports. Before importing, ask what you would say if the person asked how you chose them. If you have no answer, remove them.
Make the first message earn a reply
The first message after acceptance should be short and specific: one sentence on why you connected and one easy question. Avoid pitching the product in the connection note. Pasting a long sales pitch to a stranger is the quickest way to get a request marked as unwanted.
Several accounts, not one overworked one
Agencies and teams often spread volume across several accounts, each belonging to a real person who is the sender. That keeps each account’s numbers modest. It does not make borrowed or fake profiles acceptable: use accounts that belong to the people they represent, with their consent, and never create fake identities.
Measure the right things
Track acceptance rate, reply rate and the number of warnings an account has received, not just invitations sent. When acceptance falls, fix targeting before raising volume.
AgentSDR’s defaults
AgentSDR connects LinkedIn accounts through Unipile: you sign in on Unipile’s hosted page, so AgentSDR never sees your password. Pacing is a set of organization-wide Sending rules, declared once in the code with a default, hard limits and a “safe edge” past which the settings page shows a warning but still saves.
| Rule | Default | Allowed range | Warns |
|---|---|---|---|
| Invitations a day, Premium or Sales Navigator | 30 | 1 to 100 | Above 30 |
| Invitations a day, free | 5 | 1 to 50 | Above 10 |
| Invitations per run | 3 to 4 | 1 to 20 | Above 8 |
| Delay between invitations | 30 to 60 seconds | 5 to 600 seconds | Below 20 seconds |
| Rest between runs | 30 to 60 minutes | 10 to 720 minutes | Below 20 minutes |
| Follow-up messages per run | 3 to 6 | 1 to 30 | Above 10 |
| Profile lookups per run | 4 to 8 | 1 to 40 | Above 15 |
| Search leads a day, per account | 400 | 10 to 2,500 | Above 1,000 |
Each account can override its daily invitation limit and set its own working hours (timezone, start, end and days); an account’s own hours always win over the organization rule, and the engine does nothing for an account outside them. With no hours set, accounts work whenever campaigns are due.
How a run works
- Look up profiles for imported leads, a few at a time.
- Send a small batch of connection requests, within the account’s daily limit.
- Send acceptance messages and due follow-ups, a few at a time.
- Rest a random time before the next pass.
A sequence has up to five messages, all optional: a connection request of up to 300 characters, an acceptance message sent when the acceptance is detected, then follow-ups one, two and three days apart. A request whose merged text exceeds 300 characters is marked Failed, not truncated, and Preview warns when a rendered invitation is too long. A reply on any channel stops automated messages to that lead.
Guard rails
- Each request or message is claimed in the database before it is sent, so a step is never sent twice to the same lead.
- A person already contacted by an account is not invited again by it.
- Do Not Contact leads are skipped, and this is checked again right before sending.
- If a connection request fails for a reason other than a limit, AgentSDR does not retry automatically, because LinkedIn may have accepted it and a retry could send a duplicate.
These defaults reduce risk; they do not remove it. AgentSDR’s responsible use page says so plainly, and so do we.
Safe-pacing checklist
- Use an account whose loss you can absorb, and keep its profile complete and honest.
- Set the daily invitation limit by account type, and start lower than the maximum.
- Restrict activity to the owner’s working hours and days.
- Keep runs small, delays random and rests long.
- Cap searches and profile lookups.
- Target tightly and keep an eye on the acceptance rate.
- Stop at the first warning from LinkedIn and resume lower.
- Do not run the same account from several tools at once.