Staying Inside Safe Sending Limits


What it does: keeps accounts alive. Every number here exists because LinkedIn restricts accounts that behave like software.

Run it when: before the first send from any account, and every time someone asks for more volume.

Time: 15 minutes to set up, then a weekly glance.

Depends on: SOP 01, Preparing a LinkedIn Account for Outreach, which starts the warm-up these limits govern.




Before you start


Every sending account connected and showing status OK

A volume target for the campaign, written as leads per week

Knowing which accounts are fresh and which are established




The steps


1. Learn the four numbers.

Connection requests: 25 per day per account is a hard ceiling, enforced in the database, with no override and nothing to negotiate. Messages: 50 a day by default. The weekly connection schedule takes per-day values from 0 to 100, but the weekly total is capped at 200. The reply agent has its own daily cap, 0 to 100. Every one of these is per LinkedIn account, not per campaign, so three campaigns on one account share one allowance.


2. Read capacity before you launch, not after.

Reachium reports each account's daily usage against its cap. Under 90 percent is fine, 90 to 99 percent is a warning, at the limit the account is full, and a limit of zero means it is blocked and sending nothing. Checking this before activation is how you avoid launching a campaign into an account that has nothing left to give today.


3. Ramp anything new or recently reconnected.

Fresh account under roughly 50 connections: 5 requests a day. Established: 10 to 15. Raise by about 5 every three to five days, varying the step so the curve is not a straight line. A reconnected account that sat idle for months is treated as new, not as established.


4. Set working hours on every account.

An account with no working-hours configuration is unrestricted and will send around the clock. Give each one a normal working window in its own timezone. This single setting removes the most obvious automation signal there is.


5. Scale with senders, never with caps.

When the target needs more volume than one account can carry, attach more accounts. A campaign takes up to 10 senders, each contributing its own safe 25 invites and 50 messages. If there are no more accounts to attach, pre-warmed rented accounts run $150 a month, arrive in the workspace within 48 hours, are ID-verified and customizable to your company, and get replaced within 72 hours if one is ever banned. There is no version of this where raising a per-account limit is the right answer.


6. Keep InMail policy deliberate.

Free InMails only reach open-profile recipients, which is why SOP 06 and SOP 11 care about open-profile status. Paid InMails are off by default and turning them on requires an explicit choice plus a daily paid cap. They consume InMail credits on every send, so decide the number before you enable it, not after the first invoice.


7. Spread load across accounts, not across hours.

Two campaigns on one account do not double its capacity; they split it. If two campaigns need to run at once, give them different senders, or accept that each runs at half speed.


8. Know what a problem looks like early.

Accept rates falling off a cliff, requests that appear to send but never show as pending, a sudden spike in withdrawn invitations, or any LinkedIn warning screen. The response is always the same: pause the campaign, stop sending from that account, and let it sit. Volume can be recovered. A restricted account frequently cannot.




Do this / Not this


Do this

Not this

Treat 25 a day as a ceiling

Treat 25 a day as a quota to hit

Add sender accounts for volume

Hunt for a setting that raises the cap

Ramp a new account over two to three weeks

Ramp it over a weekend

Set working hours per account timezone

Leave working hours unset

Check capacity before activating

Launch and wonder why nothing sent

Enable paid InMail with a cap and a decision

Enable it to "see what happens"

Pause at the first warning sign

Push through and hope it settles




Done when


Every sending account has working hours and a timezone

New accounts are on a written ramp schedule

The campaign's weekly volume target is arithmetically possible given the number of senders

Capacity checked and no account near its cap at launch

InMail policy decided, with a paid cap if paid is on

Someone owns the weekly capacity check


Powered by reachium.io