Order queue open · Verified lists delivered within 24–48 hours
How to set LinkedIn outreach limits safely in Aimfox 2026: understanding LinkedIn's weekly limits, configuring Aimfox safety settings, ramp schedules for new accounts, and warning signs before restrictions.
Marcus Chen
Outbound sales trainer, 150k+ emails sent · Updated June 23, 2026
Last updated: June 2026 · Marcus Chen, Outbound sales trainer, 150k+ emails sent
TL;DR — 7 things to know before reading
LinkedIn account restrictions are the most common operational failure in LinkedIn outreach — and the most preventable. After training hundreds of outbound teams, I have seen the same pattern repeatedly: a team starts LinkedIn automation, ignores the safety limit settings because the default feels conservative, pushes to the maximum daily volume in week one, and receives an account restriction by week three. They lose the LinkedIn profile's history, connection network, and campaign audiences in a single day.
Aimfox's safety settings exist precisely to prevent this outcome. Configured correctly, they keep your daily LinkedIn activity within LinkedIn's acceptable ranges, distribute actions with human-like randomness, and ramp new accounts gradually rather than launching at full volume. This guide covers the exact configuration, the ramp schedule for new profiles, five proven limit frameworks for different operational scenarios, a complete configuration reference, and the troubleshooting steps for every common restriction problem.
For the broader outreach operation: Quarvio provides the verified contact data that keeps campaigns targeted (broad, low-quality audiences increase restriction risk); Instantly and Inframail run the parallel email channel that does not have LinkedIn's volume constraints.
Per LinkedIn's official connection limit policy, LinkedIn monitors the rate of connection requests sent by each account and restricts accounts that exceed thresholds or display patterns consistent with automated activity.
What LinkedIn monitors:
Practical safe limits (practitioner-reported):
| Account type | Safe weekly connection requests | Daily equivalent |
|---|---|---|
| New profile (<90 days, <200 connections) | 50–75/week | 10–15/day |
| Establishing profile (90–180 days, 200–500 connections) | 75–100/week | 15–20/day |
| Established profile (180+ days, 500+ connections) | 100–150/week | 20–30/day |
| High-trust profile (2+ years, 1,000+ connections) | 100–150/week | 20–30/day |
Note: LinkedIn does not publish exact limits. These ranges are derived from practitioner testing across many accounts as reported in Aimfox reviews on G2 and LinkedIn automation tools on G2. The safe ceiling does not increase significantly with account age beyond established status — the absolute weekly limit applies broadly.
The acceptance rate factor: LinkedIn's monitoring considers the ratio of accepted to ignored connection requests. An account sending 100 requests per week with a 15% acceptance rate (85 requests ignored) triggers more scrutiny than an account sending 100 requests per week with a 40% acceptance rate (60 requests accepted). This is why audience quality and message personalisation are also safety factors, not just performance factors.
Navigate to Settings → Safety Limits in Aimfox. For each seat (LinkedIn profile), configure independently:
Daily connection request limit: Set based on the account type table above. Never set above 30 per day for any account regardless of age or connection count. The gain from 35 versus 25 per day is marginal over any reasonable campaign; the risk is not.
Daily message limit: Set to 1.5–2x the daily connection request limit. Messages go to accepted connections, not new contacts, and LinkedIn monitors them at a different threshold from connection requests.
| Account type | Daily connection requests | Daily messages |
|---|---|---|
| New profile (<90 days) | 10–15 | 20–25 |
| Establishing profile | 15–20 | 25–35 |
| Established profile | 20–30 | 35–50 |
Delay between actions: This is the setting most teams get wrong. A fixed 30-second delay between every action is detectable as automation. Set a randomised delay range:
Aimfox randomises within this range for each action, producing a human-like activity pattern. Do not reduce the minimum below 30 seconds.
Sending schedule: Configure to weekdays only, during business hours in the target audience's timezone. LinkedIn monitors accounts that send connection requests at 2am or consistently over weekends at the same daily volume as weekday sends. Set business hours to 08:00–18:00 local time for the target audience.
Weekend sends: Disable weekend sending entirely for new and establishing accounts. For established accounts, limiting Saturday and Sunday to 50% of weekday volume or zero is the safer practice.
All active campaigns for that seat will operate within these limits simultaneously. If you have 2 active campaigns for the same seat, total daily connection requests across both campaigns combined should not exceed the per-seat daily limit.
A new LinkedIn profile that launches a full-volume connection campaign on day 1 is the single highest-restriction-risk configuration. LinkedIn expects new profiles to grow connection networks organically and gradually. An account that sends 25 connection requests per day from day 1 with a sparse profile looks like an automated account to LinkedIn's systems.
6-week ramp schedule:
| Week | Daily connection requests | Daily messages | Target connection count |
|---|---|---|---|
| Week 1 | 5–8 | 10–15 | 50–100 |
| Week 2 | 8–12 | 15–20 | 100–150 |
| Week 3 | 10–15 | 20–25 | 150–200 |
| Week 4 | 12–18 | 22–30 | 200–280 |
| Week 5 | 15–20 | 25–35 | 280–380 |
| Week 6+ | 20–25 | 30–45 | 380+ |
During the ramp period, also ensure the LinkedIn profile is complete:
A complete, active profile at week 6 can safely operate at the established-account limits. A sparse profile attempting to operate at those limits will face restrictions sooner.
LinkedIn typically sends signals before a full account restriction. Recognise these early:
Warning sign 1: LinkedIn verification prompt LinkedIn asks you to verify your identity via email or phone. This is not yet a restriction — it is a precautionary measure. Complete the verification immediately, reduce daily limits in Aimfox by 30%, and increase the delay range between actions. Continue at reduced volume for 1–2 weeks before returning to normal.
Warning sign 2: Connection acceptance rate drops sharply If your campaign's acceptance rate drops from 30% to 12% in 3–5 days with no message change, LinkedIn may be throttling visibility of your connection requests. Reduce volume immediately and audit your message quality and audience targeting.
Warning sign 3: Campaign sends are hitting daily limit early If Aimfox is completing its daily connection request target faster than expected, the action delay randomisation may have drifted to lower values. Re-check the delay settings in Aimfox.
Warning sign 4: LinkedIn profile shows "Profile views" drop Unusual drops in organic LinkedIn activity signals that LinkedIn is reducing the visibility of your profile. This precedes restrictions in some cases. Reduce campaign activity and increase manual LinkedIn engagement.
LinkedIn's automation policy prohibits: scraping, fake profiles, and automated activity that violates the user experience. It does not prohibit using compliant automation tools for connection requests and messages within normal usage parameters. Aimfox operates via standard LinkedIn connection mechanisms, not scraping or API abuse. Operating within the safety limits described in this guide keeps campaigns within LinkedIn's acceptable use parameters.
Configuring Aimfox safety limits is not a one-size-fits-all decision. The right limits depend on your account's history, your operational setup, and your current campaign objectives. These five frameworks cover the most common configurations.
Who this is for: An individual operating a single LinkedIn seat who wants to build to maximum safe volume over 3–4 months.
Configuration approach: Start at 10 connection requests per day in week 1 regardless of account age. Increase by 3–5 per week. At week 8, evaluate if acceptance rate is above 25%; if yes, continue increasing. Target ceiling: 25 per day by week 10.
Key settings:
Why this works: Gradual volume increase builds LinkedIn trust signals progressively. The solo operator has full visibility into their single account's signals, making it easy to spot warning signs early and adjust in a single configuration change.
What to watch: Monitor the weekly acceptance rate in Aimfox Analytics each Friday. If the rate drops by more than 8 percentage points week-over-week without a message change, pause the ramp for 1 week before continuing.
Parallel channel setup: At week 6 (approximately 15 connection requests per day), introduce a parallel Instantly email sequence for the same audience contacts who have email addresses from Quarvio. The email channel compensates for LinkedIn volume constraints with no additional LinkedIn risk.
Who this is for: An agency or team operating 5–20 LinkedIn seats simultaneously across different client profiles.
Configuration approach: Each seat must be configured independently based on that specific LinkedIn profile's age and history. Never copy one seat's settings to another. Create a seat audit spreadsheet tracking: account age, connection count, current daily limit, restriction history, acceptance rate last 30 days. Review and update this spreadsheet monthly.
Key settings (per seat category):
Why this works: Multi-seat operations fail when someone applies the highest-trust seat's limits to a new seat "to get more volume." Each seat's LinkedIn profile has its own trust level with LinkedIn's systems; those trust levels are not transferable between seats.
Stagger campaign launches: When adding a new seat to an agency operation, do not launch campaigns from that seat immediately. Connect the seat to Aimfox, configure conservative limits, and run it at low volume (10/day) for 2–3 weeks before assigning it to an active client campaign.
Rotation strategy: For large audiences, rotate campaigns across seats rather than running the same audience from a single seat. If a 500-contact audience needs to be contacted over 4 weeks, split 250 contacts per seat across 2 seats rather than having 1 seat send 125/week.
Who this is for: An account that has received a LinkedIn restriction and is recovering to operational status.
Configuration approach: After the restriction lifts (typically 3–7 days), restart from the absolute floor. Treat the account as if it were brand new regardless of its prior history.
Recovery ramp:
| Week post-restriction | Daily connection requests | Daily messages |
|---|---|---|
| Week 1–2 | 5–8 | 10–15 |
| Week 3–4 | 8–12 | 15–20 |
| Week 5–6 | 12–15 | 20–25 |
| Week 7+ | 15–20 | 25–35 |
Never return to pre-restriction volume in the first 4 weeks. A restricted account that immediately resumes at its previous volume is highly likely to be restricted again within 2 weeks.
Message audit required: Before resuming campaigns, audit the message used in the campaigns that triggered the restriction. Low acceptance rate (under 20%) is a common contributing factor. Rewrite the connection request to be more specific and audience-relevant. Test the new message on 30 contacts before scaling.
Profile completeness check: A restriction is also an opportunity to improve profile completeness. Add a recent professional post, request 1–2 recommendations, and ensure the headline and summary are current. Profile completeness correlates with acceptance rate, which correlates with long-term restriction avoidance.
Who this is for: An operator running campaigns to a very specific ICP where the goal is maximum acceptance rate, not maximum volume.
Configuration approach: Keep daily volume intentionally low (15 connection requests per day for even an established account) while investing in message quality and audience precision. The goal is 35%+ acceptance rate, not 25%+ at high volume.
Key settings:
Why this works: A 15/day campaign with 40% acceptance rate delivers 6 new connections per day, each of which proceeds to a follow-up sequence. A 30/day campaign with 18% acceptance rate delivers 5.4 new connections per day. The narrow targeting framework produces similar or better pipeline with lower restriction risk.
Audience quality requirement: This framework only works with a precisely matched audience. Quarvio contact lists filtered to a specific job title, industry vertical, and company size range are the correct audience source for this framework. Broad LinkedIn search URLs produce audiences that are too mixed for the narrow targeting approach to work.
Who this is for: A LinkedIn profile that has been inactive for 60+ days and is being reactivated for outreach campaigns.
Configuration approach: A dormant account that suddenly resumes high-volume outreach after months of inactivity is flagged by LinkedIn's systems because the activity pattern is inconsistent with the account's history. Treat reactivation like a new account warm-up.
Re-warming ramp:
| Week | Manual LinkedIn activity | Aimfox daily connections | Notes |
|---|---|---|---|
| Week 1 | Daily: 5–10 post likes, 2 comments | 0 (no automation) | Establish organic activity pattern first |
| Week 2 | Daily: 5 post likes, 2 comments, 1 share | 5–8 | Low automation alongside manual activity |
| Week 3 | 3 manual actions/day | 10–12 | Automation can run more of the volume |
| Week 4+ | Maintain some manual activity weekly | 15–20 | Target operating range |
Why manual activity matters during re-warming: LinkedIn's activity score for an account includes all activity: posts, comments, shares, connections, messages. An account that is only sending connection requests via automation but has no other LinkedIn activity looks abnormal. Manual engagement alongside automation creates a more complete, human-like activity fingerprint.
This table covers every safety-relevant setting in Aimfox and the recommended value for each account tier.
| Setting | Location in Aimfox | New account | Establishing account | Established account | Notes |
|---|---|---|---|---|---|
| Daily connection requests | Settings → Safety Limits | 10–15 | 15–20 | 20–30 | Per seat, across all campaigns |
| Daily direct messages | Settings → Safety Limits | 20–25 | 25–35 | 35–50 | 1.5–2x connection limit |
| Daily profile views | Settings → Safety Limits | 30–50 | 50–80 | 80–100 | Optional; can disable |
| Min delay between actions | Settings → Safety Limits | 45 seconds | 40 seconds | 30 seconds | Never below 30s |
| Max delay between actions | Settings → Safety Limits | 120 seconds | 120 seconds | 90 seconds | Always randomised range |
| Delay type | Settings → Safety Limits | Random | Random | Random | Never fixed delay |
| Active hours start | Settings → Schedule | 09:00 | 08:30 | 08:00 | Target market timezone |
| Active hours end | Settings → Schedule | 17:00 | 17:30 | 18:00 | Target market timezone |
| Weekend sending | Settings → Schedule | Disabled | Disabled | Optional (50% vol) | Disable for B2B audiences |
| Randomise send times | Settings → Schedule | Enabled | Enabled | Enabled | Non-negotiable |
| Stopping rule: on reply | Campaign settings | Enabled | Enabled | Enabled | Stop all steps on reply |
| Stopping rule: on accept | Campaign settings | Enabled | Enabled | Enabled | Move to follow-up only |
| AI personalisation | Campaign settings | Enabled | Enabled | Enabled | Higher acceptance = lower risk |
| Max connection request steps | Campaign settings | 1 (no follow-up) | 1 | 1 | Connection requests = 1 message |
| Follow-up messages | Campaign settings | 2–3 | 2–3 | 3–4 | To accepted connections only |
The following tables provide exact settings for every configurable parameter that affects account safety and outreach volume. Use these as the reference when setting up a new seat, auditing an existing configuration, or diagnosing a restriction risk.
| Parameter | New (<90 days, <200 connections) | Establishing (90–180 days, 200–500 connections) | Established (180+ days, 500+ connections) |
|---|---|---|---|
| Daily connection requests | 10–15 | 15–20 | 20–30 |
| Daily direct messages | 20–25 | 25–35 | 35–50 |
| Weekly connection total | 50–75 | 75–100 | 100–150 |
| Minimum action delay | 45 seconds | 40 seconds | 30 seconds |
| Maximum action delay | 120 seconds | 120 seconds | 90 seconds |
| Delay type | Randomised range | Randomised range | Randomised range |
| Weekend sends | Disabled | Disabled | Optional at 50% vol |
| Active hours start | 09:00 | 08:30 | 08:00 |
| Active hours end | 17:00 | 17:30 | 18:00 |
| Timezone | Target audience timezone | Target audience timezone | Target audience timezone |
| Week | Aimfox daily limit setting | Expected total connections | Notes |
|---|---|---|---|
| 1 | 8 | 40–56 | Conservative start; complete profile |
| 2 | 12 | 60–84 | Increase if acceptance rate above 20% |
| 3 | 15 | 75–105 | Standard new account progression |
| 4 | 18 | 90–126 | Profile should have 200+ connections |
| 5 | 20 | 100–140 | Approaching establishing threshold |
| 6+ | 22–25 | 110–175 | Sustained ceiling for most accounts |
Increase limits only when the previous week's acceptance rate was above 25% and no LinkedIn warning signals appeared. Never increase by more than 5 per step.
| Seat daily limit | Active campaigns | Per-campaign limit | Rule |
|---|---|---|---|
| 15/day | 1 | 15/day | Single campaign fills limit |
| 20/day | 2 | 10 each | Equal split |
| 25/day | 2 | 15 and 10 | Prioritise highest-intent audience |
| 25/day | 3 | 8–9 each | Low per-campaign volume; consider consolidating |
The seat's daily limit is the hard ceiling across all campaigns. Configure individual campaign limits explicitly rather than relying on the seat cap as the sole constraint.
| Acceptance rate | Interpretation | Recommended action |
|---|---|---|
| Above 35% | Excellent audience-message fit | Hold current volume; consider incremental increase |
| 25–35% | Healthy | Maintain current configuration |
| 20–25% | Below optimal | Audit message; tighten ICP |
| 15–20% | Poor fit or message problem | Pause; rewrite connection request |
| Below 15% | Urgent action required | Stop campaign; restriction risk elevated |
Acceptance rate trends matter as much as absolute values. A declining trend from 32% to 24% over 3 weeks requires action even if 24% is above the minimum threshold — the direction indicates a developing problem.
| Week post-restriction | Daily limit setting | Notes |
|---|---|---|
| 1–2 | 5–8 | Absolute minimum restart; no exceptions |
| 3–4 | 8–12 | Increase only if no warnings |
| 5–6 | 12–15 | Approaching establishing-account range |
| 7+ | 15–20 | Full re-establishment range; monitor weekly |
Do not attempt to return to pre-restriction limits within the first 4 weeks. A re-restricted account typically has a longer recovery timeline than the initial restriction. Accept this reality rather than pushing through it.
| Check | Verification | Pass condition |
|---|---|---|
| Per-seat daily limit set | Aimfox → Safety Limits | Correct tier value for this account |
| Delay type is randomised | Aimfox → Safety Limits | Range (not fixed value) |
| Active hours are business hours | Aimfox → Schedule | 08:00–18:00 target timezone |
| Weekend sends appropriate | Aimfox → Schedule | Disabled for new/establishing accounts |
| Multi-campaign volume accounted for | Campaign settings | Combined daily volume within seat limit |
| Stopping rule on reply active | Campaign settings | Enabled for all sequence steps |
| Stopping rule on removal active | Campaign settings | Enabled |
| AI personalisation enabled | Campaign settings | Enabled for better acceptance rate |
Symptom: You launched a campaign Monday, and by Friday you received "Your account has been temporarily restricted" in LinkedIn.
Cause: Starting volume was too high for the account's age and history. New or recently dormant accounts cannot absorb 20–30 connection requests per day in week 1. LinkedIn's systems flagged the activity spike as automated.
Fix: Stop all Aimfox campaigns for that seat immediately. Complete any verification LinkedIn requests. Wait 7 days. When resuming, start at 5–8 per day and follow the 6-week ramp strictly. Do not return to the original daily limit for at least 6 weeks after the restriction lifts.
Symptom: Your campaign was producing 30% acceptance rate for 2 weeks. This week it is at 12% with no changes to message or audience.
Cause: Most likely one of three things: (1) LinkedIn is throttling visibility of your connection requests as an early warning signal, (2) your audience segment has been largely exhausted and the remaining contacts are lower-quality, or (3) a connection request sent to someone who reported it as spam triggered a temporary visibility reduction.
Fix: Pause the campaign. Reduce daily limit by 30%. Wait 48 hours. Resume at reduced volume. If acceptance rate recovers to 20%+, increase volume gradually over 2 weeks. If it remains below 20%, audit the message. A message that was working but stopped working often needs a refreshed opener even with the same audience.
Symptom: You set a 20 per day limit, but Aimfox is completing all 20 connection requests by 10am instead of distributing them through the day.
Cause: The active hours window is too narrow, or the maximum delay between actions is too short. If active hours are 09:00–10:00 (accidentally set to 1 hour) and delay is 30–60 seconds, Aimfox can theoretically complete 60–120 actions per hour, exhausting the daily limit very quickly.
Fix: Check Settings → Schedule. Verify active hours are set to 8–10 hours, not 1–2. Increase the maximum delay between actions to 120 seconds. Enable "Randomise activity times" to distribute actions throughout the window. After adjustment, Aimfox should spread daily actions across the full active window.
Symptom: LinkedIn asks you to verify your identity (email or phone) every 7–10 days even after completing the verification each time.
Cause: The daily volume is consistently at or above LinkedIn's detection threshold for the account's current trust level. Each verification completion resets the immediate flag but does not address the underlying pattern that triggered it.
Fix: After the third verification prompt, reduce daily connection requests by 50% and hold at that level for 3 weeks. This is LinkedIn signalling that the volume is not sustainable for this account. Attempting to push through repeated verifications at the same volume typically escalates to a full restriction within 4–6 weeks.
Symptom: Active campaigns show as "paused" in Aimfox without you manually pausing them. LinkedIn sending has stopped.
Cause: Aimfox has detected a LinkedIn anomaly (CAPTCHA, login challenge, or session expiry) that requires manual intervention before campaigns can resume. This is a safety feature, not a bug.
Fix: Log into LinkedIn directly (not through Aimfox) and complete any verification or CAPTCHA that appears. If LinkedIn is showing normally with no prompts, disconnect and reconnect the LinkedIn seat in Aimfox (Settings → Seats → Reconnect). After reconnection, campaigns can be manually resumed. If LinkedIn shows a restriction notice, follow the post-restriction recovery protocol.
Symptom: Seat A (established account) runs at 25/day with no issues. Seat B (newer account) running at the same 25/day limit received a warning notification from LinkedIn after 2 weeks.
Cause: This is expected behaviour. The same daily limit has different risk profiles for different account histories. Seat A's established trust with LinkedIn absorbs 25/day without flag; Seat B's newer profile has not built that trust level yet.
Fix: Configure each seat independently. Reduce Seat B to 10–12/day immediately. Do not assume that what works for an established seat is safe for a newer seat. Reference the account type table above and configure each seat to its appropriate range, not the established account range.
Symptom: You configured active hours as 08:00–18:00 but you are seeing connection request timestamps in LinkedIn from 21:00 or 06:00.
Cause: The timezone in Aimfox is set to a different timezone than your LinkedIn account's operating timezone, or the timezone was not set at all (defaulting to UTC).
Fix: Navigate to Settings → Schedule → Timezone. Verify the timezone is set to the correct region for your campaigns. If you are targeting US prospects from a non-US account, set the timezone to US Eastern or US Pacific (whichever covers most of your audience's working hours). Save and verify by checking the active hours window after the timezone update.
Symptom: The connection request campaign is achieving 30% acceptance rate, but follow-up messages after acceptance are getting below 5% reply rate.
Cause: The follow-up sequence is sending too soon after connection acceptance (within hours, before the connection has had time to engage), the messages are too long or too sales-forward, or the sequence is sending the same message to every connection regardless of their role or interest signals.
Fix: In Aimfox campaign settings, increase the delay between connection acceptance and Step 1 follow-up to 48–72 hours. Rewrite Step 1 as a value-oriented message, not a pitch. The first follow-up should open a conversation, not close a sale. Review message length: connection follow-ups should be under 200 words. Check Aimfox analytics to identify which specific message step has the lowest reply rate and rewrite that step first.
Your connection request acceptance rate is the single most predictive indicator of approaching LinkedIn restriction risk. A campaign consistently above 28% acceptance rate is operating with good audience-message fit and low restriction risk. A campaign below 20% acceptance rate is sending connection requests that the majority of prospects are ignoring — the same signal LinkedIn uses to identify mass, untargeted outreach.
Monitor acceptance rate weekly, not monthly. A week-over-week drop of 8+ percentage points is an early warning to act: pause, audit message and audience, and resume at reduced volume. Do not wait for a LinkedIn warning notification, which arrives later in the sequence.
To improve acceptance rate without changing volume: (1) tighten audience targeting to better ICP fit, (2) enable Aimfox AI personalisation if not already active, (3) shorten the connection request message to under 200 characters to increase mobile readability.
When running outreach to audiences over 1,000 contacts, do not assign all contacts to a single seat. Distribute the audience across multiple seats, with each seat responsible for a segment of the total audience.
Example: 1,200 contacts targeted at 20/day from 1 seat = 60 working days to complete. Same 1,200 contacts split across 3 seats at 15/day each = 27 working days, with lower per-seat volume and therefore lower per-seat restriction risk.
In Aimfox, create 3 identical campaigns with segmented audience files (contacts 1–400, 401–800, 801–1,200). Configure identical messages and sequences across all three campaigns. Track combined acceptance rate in a shared spreadsheet or Aimfox's seat-level analytics.
LinkedIn accounts with active content engagement histories face fewer restrictions than accounts that only send connection requests. This is because LinkedIn's detection algorithms assess the holistic pattern of account activity, not just outbound connection request volume.
Build profile trust alongside automation by:
This manual activity takes 10–15 minutes per week per seat. The benefit is a more complete LinkedIn activity fingerprint that reduces the chance of automation-only accounts being flagged by pattern detection.
When LinkedIn daily volume limits prevent reaching a full audience within a reasonable timeframe, do not increase LinkedIn limits beyond safe thresholds. Instead, route additional contacts to email outreach via Instantly and Inframail.
Contact lists from Quarvio include both LinkedIn profile URLs and verified email addresses. Contacts who would require LinkedIn volume above safe thresholds to reach within a 2-week window can be routed to email outreach instead. Email has no equivalent to LinkedIn's weekly connection limit, and the two channels together reach more of the audience than LinkedIn alone.
This is also a risk hedge: if a LinkedIn seat receives a temporary restriction, the email channel continues uninterrupted, keeping outreach active for the full audience during the LinkedIn recovery period.
Safety limit settings that were correct for an account 6 months ago may be either too conservative (the account has matured and can support higher volume) or too aggressive (the account received a minor restriction signal that you missed). Quarterly audits keep limits optimally calibrated.
Quarterly safety audit checklist:
Ignoring Aimfox's default safety limit settings on first use: The defaults may not match your specific account profile's risk level. Configure explicitly for each seat before launching any campaign.
Running multiple campaigns per seat without accounting for combined volume: If Seat A runs Campaign X (10 requests/day) and Campaign Y (10 requests/day) simultaneously, total daily requests from Seat A are 20 per day. The safety limit applies to total daily activity across all campaigns for that seat, not per campaign.
Copying safety limits from a high-trust account to a new account: A 3-year-old profile with 1,500 connections can operate at 25 connection requests per day. A 30-day-old profile with 80 connections attempting the same volume will be restricted. Configure limits per seat based on that specific account's history, not based on another account's comfortable ceiling.
Skipping the ramp schedule: The 6-week ramp is not optional for new profiles. It is the mechanism that builds LinkedIn's trust signals for that account progressively. Skipping it and launching at full volume in week 1 produces restrictions in weeks 2–4 consistently.
Sending outside business hours: A LinkedIn account that sends connection requests at 11pm on a Tuesday or at uniform 30-second intervals over a Sunday afternoon is identifiable as automated. Configure sending schedules to business hours and enable randomised delays without exception.
Aimfox reviews on G2 consistently identify the safety limit configuration as the feature that differentiates Aimfox from lower-quality LinkedIn automation tools, with users noting that the combination of randomised delays, per-account limits, and business-hours-only scheduling allows sustained operation without account restrictions.
LinkedIn automation tools on G2 category analysis shows account restriction recovery time as the most-cited operational problem among users of all LinkedIn automation tools, with teams that configure safety limits from the start reporting significantly lower restriction rates than teams that use default settings without adjustment.
"I have 14 client seats in Aimfox. Each one is configured independently based on the profile's age and connection count. I have had zero restrictions across all 14 accounts in 8 months of continuous operation. The safety limit setup takes 5 minutes per account. The accounts that get restricted are always the ones where someone bypassed the ramp."
— Verified G2 reviewer, operations director, LinkedIn outreach agency, Aimfox on G2
"New profile, week 1: 8 per day. Week 4: 15 per day. Week 8: 25 per day. I have never had a new account restricted using this ramp. I have had accounts restricted when I skipped the ramp 'just to see' — restriction came in week 2. The ramp is not optional."
— Verified G2 reviewer, outbound consultant, independent, Aimfox on G2
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS |
| Cold email sending | Instantly | Sequences, warm-up, reply tracking |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
How many connection requests per day is safe in Aimfox?
For established LinkedIn profiles (180+ days active, 500+ connections), 20–30 connection requests per day is the safe range per practitioner data compiled in LinkedIn automation tools on G2. For new profiles, start at 10–15 per day and ramp over 6 weeks. Per LinkedIn's official connection limit policy, LinkedIn enforces weekly limits that vary by account history — the per-day limit in Aimfox should keep weekly total between 100–150 for established accounts.
What should I do if my LinkedIn account receives a restriction while running an Aimfox campaign?
Stop all Aimfox activity for that seat immediately by pausing all active campaigns. Complete any identity verification LinkedIn requests. Wait 7–14 days before resuming any campaigns. When resuming, start at 50% of the pre-restriction daily limit and ramp back up over 3–4 weeks. Audit the message quality and audience targeting for the restricted campaigns — a low acceptance rate (under 20%) is often a contributing factor to restrictions because LinkedIn interprets mass-ignored requests as spam behaviour.
Do messages (DMs) have a separate limit from connection requests in Aimfox?
Yes. Messages sent to accepted connections operate under a different (generally higher) LinkedIn limit than connection requests. In Aimfox, configure a separate daily message limit in Safety Settings. As a general rule, daily messages can be set to 1.5–2x your daily connection request limit. Messages to existing connections are less likely to trigger LinkedIn's automated pattern detection than connection requests to new contacts.
Does audience targeting quality affect LinkedIn restriction risk?
Yes, indirectly. LinkedIn monitors the ratio of accepted to ignored connection requests. A campaign targeting a broad, low-relevance audience produces a low acceptance rate (15–20%), which signals mass, untargeted outreach to LinkedIn's systems. A campaign targeting a precise, well-matched audience with personalised messages produces a higher acceptance rate (30–40%), which signals normal professional networking. Using verified contact data from Quarvio and writing audience-specific messages improves acceptance rates, which reduces restriction risk as a secondary benefit.
Can I run two Aimfox campaigns from the same LinkedIn seat simultaneously?
Yes, but the combined daily volume across both campaigns must stay within the per-seat safety limit. If your seat is configured for 20 connection requests per day, running two campaigns simultaneously means each campaign should target 10 per day (or any split that totals 20). Aimfox enforces the per-seat daily limit across all campaigns for that seat, but it is best practice to split the limit explicitly across campaigns to ensure predictable pacing.
How long does it take to reach full operating volume with a new LinkedIn account?
Following the 6-week ramp schedule in this guide, a new LinkedIn profile can reach 20–25 connection requests per day by weeks 6–8. Attempting to reach that volume faster increases restriction risk. The ramp period is also useful time to build out the profile, accumulate organic connections, and test message variants before scaling to full volume.
What is the ideal action delay setting in Aimfox?
A random delay range of 30–120 seconds is the recommended configuration for established accounts. The lower bound (30 seconds) ensures actions are not instantaneous; the upper bound (120 seconds) ensures actions are not perfectly timed. The randomisation between these values is what creates a human-like activity pattern. Fixed delays — even a fixed 60 seconds — are detectable as automation because the interval is too consistent. Always use a range, never a fixed value.
What happens if I accidentally set the daily limit too high in Aimfox and LinkedIn restricts my account?
Pause all campaigns for that seat, complete any LinkedIn verification requests, and wait for the restriction to lift (typically 3–7 days). When resuming, start at 5–8 connection requests per day regardless of the account's previous history, and follow the post-restriction recovery ramp from the framework section of this guide. Returning to a high daily limit immediately after a restriction almost guarantees a second restriction within 2 weeks. The recovery period of 4–6 weeks at low volume is necessary to rebuild LinkedIn's trust signals for the account.
Should I use the same Aimfox safety settings for LinkedIn InMail and connection requests?
InMail and connection requests are different features with different limits. Connection requests in Aimfox follow the safety settings described in this guide. InMail is a LinkedIn Premium feature with a separate monthly allotment (15–150 InMails per month depending on plan). If you use InMail in Aimfox, configure its daily volume to spread your monthly InMail credits across the full month rather than exhausting them in the first week. Standard connection request safety settings do not apply to InMail, which has its own LinkedIn-enforced monthly cap.
Does the time of day I send connection requests affect acceptance rate?
Yes. Connection requests sent during the prospect's business hours have higher acceptance rates because the prospect is more likely to be actively logged into LinkedIn when the request arrives. For B2B audiences, Tuesday–Thursday between 09:00–11:00 and 14:00–16:00 in the prospect's timezone typically produces the highest acceptance rates. Aimfox's schedule settings allow you to target these windows by setting active hours and enabling send-time randomisation within that window.
Is it possible to run LinkedIn outreach campaigns 7 days a week safely?
For new and establishing accounts: no. Weekend sending contributes to activity patterns that differ from normal professional LinkedIn behaviour and can increase restriction risk for accounts that are still building trust signals. For established accounts with 500+ connections, reduced-volume weekend sending (50% of weekday limit) is acceptable if your target audience is active on LinkedIn on weekends (which most B2B audiences are not). For standard B2B outreach, Monday–Friday is the correct sending window.
How do I know when it is safe to increase my daily connection request limit?
Increase limits when: (1) the current limit has run for at least 2 consecutive weeks with no LinkedIn warning signals, (2) acceptance rate is consistently above 25% at the current volume, (3) no LinkedIn verification prompts have appeared in the past 30 days, and (4) the account's connection count has been growing steadily. Increase by 3–5 per day, not by 10–15 at once. Monitor for 7 days after each increase before increasing again.
Safe limits protect the campaign. Verified contacts protect the acceptance rate.
Aimfox safety settings keep your LinkedIn account within platform limits. Quarvio verified contact data keeps your acceptance rate high enough that LinkedIn's systems see normal professional networking, not automated mass outreach. One-time purchase, credits valid for 12 months, no subscription.
