What to do when one team LinkedIn account is restricted

How a B2B sales team handles a restricted LinkedIn account: stop the sends, sort the leads, and move the pipeline to healthy accounts without a second ban.

Get started

Short answer

Stop every send on the restricted account the same day, including queued campaign messages, because the queue is what turns a warning into a ban. Then sort the leads that account was working, move the replied and interested ones to a healthy teammate's account first, and spread the rest across accounts at their normal daily volume.

Stop all activity on the restricted account

A restriction notice means the account goes quiet the same day. Every invite, message and profile view sent after that point gives LinkedIn another reason to make the restriction permanent, and the queue is where most of the damage happens.

The account owner should stop working from that profile entirely, including manual browsing. Reading a profile looks harmless. It still registers as activity on an account that is already flagged.

Don't delete the profile or spin up a replacement under the same name. A fresh account carrying the same list looks like an attempt to get around the restriction, and it tends to end the same way.

  1. 1

    Disconnect the outreach tools

    Log out of every tool that sends on the account's behalf and revoke its access. Check for scheduled jobs that hold a session in the background, because those keep sending after the browser is closed.

  2. 2

    Pause the campaigns pointed at that profile

    Queued messages go out on a timer whether or not anyone is watching. Pausing the campaign is the single step that stops a warning from becoming a ban.

  3. 3

    Tell the owner to stop manual outreach

    No browsing, no accepting invitations, no replies. If they need to check something on LinkedIn, they ask a teammate to look instead.

  4. 4

    Save the notice

    Screenshot the wording and note the date. You need it for the appeal, and it tells you which kind of restriction you're dealing with.

Work out which restriction you're dealing with

Two of these are housekeeping and two are serious. A greyed-out invite button is a signal to slow down for a few days. A full lock means the account is out of action for as long as the review takes, and you should plan the team's week as if it won't come back.

A warning asking you to slow down

What you see
Automated checks flagged volume or timing
What it usually means
Stop sending for the day, lower the daily limits, and check the send window against the prospect's time zone

A request to verify identity

What you see
LinkedIn wants to confirm a real person owns the account
What it usually means
The owner completes it with their own ID and phone, from their usual device

The invite button is greyed out

What you see
Too many invitations are sitting unanswered
What it usually means
Withdraw stale invites, wait for the pool to clear, and don't queue more

A full lock with no sign-in

What you see
The account is suspended pending review
What it usually means
Appeal once from the owner's usual device and keep the rest of the team sending from their own accounts

Sort the leads that account was working

Export the account's leads before you change anything. If the profile gets locked, the tool's view of it may go with it, and a CSV is the copy you can reload on another account.

Then split the list by where each person sits, because the four groups need different handling and different timing.

Priority comes from two things: how recently the person replied, and how much the deal is worth. A reply from this morning on a mid-sized account beats a reply from last week on a small one. Sort by that, not by the order the leads happen to sit in the tool.

  • Replied and interested. These have a clock on them. Move them first, today.
  • Replied and not interested. Leave them alone. A second pitch from a different name reads as pressure.
  • Mid-sequence with no reply. Move them to a healthy account and continue from the next step, not from the beginning.
  • Never contacted, still sitting in a lead group. The easiest to move and the least urgent. Park them until the rest of the list is stable.

A prospect who answered on Monday and hears nothing until Friday has usually moved on. That's the only real deadline in this process.

Move the leads without tipping the next account over

The obvious move, dumping the whole list onto one healthy account, is how teams end up with two restricted accounts in the same week. LinkedIn looks at behaviour per account, and a sudden jump on a profile that was quiet last week stands out.

Spread the leads across the accounts that have room, weighted by what each one already sends. An account running a few invites a day shouldn't suddenly send many times that.

Move the replied leads first, one at a time, by hand. Then the mid-sequence leads, in batches sized to what each account can absorb. The untouched leads can wait until next week, and often they should.

What gets the next account restricted

  • Moving every lead onto one teammate's profile and clearing the backlog in an afternoon
  • Reusing the exact opening line that was running when the first account got flagged
  • Adding the moved leads on top of the volume that account was already sending

What keeps it steady

  • Splitting the lead groups across three or four accounts, weighted by current volume
  • Rewriting the opening line so the new sends don't repeat the old copy word for word
  • Holding each account at its usual daily volume and letting the backlog clear over a week or two

The backlog is not urgent. A prospect who waits four extra days is a smaller problem than a second restricted account.

Answer the replies that are already in flight

Someone has to pick up the conversations the restricted account started. The owner can't, so a teammate or the manager answers from their own profile and says who they are in the first line.

Keep the handover to one sentence. The prospect doesn't need the details, and a long explanation reads as an excuse for something they never asked about.

Decide who owns the thread once the handover is done. If the original owner is coming back, they take it back when the account clears. If they aren't, the teammate keeps it and the original owner stays out of that conversation.

Example

  1. Prospect

    This looks relevant. What would a pilot involve?

  2. Suggested reply

    Hi Sarah, I'm picking this up from Marcus while his account is being sorted. Same team, same questions. A pilot runs four weeks on your own data. Would Thursday morning work for a short call?

  3. Prospect

    Thursday works. Send an invite.

Write the handover down where the team can see it. If the original owner comes back next week and replies to the same thread, the prospect gets two answers from two people and trusts neither.

Fix the cause before the team sends again

Write the answer down before the account restarts. A short note per incident stops the same mistake from repeating across the team.

When the account comes back, restart below the volume it was running before and watch the first week. LinkedIn doesn't publish how long a restriction lasts, so the notice clearing is your only signal that it's over.

  • Volume. Did the daily count climb sharply, or did a backlog go out at once?
  • Copy. If every message opens with the same sentence, the pattern is easy to spot from the outside.
  • Timing. Messages landing at 2am in the prospect's time zone look automated, because they are.
  • Pending invites. A pool full of invitations nobody answered is a signal on its own.
  • Access. A new device or network in the same week as a volume spike is a bad combination.

Paste this job

Account: [name]
Notice wording: [paste it]
Last 7 days: invites __ , messages __ , replies __
Opening line used: [paste it]
Pending invites at notice: __
One change before restart: [specific]
Restart date: __

Doing this with Kinlead

Kinlead keeps leads in lead groups rather than tying them to one person, so a restricted account doesn't take its list with it. You point a campaign on a healthy account at the same group and the leads carry on from where they were.

When LinkedIn pushes back on an account, Kinlead pauses invites on that account and emails the user. That stops the queued sends that turn a warning into a ban, without anyone having to remember to check.

Replies from every campaign land in one inbox, classified by intent with interested ones first, so the conversations that were mid-flight are easy to find and hand to a teammate. Settings also shows pending invitations and acceptance rate, which is where you look first when an account starts behaving oddly. The unified inbox page covers how the handover works.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? What to do when one team LinkedIn account is restricted.md