How to manage LinkedIn limits with virtual assistants

Run LinkedIn outreach through a virtual assistant without sharing your password, tripping location checks, or burning through your weekly invite pool.

Get started

Short answer

Keep the LinkedIn password with you and let the VA work through a connection tool that holds the session in one place. Give them a written volume ceiling, a script that mentions a real detail from each profile, and a clear point to hand the conversation back to you.

Why a VA logging in from another country causes flags

LinkedIn looks at the device and the network behind a login. If you check your account in New York in the morning and your VA signs in from Manila an hour later, that pattern looks like a hijacked account. The same applies if the VA uses a shared VPN that thousands of other people use. The platform can't tell your assistant from a stranger who bought a password list.

Speed is the second signal. A person who opens many profiles in a few minutes and sends the same sentence to each one looks like a script, even when a human is clicking. LinkedIn does not publish the thresholds it uses, so you can't copy a number from a blog post and assume it is safe. What you can do is keep the login in one place and keep the activity slow enough that a person could plausibly do it.

What gets accounts checked

  • The VA signs in from their own laptop in another country
  • You and the VA are both logged in at the same time from different networks
  • The VA installs a scraping extension and opens profiles in batches

What keeps the account boring

  • The VA works through one connection tool that holds the session
  • You keep the password and approve access once
  • Actions are spaced across the day instead of run in one burst

How to find your account's real limits without guessing

LinkedIn does not publish daily invite, message or profile view limits. The number moves with account age, how many invites people accept, how many people report or ignore you, and whether the account has been restricted before. A new account and an account that has sent invites for two years do not have the same ceiling.

Test in small steps. Pick a starting volume below what you think the account can take. Hold it for a full week and watch for warnings, pending invites that never get accepted, and any drop in profile views. If the week is clean, add a small amount. If you see a warning, drop back to the last clean number and stay there for a while. Stay under the ceiling every week instead of testing the maximum once.

First week

Stage
Send fewer invites than you think the account can take, then hold that number
What to do
You learn tolerance without a spike

Clean week

Stage
Add a small number only if there were no warnings
What to do
You grow inside the account's real ceiling

Warning week

Stage
Drop back to the last safe number and stay there
What to do
You stop a restriction before it starts

Set up access so the VA never holds your password

The safest setup is the one where your VA never sees the password and never signs in from their own device. Use a connection tool that authorizes through LinkedIn's own screen and keeps the session on a stable connection. The VA gets a seat inside that tool, not the keys to your account.

If you have to choose between a cheaper VA who wants your password and a slightly more expensive one who will work inside your tool, pay the extra. A password shared over chat is a password you have to change later, and a login from another country is the exact pattern that triggers a checkpoint.

  1. 1

    Connect the account once from your usual device

    Complete the LinkedIn login and any verification yourself. Do not hand the VA a code to type.

  2. 2

    Give the VA a named seat in the tool

    They should have their own login to the tool, not yours. You can remove the seat without changing your LinkedIn password.

  3. 3

    Lock the work to one interface

    The VA should not open LinkedIn in a separate browser, install extensions, or log in on a phone.

  4. 4

    Write the rules down

    One page: starting volume, message template, handoff trigger, and who can change the volume.

Write a VA outreach script that doesn't look automated

A script helps, but only when it changes with each profile. The VA needs one specific detail from each profile before they send anything: a post, a job change, a shared event, a tool the person mentions. That detail goes in the first line.

Keep the first note short. A connection request note has a character limit, and the reader decides in a second whether it is a pitch. Mention the detail, say why you are connecting, and stop. Do not put a calendar link in the first note. Do not ask for a call before they accept.

Paste this job

Connection note template:
Hi {{first_name}}, your post about {{specific_topic}} at {{company}} caught my eye. I work with {{type_of_buyer}} on the same problem. Open to connecting?

Rules for the VA:
1. Find one real detail before writing the note.
2. Keep the note under 200 characters.
3. No links, no pricing, no calendar in the first note.
4. If the profile has nothing specific, skip the lead.

Where the VA stops and you take over

VAs are good at finding the detail, sending the note, and keeping the list clean. They are bad at pricing questions, technical objections, and the moment a lead wants to talk to the person who owns the outcome. Set the handoff before you start.

Write down three triggers: the lead asks about price, the lead asks a question the VA cannot answer from the brief, or the lead asks for a call. When one of those happens, the VA tags the thread and stops. You reply within the same day. A slow handoff loses more meetings than a bad first note.

Example

  1. Suggested reply

    Hi Sarah, your post about multi-currency billing at Northwind caught my eye. I work with agency ops leads on the same problem. Open to connecting?

  2. Prospect

    Sure. We're looking at tools now. How do you handle invoices in two currencies?

  3. Suggested reply

    We keep the invoice in the client's currency and report in yours. Want me to send a short video?

  4. Prospect

    A call is better. Thursday?

  5. You

    Thursday at 2pm works. I'll send an invite. If you want to include your finance lead, bring them.

Keep the pending invite pool clean

Pending invites pile up when a VA sends requests and never checks what happened. LinkedIn shows your acceptance rate, and a low rate makes future invites look worse. A VA who sends a batch of invites and gets a handful of accepts is creating a problem for next month, even if nothing happens this week.

Make cleanup part of the weekly routine. The VA withdraws invites that have been pending for a couple of weeks and have no reply. They also keep a simple sheet: name, date sent, accepted yes or no, reply yes or no. That sheet tells you whether the volume is working. If acceptance drops, cut the volume before LinkedIn cuts it for you.

If LinkedIn asks for a verification code or shows a warning, stop all sends for the day. Complete the check from your usual device. Do not let the VA retry the login.

Doing this with Kinlead

Kinlead connects your LinkedIn account through Unipile, so the VA never handles your password. You set daily invite and message limits and a send window in the lead's time zone, and each LinkedIn account sends at most one action every 5 minutes. Stale pending invitations are withdrawn automatically. If LinkedIn pushes back on the account, Kinlead pauses invites and emails you. The LinkedIn account safety page covers the settings. Pro costs $49 a month after a 7-day free trial, and you can cancel in Settings.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to manage LinkedIn limits with virtual assistants.md