# How to clean up your pending LinkedIn invitations
> Unanswered connection requests pile up and can get your LinkedIn account flagged. How to find sent invites, decide what to withdraw and keep the pool clean.
- HTML: https://getkinlead.com/managing-pending-invites-pool
- Markdown: https://getkinlead.com/managing-pending-invites-pool.md

**Short answer:** LinkedIn treats acceptance as a signal about your outreach, and a large pile of unanswered requests makes an account look low quality. LinkedIn doesn't publish a number that triggers a flag, so the safe move is to withdraw requests that have sat for two or three weeks and fix the targeting that created them.

## Why a large pending pool gets an account flagged

LinkedIn treats acceptance as a signal about your outreach. When you send a request, the person on the other end either accepts it, ignores it or declines it. A decline at least tells the system the person saw the request and said no. An ignored request tells it nothing, and a large pile of them makes an account look like it's messaging strangers at random.

That's the pattern LinkedIn's defenses are built to catch, because it's also what a compromised or automated account produces. The system can't tell a hacked account spraying invites from a salesperson working a bad list. Both look the same from the outside: high volume out, low acceptance back.

The pool also grows without you noticing. You send twenty invites on a Monday, get six accepts by Friday, and feel fine. The other fourteen sit there. Do that for three months and you're carrying a hundred and fifty unanswered requests you never decided to keep.

What happens when the system reacts varies. You might lose the ability to send a note with your invite, you might be asked to type the person's email address before you can connect, or invites might stop going out altogether. None of these are permanent, but each one costs you days of outreach while you wait it out.

**Flagged account pattern**

- Sends requests to anyone who matches a job title
- Never opens the sent list
- Pending pool grows for months
- Notes read like a template

**Healthy account pattern**

- Sends requests to people who share a group, event or comment thread
- Clears the sent list every couple of weeks
- Pending pool stays small enough to scan in one sitting
- Notes mention the specific thing that prompted the request

## How to find your sent invitations

LinkedIn keeps two lists: invitations you've received and invitations you've sent. The sent list is the one nobody opens. It doesn't appear on your profile or in your notifications, and the default invitations view shows the incoming side.

The desktop path takes about four clicks. Mobile buries it deeper, so open a laptop if you have one. The list shows names, the date each request went out, and a withdraw link next to each one.

1. **Open my network.** Click the My Network icon in the top navigation bar of your LinkedIn homepage.
2. **Go to manage invitations.** Find the invitations panel and click Manage invitations. This opens the incoming list by default.
3. **Switch to the sent tab.** Click Sent. You'll see every request still waiting for a response, newest first.

## Deciding which requests to withdraw

Withdrawing too early is its own mistake. Plenty of people check LinkedIn once a week, and a request sent on Monday might get accepted the following Thursday. Pull it on day four and you've lost the connection for nothing.

Two weeks is a reasonable line for most B2B outreach. Past that point, the odds of an acceptance drop and the request just sits there taking up room. Go to three weeks if you sell to people in slow-moving roles like finance, procurement or anything with a long internal calendar.

There's a second category worth pulling sooner: requests sent to the wrong person. A generic company profile, someone who's clearly left the company, a recruiter when you wanted the hiring manager. Those will never convert, and they're the easiest names to clear.

One more thing to check while you're in there. If a name looks familiar but you can't remember why you invited them, that's a targeting problem, not a list problem. Note it and fix it in the next section.

| | Time since sent | What to do | Why |
| --- | --- | --- | --- |
| Under 7 days | Leave it | Normal checking window |
| 7 to 14 days | Leave it, watch the total | Still a plausible acceptance |
| 14 to 21 days | Withdraw | Odds drop sharply after this |
| Over 21 days | Withdraw first | Dead weight in the pool |
| Wrong person, any age | Withdraw now | Will never accept |

## The manual cleanup, step by step

There's no bulk withdraw button. You click names one at a time, which is why most people put this off until the account is already in trouble.

