LinkedIn Sending Limits 2026: Safe Daily Caps and Ethical Guidelines
LinkedIn restricts accounts that send like software. The safe ceiling is 100 to 200 connection requests a week per account, and Reachium enforces a hard 25 a day per account that nobody can raise, including us. Here are the four numbers, the ramp schedule for a new account, and the warning signs that mean stop.
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, How to Warm Up a LinkedIn Account for Outreach, which starts the warm-up these limits govern.
Last reviewed September 2026.
Before you set limits
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
How to set safe LinkedIn sending limits
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.
Across 37,551 connection requests sent from Reachium accounts, the 25-a-day cap was never raised once. On Reachium it could not be: 25 a day is enforced for every account on the platform, ours included.
2. Read capacity before you launch, not after.
Reachium reports each account's daily usage against its cap on the Accounts page. 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. Check it before activation, not after.
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. Out of accounts? Pre-warmed rented accounts are $150 a month, arrive within 48 hours, are ID-verified and customizable to your company, and are 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.
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.
Safe limits: 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 |
Rather not spend three weeks warming seats? Scaling safely is mostly patience and more accounts, and our team can run that part for you. Book a call
You approve the campaign copy before anything sends.
Our inbox managers reply by hand, and they check with you first.
We hold the daily caps. 25 invites per account, no exceptions.
Month to month. No lock-in.
Questions people ask
How many LinkedIn connection requests can I send per day?
LinkedIn publishes no number. The safe working ceiling is 100 to 200 a week per account. Reachium enforces 25 a day per account in the database, for every workspace on the platform, with no override.
Will LinkedIn ban me for using automation?
Restriction is far more common than a ban, and it tracks volume and pattern rather than automation itself. Accounts that stay inside daily caps, send only in working hours and ramp over weeks are rarely restricted.
Is LinkedIn automation safe in 2026?
Yes, at human volumes. The risk is sending faster than a person could, at hours a person would not, from an account with no history. Cap the volume, set working hours, warm the account.
What happens if my account gets restricted?
Pause every campaign on that account and stop sending. Most restrictions lift on their own if the account goes quiet. Sending through a warning is what turns a temporary restriction into a permanent one.
You are 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
Do it yourself. Open your LinkedIn accounts in Reachium
Have our team do it for you. We build the lists, write the copy, run the campaigns and work the inbox. Book a call
Already a customer. Stuck on something? Book a support call
