Safety
Zevari is built to be the slowest AI in your stack.
Six specialists take a prospect to a qualified reply, and not one of them can send without your approval until it has earned the right. Here is exactly how that is enforced, with the numbers.
Nothing happens without a person on the other side. Every message, connection request, comment, and post is staged for you first.
Deliberate by design. Actions run inside your working hours, spaced the way a person would space them, never in a burst.
When in doubt, it stops. A ceiling reached, a session in question, a check that cannot complete: the action waits, it does not guess.
You set the boundaries. The Safety Warden enforces them, and it will not let a campaign talk it out of them to hit a number.
The mechanics
None of these is a preference you could forget to set. They are how the execution layer is built, and every one of them is visible in the Safety Center while the team works.
Messages, connection requests, comments, and posts never fire on their own. A specialist drafts and queues the action; you approve it from the review surface, from inside your AI, or from a digest. This is not a setting you can leave off. It is how the execution layer is wired.
The single biggest reason accounts get restricted is an unfamiliar automation fingerprint on a browser session. Zevari connects through a managed session and never injects a scraped cookie into a headless browser, and never stores your password to log in as you.
The Safety Warden holds every sender under LinkedIn's tolerance bands for its account type: 150 connection requests a week on Free* and Premium, 200 on Sales Navigator. These are ceilings in code, not a slider we trust you to set sensibly. That weekly figure covers connection requests sent without a note - see the note below the table for what a free account can send with one.
The weekly ceiling above covers connection requests sent without a note. LinkedIn allows a free account up to 5 connection requests with a note per month, and gives Premium and Sales Navigator accounts a far larger allowance for requests that carry one. Most outreach uses a note, so a free account is spent after 5 in a month. That monthly limit is LinkedIn's own restriction on the account type, not a ceiling Zevari sets, and it is the reason Premium or Sales Navigator is the practical choice for anyone doing real outbound.
On top of the weekly ceilings there is a cap on everything the account does in a day, 400 actions on Free, 1,000 on Premium, 2,000 on Sales Navigator, and a burst limit per minute and per hour. Real people do not fire 80 requests in ninety seconds at 3am, so neither does your team.
Follow-up will not run on autopilot until ten of its messages have gone out with your approval in the last 30 days. ICP Scoring will not sort leads on its own until it has learned from your reviews. You can turn either back to reviews with you at any time.
It will not message the same person twice by accident, re-request a connection you already sent, or double-comment. New accounts ramp toward their ceilings instead of starting at them, and the team can view, react, and comment before any ask.
The numbers
Per LinkedIn account, by the kind of account it is. A new account ramps toward these rather than starting at them.
What is counted on the plan| Per account | Free | Premium | Sales Navigator |
|---|---|---|---|
| Connection requests a week | 150* | 150 | 200 |
| Messages a week | 500 | 1,000 | 2,000 |
| All actions a day | 400 | 1,000 | 2,000 |
| Burst cap, a minute / an hour | 12 / 80 | 16 / 160 | 20 / 240 |
* The weekly connection-request ceiling covers requests sent without a note. LinkedIn allows a free account up to 5 connection requests with a note per month, and gives Premium and Sales Navigator accounts a far larger allowance for requests that carry one. Most outreach uses a note, so a free account is spent after 5 in a month, which is why Premium or Sales Navigator is the practical choice for anyone doing real outbound. That monthly limit is LinkedIn's own restriction on the account type; the weekly and daily ceilings in this table are the ones Zevari enforces.
In writing
The cookie tools, the offshore VAs, and the autonomous SDRs each fail on one of these. Zevari is the opposite design on every axis.
Questions
No tool can put zero in writing, and anyone who does is not being straight with you. What we can put in writing is the mechanism: every write is staged for your approval, the connection is session-based with no browser cookies, and weekly ceilings, daily caps, working hours, burst limits, and duplicate checks are enforced in code. Zevari has recorded zero ban incidents to date.
150 on a Free* or Premium account, 200 on Sales Navigator. Those are the enforced ceilings, spaced across your working hours. A new account ramps up to them rather than starting there. Those figures cover connection requests sent without a note; requests that carry a note are limited separately on a free account.
No, and this is the distinction that matters most. The weekly ceiling covers connection requests sent without a note. LinkedIn allows a free account up to 5 connection requests with a note per month, and gives Premium and Sales Navigator accounts a far larger allowance for requests that carry one. Most outreach uses a note, so a free account is spent after 5 in a month, which is why Premium or Sales Navigator is the practical choice for anyone doing real outbound. That monthly limit is LinkedIn's own restriction on the account type, not a Zevari ceiling: the weekly and daily numbers in the table are the ones Zevari enforces.
No. A free or Premium account works. Sales Navigator raises the weekly connection ceiling from 150 to 200 and unlocks InMail. It is not required to start. If your outreach sends a note with the connection request, though, a free account is capped by LinkedIn at 5 a month, so Premium or Sales Navigator is the practical choice for real outbound.
Only a specialist you have moved to autopilot, and only after it has earned it: ten approved sends in 30 days for Follow-up, finished ICP training for scoring. Until then, and whenever you switch it back, every send waits for you.
The action waits until the window resets. It is not skipped, not retried in a burst, and not routed around. You can see the count against every ceiling in the Safety Center.
Those inject a browser cookie into a headless session, which is the most common reason LinkedIn flags an account. Zevari uses a managed, session-based connection, an approval gate on every write, and enforced pacing. The difference is activity that looks like you versus activity that looks like a script.