Work from the oldest end. The list runs newest first, so scroll to the bottom and clear upward until you reach the two-week line, then stop. If you have years of backlog, do the oldest hundred and come back next week.

Pace it. Withdrawing is gentler than sending, but a hundred withdrawals in five minutes still looks like a script. Twenty or thirty at a time with a break in between is plenty.

Keep a note of what you cleared. Not for LinkedIn, for you. If half the withdrawals are people from one list, that list is the thing to fix.

1. **Open the sent tab.** Manage invitations, then Sent. Confirm you're looking at outgoing requests, not incoming ones.
2. **Scroll to the oldest request.** Jump to the bottom of the list. Everything you need to clear is down there.
3. **Withdraw until you hit two weeks.** Click Withdraw next to each name, working upward. Stop when the dates reach the last fortnight.
4. **Log the pattern.** Write down which source or search most of those names came from. That's your next fix.

## Fixing the targeting that filled the pool

Cleaning the list fixes the symptom. If you keep sending the same requests, the pool refills within a month.

The usual cause is a list built from job titles alone. A title tells you someone's role. It doesn't tell you they have a reason to reply this week. Requests that carry a specific reason get accepted far more often than requests that carry a pitch, and the difference shows up in your pending count within a few weeks.

The second cause is the note. A note that opens with your product reads like an ad. A note that opens with whatever made you look the person up reads like a person. The note is short, so the reason has to come first and the ask has to be brief.

- **you:** Hi Priya, saw you're hiring a second SDR at Northwind. I run outbound for a few agencies and just went through the same hire. Would like to connect.
- **them:** Sure, happy to. How did the hire work out?
- **you:** Slower than I expected, but the second person freed up the first to focus on replies. Worth a short call if you're weighing the same trade-off.

```
Hi {{first_name}}, your comment on {{post_topic}} is the same problem I hear from {{role_type}} teams every week. I work on {{problem}} and would like to follow what you're building at {{company}}.
```

## Keeping the pool clean without thinking about it

Pick a fixed day and a fixed amount of time. Friday afternoon, ten minutes, clear anything past two weeks. That's the whole system, and it works better than a big cleanup every six months.

Watch two numbers: how many requests are pending, and what share of your recent requests were accepted. If the pending count climbs for three weeks running, your targeting slipped. If acceptance drops, your note or your list is off. Neither number needs to be perfect. You're looking for direction, not a grade.

Don't chase a perfect ratio. The goal is a pool small enough that you could read every name and remember why you sent each one. If you can do that, the pool is healthy regardless of what the number says.

> A pending pool you can't explain is the warning sign. If you can't remember why you invited someone, withdraw the request.

## Doing this with Kinlead

Kinlead withdraws stale pending invitations automatically, so the pool doesn't grow while you're busy with other work. Settings shows your pending invitations and acceptance rate, with a warning when either looks off.

When LinkedIn pushes back on an account, Kinlead pauses invites on that account and emails you, rather than letting the campaign keep firing into a wall. Sending stays inside the daily invite and message limits you set, inside a send window in the lead's time zone, at one action every five minutes per account. That pacing is what stops the pool filling overnight.

Plans and what each one includes are on [the pricing page](/pricing).

## Related

- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)
- [Pricing and plans](https://getkinlead.com/pricing.md)

## Common questions

**Does withdrawing a connection request notify the person?**

No. The request disappears from their invitations list and they aren't told. If they never opened it, they'll never know it existed.

**Can I send the request again after withdrawing?**

You can, but sending the same note again usually lands in the same ignored state. Wait a few weeks and come back with a different reason, or reply to a post they wrote instead.

**How many pending invitations are too many?**

LinkedIn doesn't publish a number. A workable test is whether you can read every name in your sent list and remember why you invited them. Once the list is too long to scan, it's too long.

**Does withdrawing requests hurt my acceptance rate?**

Withdrawing isn't a decline. It removes an unanswered request from the pool, which is the point. It doesn't touch the requests people already accepted.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
