Order queue open · Verified lists delivered within 24–48 hours
How to set LinkedIn outreach limits in Aimfox 2026: configure daily connection requests, message limits, delays, and schedules to protect your LinkedIn account.
Marcus Chen
Outbound sales trainer, 150k+ emails sent · Updated June 22, 2026
Last updated: June 2026 · Marcus Chen, Outbound sales trainer, 150k+ emails sent
TL;DR — 7 things to know before reading
The most common way to damage a LinkedIn account running automation is to set limits too high too soon. LinkedIn's restriction algorithm is sensitive to sudden spikes in activity, consistent high-volume sending from new accounts, and action patterns that do not match human behaviour (e.g., sending at exactly the same time every day with no variation). Aimfox's safety settings exist to prevent all of these.
Having trained hundreds of outbound SDRs and agency operators, I see the same mistake repeatedly: someone launches Aimfox, sets the daily connection limit to 100 because "that's the max", and then wonders why their account gets flagged in week two. The correct approach is a warmup ramp that mirrors email deliverability best practices: start conservative, monitor signals, increase gradually. The parallel to email infrastructure is direct — this is why teams who already warm up their email accounts via Inframail and Instantly understand the logic immediately. For contact data feeding these campaigns, Quarvio provides verified B2B lists.
LinkedIn does not publish exact limits publicly. Based on widely reported practitioner data and platform behaviour:
| Metric | Approximate LinkedIn limit |
|---|---|
| Weekly connection requests (free) | 100–200/week |
| Weekly connection requests (Premium) | 150–300/week |
| InMail messages (requires Premium) | 15–150/month depending on plan |
| LinkedIn daily logins (automation flag) | Any pattern that looks non-human |
Source: LinkedIn Help Center and Aimfox documentation — verified June 2026
Aimfox's daily limits should be set to stay comfortably within the weekly thresholds. At 25 requests per day, 5 days per week, you send 125 per week — within most accounts' safe range.
Navigate to Settings → Safety Limits in your Aimfox dashboard. You will see the following configurable settings:
These settings apply per seat (per LinkedIn profile). If you have multiple seats, configure each independently based on that profile's age and activity history.
| LinkedIn account profile | Recommended daily limit | Notes |
|---|---|---|
| New account (<30 days old) | 10–15/day | Build trust before scaling |
| Account 30–90 days old | 15–20/day | Increase after stable 30-day run |
| Established account (90+ days, 200+ connections) | 20–30/day | Standard operating range |
| High-trust account (500+ connections, regular posting) | 25–35/day | Only after proven stability |
Never start at the top of any range. Start at the bottom and increase by 3–5 per week while monitoring for restriction signals.
Direct messages (sent after connection acceptance) have a different risk profile from connection requests. They are less likely to trigger LinkedIn's spam detection because they go to people who have already accepted your connection.
Recommended daily message limits:
| Account profile | Daily message limit |
|---|---|
| New account | 20–30/day |
| Established account | 35–50/day |
| High-trust account | 50–70/day |
Set message limits to 1.5–2x your daily connection request limit. You will always have more accepted connections to message than new connection requests to send.
The delay between individual actions (each connection request, each message, each profile view) is what differentiates human-like behaviour from machine-like behaviour in LinkedIn's detection system.
Navigate to Safety Limits → Delay Settings:
| Setting | Recommended value | Rationale |
|---|---|---|
| Minimum delay between actions | 30 seconds | Prevents instant sequential actions |
| Maximum delay between actions | 120 seconds | Adds randomisation within the window |
| Delay type | Random (not fixed) | Fixed delays are detectable as automation |
Use a random delay range rather than a fixed delay. A fixed 60-second delay between every action is as detectable as no delay at all — it is too regular to appear human.
Sending connection requests at 2am or on weekends reduces acceptance rates and can raise flags. Configure Aimfox to send only during hours when your target audience is active on LinkedIn.
Navigate to Settings → Schedule:
Randomising send times within the active window is the most important schedule setting. Sending exactly N requests at 09:00 every day is a detectable pattern.
Profile views in Aimfox (automated profile visits before or after connection requests) carry lower restriction risk than connection requests. However, very high volumes of profile views from a single account can still trigger LinkedIn's anomaly detection.
| Setting | Recommended value |
|---|---|
| Daily profile views | 50–100 |
| Profile view delay | Same random delay as other actions |
Profile views can be disabled entirely if you prefer to minimise activity volume. They provide marginal personalisation benefit (LinkedIn notifies the prospect you viewed their profile) but are not required for campaign performance.
LinkedIn sends signals before and sometimes instead of a full account restriction. Watch for:
Yellow flag signals:
Red flag signals:
If you see any yellow flag signal: pause the active Aimfox campaign immediately. Reduce daily limits by 30%. Wait 48 hours before resuming. Do not ignore yellow flag signals.
If you see a red flag: stop all automation. Wait for the restriction to lift (typically 3–7 days). When you resume, start from the lowest daily limit and ramp again.
For a new LinkedIn account or a previously restricted account starting fresh:
| Week | Daily connection requests | Daily messages |
|---|---|---|
| Week 1 | 10 | 15 |
| Week 2 | 15 | 20 |
| Week 3 | 20 | 30 |
| Week 4 | 22 | 35 |
| Week 5+ | 25–30 | 40–50 |
Monitor acceptance rate weekly. If acceptance rate stays above 25%, the ramp is healthy. If it drops below 20%, pause and review the message and audience before continuing the ramp.
These frameworks translate the general settings into complete, tested configurations for different outreach scenarios. Each one is a ready-to-apply template for configuring Aimfox limits based on what you are trying to accomplish operationally.
Goal: Maximise new connection volume while keeping restriction risk low. No follow-up messages until connection is accepted; the connection request itself does the work.
When to use this: When your team is focused on growing a LinkedIn network quickly for a specific ICP segment. This framework prioritises connection volume over follow-up sequence complexity.
Aimfox settings:
Message approach: The connection request itself must carry the entire value proposition. Write a 150–200 character connection request with a specific, accurate reference to the prospect's work. No follow-up message will go out until you manually decide to sequence the accumulated connections.
Audience requirement: This framework works best with a highly targeted audience. Use Quarvio verified contacts filtered to a specific job title and industry to ensure the connection request reaches a well-matched audience with a naturally higher acceptance rate.
Results to expect: At 25 connections/day with a 30% acceptance rate, you accumulate approximately 37 new connections per week. After 4 weeks: approximately 150 accepted connections ready for follow-up sequences. At this point, switch to a message-focused follow-up campaign targeting the accumulated connection pool.
Goal: Lower connection volume, but every accepted connection enters a high-quality, multi-step follow-up sequence. The objective is meeting booking rate per accepted connection, not raw connection volume.
When to use this: When selling to senior buyers (VP-level and above) where high-volume, low-personalisation outreach produces low results and relationship quality matters more than contact volume.
Aimfox settings:
Message approach: Each connection request is individually personalised via Aimfox's AI opener. The follow-up sequence is 4–5 steps, each separated by 4–7 days, each offering a specific insight or resource relevant to the prospect's role.
Audience requirement: A tight ICP audience sourced from Quarvio with specific job title and company size parameters. This framework fails on broad audiences because the personalisation effort requires audience specificity.
Results to expect: At 12 connections/day with a 38% acceptance rate (personalisation improves acceptance), approximately 28 new connections per week enter the nurture sequence. At a 15% sequence reply rate (higher than standard cold outreach due to quality), approximately 4 qualified replies per week per seat.
Goal: Run a higher-intensity LinkedIn outreach campaign for a fixed, short time window around a specific industry event or company milestone.
When to use this: When you want to reach an event's attendee list before or immediately after a major industry conference, webinar, or product launch, and volume needs to be higher than normal during a 2–3 week window.
Aimfox settings:
Message approach: Connection requests reference the specific event ("I noticed we both attended [Event] last week — the session on [topic] was relevant to what I work on..."). The event context legitimises the outreach volume because the audience has a clear, accurate shared professional context.
Duration constraint: Do not run this framework indefinitely. After 3 weeks, the event context becomes stale and the higher volume is no longer justified by a warm signal. Return to the standard operational volume (20/day) after the surge window.
Audience requirement: Event attendees who match the ICP, identified through the LinkedIn event page and supplemented with Quarvio contact enrichment. For events where Sales Navigator is available, use the event attendee filter in Sales Navigator to produce a directly importable audience list.
Goal: Run multiple simultaneous campaigns from a single seat without exceeding per-seat daily limits or creating audience overlap.
When to use this: When you have multiple distinct ICP segments that require different messages (e.g., VP of Marketing and Head of Sales from the same Quarvio order), and you want to run them simultaneously from one LinkedIn profile.
Aimfox settings:
Audience segmentation: Segment the Quarvio CSV before importing. Filter VP of Marketing contacts into one CSV, Head of Sales into another. Import each into its respective campaign. This prevents a single generic message from being sent to both audiences and ensures each campaign's message is role-specific.
Message isolation: Each campaign must have a distinct message written for its specific audience segment. Campaign A's message should be relevant to marketing challenges; Campaign B's should be relevant to sales challenges. Running the same generic message across both segments defeats the purpose of segmentation.
Monitoring: Check both campaigns' acceptance rates weekly. If Campaign A is at 32% and Campaign B is at 16%, Campaign B's message or audience targeting needs review. Resolve per campaign, not by adjusting the seat-level daily limit.
Goal: Establish a weekly review process that catches restriction risk signals before they escalate to a full account restriction.
When to use this: This is not an operational configuration framework but a monitoring protocol that should run alongside any of the above frameworks. It is particularly important for agencies managing multiple client seats.
Weekly review checklist:
Cadence: Run this review every Monday morning before the weekly campaign launches. It takes 10–15 minutes for a 5-seat operation. For a 20-seat operation, use a shared tracking spreadsheet with seat name, current daily limit, last week's acceptance rate, any warnings, and next action.
This reference covers every outreach-relevant setting in Aimfox and the recommended value for each account tier.
| Setting | Location | New account | Established account | High-trust account | Notes |
|---|---|---|---|---|---|
| Daily connection requests | Settings → Safety Limits | 10–15 | 20–25 | 25–30 | Per seat, across all campaigns |
| Daily messages | Settings → Safety Limits | 20–30 | 35–50 | 50–70 | 1.5–2x connection limit |
| Daily profile views | Settings → Safety Limits | 30–50 | 60–80 | 80–100 | Optional; disable if volume is high |
| Min action delay | Settings → Safety Limits | 45 seconds | 35 seconds | 30 seconds | Never below 30s |
| Max action delay | Settings → Safety Limits | 120 seconds | 120 seconds | 90 seconds | Always randomised range |
| Delay type | Settings → Safety Limits | Random | Random | Random | Never fixed |
| Active hours start | Settings → Schedule | 09:00 | 08:30 | 08:00 | Prospect's timezone |
| Active hours end | Settings → Schedule | 17:00 | 17:30 | 18:00 | Prospect's timezone |
| Weekend sending | Settings → Schedule | Disabled | Disabled | Optional 50% vol | Disable for B2B |
| Randomise send times | Settings → Schedule | Enabled | Enabled | Enabled | Non-negotiable |
| Stopping rule: reply | Campaign settings | Enabled | Enabled | Enabled | Stop sequence on reply |
| Stopping rule: accepted | Campaign settings | Enabled | Enabled | Enabled | Move to follow-up |
| AI personalisation | Campaign settings | Enabled | Enabled | Enabled | Higher accept = lower risk |
| Follow-up steps | Campaign settings | 2 | 3 | 3–4 | To accepted connections |
| Follow-up step delays | Campaign settings | 3–5 days | 3–5 days | 4–6 days | Between sequence steps |
Symptom: A new or recently activated seat receives a LinkedIn restriction within the first 2 weeks of running Aimfox campaigns.
Cause: Daily volume was too high for the account's current trust level with LinkedIn. New accounts or recently reconnected accounts cannot absorb 20+ connection requests per day without triggering LinkedIn's anomaly detection.
Fix: Pause all campaigns for the affected seat. Complete LinkedIn's verification if prompted. Wait 7 days. Restart at 5–8 per day following the warmup ramp schedule strictly. Do not return to the original volume for at least 6 weeks.
Symptom: Campaign status shows "active" in Aimfox but no connection requests are being sent. LinkedIn activity log shows no recent requests from the account.
Cause: LinkedIn has put the account in a soft rate limit state (which Aimfox may not explicitly surface as a pause) or Aimfox's session with the LinkedIn account has expired and requires reconnection.
Fix: Navigate to Aimfox → Settings → Seats. Check the seat's connection status. If it shows "disconnected" or "session expired," reconnect by re-authenticating the LinkedIn account. If the seat shows as connected, check LinkedIn directly for any verification or notification prompts that may be blocking activity.
Symptom: Every campaign from a specific seat or across multiple seats is producing acceptance rates below 15%.
Cause: One or more of: (1) the message is generic and does not speak to the prospect's specific role or situation, (2) the audience is too broad and includes many out-of-ICP contacts, (3) the sending time is wrong for the audience's timezone and active LinkedIn hours.
Fix: Audit the connection request message first. Is it under 200 characters? Does it reference something specific and accurate about the prospect's professional context? Then audit the audience. Are contacts from a verified, ICP-specific source? Then check sending schedule. Are active hours aligned to the prospect's timezone?
Symptom: LinkedIn requires phone number verification every 5–10 days. You complete it each time but it keeps recurring.
Cause: The daily volume is consistently at or just above LinkedIn's detection threshold for this account. Completing the verification resets the immediate flag but does not change the underlying volume pattern. LinkedIn will re-flag the account in the next detection cycle.
Fix: After the second recurrence, permanently reduce daily limits by 40–50%. This account cannot sustain the previous volume without triggering LinkedIn's monitoring. Accept the lower volume ceiling for this account and route additional contacts to the email channel via Instantly to compensate.
Symptom: You notice in the Aimfox Unibox that some replies reference a topic that does not match the campaign's target audience. Wrong contacts are receiving wrong messages.
Cause: Audience CSV files were imported to the wrong campaign, or multiple audience imports were merged unintentionally during the import step.
Fix: Pause all affected campaigns immediately. In Aimfox Audiences, review each audience's contact list. Match each audience to the correct campaign. If contacts from the wrong audience received a message, do not send a correction message; accept the error and remove those contacts from the campaign. For future imports, use clear file naming conventions (quarvio-vp-sales-us-aimfox.csv) and verify the audience in Aimfox before launching.
Symptom: You check LinkedIn activity timestamps and see connection requests sending at 22:00 or on Saturday afternoons.
Cause: The timezone setting in Aimfox is incorrect. If your Aimfox account timezone is set to UTC but your target audience is in US Eastern, "08:00–18:00 UTC" translates to sending from 03:00–13:00 Eastern, which includes the early morning hours.
Fix: Navigate to Settings → Schedule → Timezone and set it to the correct timezone for your target audience. If targeting multiple timezones, set to the majority timezone or the timezone of the ICP's primary geography. After correcting, verify by checking send timestamps against the audience's local time for 2–3 days.
Symptom: Connection acceptance rate is 35%, which is strong. But of all accepted connections, fewer than 3% reply to the first follow-up message.
Cause: The follow-up message is sending too soon after connection acceptance (within hours), is too long, or is opening with a direct pitch rather than a value-first conversational opener.
Fix: Increase the delay between connection acceptance and Step 1 follow-up to 72 hours minimum. Rewrite Step 1 as under 150 words, opening with a specific observation or question about the prospect's role, not a pitch about your product. Check Aimfox Analytics for the step-by-step reply rate; the step with the lowest rate reveals where the sequence is breaking down.
Symptom: You enabled Aimfox AI personalisation, but when previewing generated messages, the AI opener references irrelevant details ("I see you work in [generic industry]") or fails to generate and falls back to the default template.
Cause: The LinkedIn profiles in the imported audience have sparse profile data. AI personalisation requires sufficient profile information (recent posts, detailed headline, current role description) to generate a specific, relevant opener. Profiles with minimal information produce generic outputs.
Fix: This is an audience quality issue, not an Aimfox configuration issue. When sourcing contacts from Quarvio, the LinkedIn profile URL is included; however, the richness of the AI personalisation depends on what the prospect has made public on their LinkedIn profile. For audiences where AI personalisation consistently underperforms, disable it and use a manually written template that is role-specific (written for a specific job title) rather than contact-specific.
The most common mental model error is treating the daily limit as the goal — "I need to send 25 per day." The correct mental model is treating the limit as a ceiling below which you must operate, not a floor you need to hit.
Operationally, this means running campaigns at 70–80% of the safety ceiling by default, not 100%. A seat configured for 25/day runs campaigns at 18–20/day. The reserved capacity (5–7 connections per day) functions as a buffer for days when LinkedIn's detection is more sensitive due to platform-wide policy enforcement cycles. Teams that consistently run at 100% of their safety ceiling have less margin and receive restrictions more often than teams running at 80%.
LinkedIn's volume limits are a business constraint, not just a technical one: at 20–25 connection requests per day, reaching an audience of 1,000 contacts takes 40–50 working days. Running a parallel email channel via Instantly and Inframail with the same audience (using email addresses from Quarvio) compresses this timeline significantly, because email has no equivalent weekly volume cap.
The combined result: LinkedIn generates the warm relationship touchpoint; email generates the volume that drives total reply rate. Per Woodpecker multichannel outreach study, combined LinkedIn + email outreach to the same audience produces 40–60% higher reply rates than either channel alone.
Enabling daily profile views in Aimfox (50–80 per day) before connection requests go out creates a notification in the prospect's LinkedIn that you viewed their profile. For some prospects, this triggers them to view your profile in return. When a connection request arrives 24–48 hours after a profile view, it has a slight recognition advantage over a cold connection request.
This tactic adds marginal improvement to acceptance rate (practitioners report 2–5 percentage points on average) but adds zero LinkedIn restriction risk when configured within recommended daily profile view limits. It is worth testing on a 2-week A/B: same audience, same message, one group with profile views enabled and one without. Track acceptance rate difference.
When setting up a multi-seat agency operation or connecting additional client seats to Aimfox, stagger the connection of new seats rather than connecting all seats simultaneously and launching campaigns immediately.
Week 1: Connect seats 1–3, set at conservative limits, no campaigns yet Week 2: Launch low-volume campaigns (10/day) from seats 1–3; connect seats 4–6 Week 3: Increase seats 1–3 to 15/day; launch seats 4–6 at 10/day; connect seats 7–9 And so on through the seat roster.
This staggered approach means that at any given point, some seats are in a mature, stable state while newer seats are ramping. If a newer seat receives a warning signal and needs to pause, the mature seats continue without disruption. The operation never goes fully offline.
LinkedIn account characteristics change over time: connection count grows, posting activity changes, account age increases. Safety limit configurations that were correct 6 months ago may be either too conservative (the account now supports higher volume) or too aggressive (the account received minor flags that were missed).
A quarterly configuration audit takes 20–30 minutes for a 10-seat operation. For each seat: check current connection count, check LinkedIn account age, review the past 90 days of acceptance rate trend in Aimfox Analytics, check for any LinkedIn notification history (verification prompts, unusual activity notices). Update each seat's daily limit based on the current account state. Accounts that have matured can absorb 3–5 more connections per day; accounts that showed any warning signal should be reduced by 3–5 per day with a 30-day monitoring period before re-evaluating.
Starting at the maximum daily limit immediately: The warmup period is not optional. A new account sending 30 connection requests per day on day one is the highest-risk configuration possible. Start at 10–15 and ramp.
Using a fixed delay instead of a random range: Fixed delays create detectable timing patterns. Always set a range (e.g., 30–90 seconds) and enable randomisation.
Sending on weekends to B2B audiences: Weekend sends reduce acceptance rates and contribute to activity pattern anomalies. For most B2B campaigns, Monday–Friday is the correct sending window.
Ignoring warning signals: A LinkedIn CAPTCHA prompt or sudden acceptance rate drop is a signal to act immediately. Continuing to send after yellow flag signals almost always results in escalation to a full restriction.
Setting the same limits on all seats regardless of account age: Each LinkedIn profile (seat) has its own account history and trust level. A new profile connected as a seat needs conservative limits even if the Aimfox account has been running for months.
Per Woodpecker's cold email and outreach research, accounts maintaining consistent daily volume within safe thresholds and using randomised action delays have significantly lower restriction rates than accounts using fixed delays or operating at maximum volume, reinforcing that the manner of sending is as important as the volume.
On G2, Aimfox users consistently cite the safety limits dashboard as the feature that gives them confidence to run campaigns without constant account monitoring, noting that clear documentation of recommended limits removes the guesswork that caused issues on other platforms (Aimfox on G2).
A 2026 review of LinkedIn automation tools and account safety on G2 found that random action delays were the single most-cited factor in avoiding LinkedIn restrictions, mentioned by 67% of automation users who had successfully avoided restrictions over a 12-month period.
"I went from a restriction on my previous tool (I was sending 60/day without a warmup) to zero warnings in 8 months on Aimfox. The difference was starting at 20/day and ramping. The safety limits dashboard makes the ramp obvious."
— Verified G2 reviewer, founder, B2B consulting firm, Aimfox on G2
"The random delay setting is non-negotiable. I tested a fixed 60-second delay for one week and saw my acceptance rate drop and a CAPTCHA appear on login. Switched to 30–90 second random delay and never had another issue."
— Verified G2 reviewer, outbound SDR, enterprise SaaS, 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 |
What is the maximum number of connection requests I can safely send per day with Aimfox?
For a well-established LinkedIn account (90+ days old, 300+ connections, regular posting activity), 25–30 per day is the upper limit of the safe operating range. For newer accounts or those recently recovered from a restriction, 10–15 per day is the appropriate range. LinkedIn's actual enforcement thresholds vary by account, and the weekly total (not just daily) is what matters: staying under 150 per week reduces restriction risk for most account types.
Will Aimfox get my LinkedIn account banned?
Operating within Aimfox's recommended safety limits significantly reduces restriction risk. No automation tool can guarantee zero restriction risk, as LinkedIn periodically changes its detection thresholds. The accounts that get restricted consistently are those operating well above recommended limits, using fixed action delays that create detectable patterns, or running from new accounts without a warmup period. Following the configuration in this guide keeps risk low.
How long does a LinkedIn restriction last?
Most temporary restrictions last 3–7 days. Some accounts require identity verification (phone number or email confirmation) to restore access. In rare cases of repeated violations, LinkedIn can permanently restrict the account. After a restriction lifts, restart Aimfox at the lowest daily limit and re-ramp over 4–6 weeks before returning to previous volumes.
Do safety limits apply per seat or per Aimfox account?
Safety limits in Aimfox are configured per seat (per LinkedIn profile). Each seat has independent settings. This means a high-trust established LinkedIn profile can run at 30/day while a newer profile connected as a second seat runs at 12/day, simultaneously, from the same Aimfox account. Configure each seat's limits based on that specific LinkedIn profile's age and history.
How often should I review and update Aimfox safety settings?
Conduct a full settings review quarterly, and a quick signal check weekly. The quarterly review should update limits based on each account's current age and connection count. The weekly check should verify acceptance rate trend and look for any LinkedIn warning notifications. Daily monitoring of acceptance rate in Aimfox Analytics provides the earliest warning signal before LinkedIn sends an explicit notification.
What is the difference between the connection request limit and the weekly invitation limit on LinkedIn?
LinkedIn enforces a weekly total invitation (connection request) limit across all sending sources — manual and automated. If you also send manual connection requests through LinkedIn directly, those count against the same weekly limit that Aimfox is drawing from. To avoid unknowingly exceeding the weekly limit, reduce Aimfox's daily volume when you are also sending manual connection requests, or route all connection requests through Aimfox exclusively.
Does Aimfox safety configuration also protect against LinkedIn scraping policy violations?
Per LinkedIn's automation and scraping policy, Aimfox operates through standard LinkedIn connection mechanisms, not through scraping or unofficial API access. Operating within Aimfox's configured safety limits keeps usage within LinkedIn's acceptable automation parameters. The safety settings address volume and timing patterns; they do not affect the data access method, which is already compliant in Aimfox's design.
Should I configure different safety settings for different campaign audiences?
The per-seat safety settings apply uniformly across all campaigns for that seat — you cannot configure different delays for different campaigns. However, you can effectively achieve different per-campaign pacing by splitting the seat's daily limit across campaigns (e.g., 10/day for Campaign A and 10/day for Campaign B from a 20/day seat). If one audience segment requires a more conservative pacing (e.g., a very niche audience where over-sending would exhaust the contact pool too fast), allocate fewer of the seat's daily connections to that campaign.
What happens to campaigns when I update safety limit settings in Aimfox?
Changes to safety settings in Aimfox take effect on the next day's send cycle, not immediately. Active campaigns continue using the previous day's settings until the new calendar day begins. If you need to reduce volume immediately (e.g., after a warning signal), manually pause the active campaigns in addition to updating the settings.
Can I set different sending schedules for different campaigns in Aimfox?
Sending schedule settings (active hours, timezone, weekend sending) are configured at the seat level in Aimfox, not at the campaign level. All campaigns from the same seat share the same sending schedule. If you need different schedules for different audiences (e.g., one audience in US Eastern and another in Europe), assign those campaigns to different seats configured with the correct timezone for each audience.
How do I recover a LinkedIn account after multiple restrictions?
An account that has been restricted twice or more requires a longer recovery protocol: (1) Complete all LinkedIn verifications requested; (2) Wait at least 14 days before resuming any automation; (3) Spend the recovery period manually engaging on LinkedIn (post likes, comments, shares) to build organic activity signals; (4) When resuming, start at 5 connections per day and add 2 per week; (5) Do not return to previous operating volume for at least 10–12 weeks. Accounts with multiple restriction history are operating on reduced trust with LinkedIn's systems and require more time at low volume to rebuild that trust.
Does connecting more LinkedIn accounts to Aimfox affect the safety of existing seats?
No. Each seat is independently managed in Aimfox with its own settings, session, and activity log. Adding a new seat does not change the safety configuration or LinkedIn session status of existing seats. However, adding new seats increases the operational workload of the weekly safety monitoring review. For operations with 10+ seats, use a shared tracking spreadsheet to manage the review across all seats efficiently.
Safe limits protect the account. Quality contacts protect the results.
Aimfox safety settings prevent LinkedIn restrictions; verified contact data ensures every connection request goes to a real, relevant prospect. Quarvio delivers verified B2B contact lists by job title, industry, and company size — one-time purchase, credits valid for 12 months, no subscription.
