# How to message prospects who ignore your connection request
> Stop the request loop and use public engagement or channel switching to build trust with LinkedIn prospects who haven't accepted your invite.
- HTML: https://getkinlead.com/how-to-message-prospects-who-ignore-connection-requests
- Markdown: https://getkinlead.com/how-to-message-prospects-who-ignore-connection-requests.md

**Short answer:** Stop sending requests if a prospect ignores you. Instead, engage with their public posts or switch to another channel to build familiarity before you try to connect again.

## Stop the request loop

The biggest mistake is trying to force the connection. Sending a second request from a different profile or a reminder through another tool looks like spam. It tells the prospect you care more about your quota than their time.

If a request stays pending, it's a signal. They might not check LinkedIn often, they might have a rule against connecting with strangers, or your profile doesn't look relevant. Pushing harder just increases the chance they mark you as spam, which puts your account at risk.

A pending request also takes up space in your pending pool. LinkedIn does not publish exact limits on pending invitations, but a high number of unaccepted requests can hurt account health. Withdraw stale invites and keep the pool small enough that new requests can go out. If you use a tool that sends requests for you, check how it handles pending invites before you blame the prospect.

**Pushy approach**

- Sending a second request from a personal account after the work account was ignored.
- Messaging the prospect on every social platform within 24 hours.
- Sending a 'Did you see my request?' message via a third party tool.

**Patient approach**

- Leaving the pending request alone for 14 to 30 days.
- Withdrawing the request after a month to keep your pending pool clean.
- Moving to public engagement to build a bridge before trying again.

> LinkedIn does not publish exact limits on pending invitations. Watch your pending count and acceptance rate in your own account, and withdraw requests that have sat for weeks.

## Check whether the request was actually ignored

Before you change tactics, look at the request itself. A request sent on Friday afternoon can sit unread until Tuesday. A request sent to someone who logs in once a month can look ignored when it is just unseen. Give it at least a week before you treat it as a no.

Check your sent invitations and the profile. If they have posted or commented since you sent the request, they have been on LinkedIn. That is a stronger signal that they saw it and chose not to accept. If they have not been active, wait.

Also check your own profile as a stranger would see it. A blank banner, a vague headline and no recent activity make a request easy to skip. You do not need a perfect profile, but the first screen should say what you do and who you help.

If you sent a note with the request, read it again. A note that talks about your product before it talks about them is easy to ignore. A note that mentions a post, a shared group or a specific problem gives the person a reason to accept.

## The public first strategy

If the direct door is closed, use the public square. Most people who ignore requests still check notifications to see who is commenting on their posts. This is a low friction way to get your name and face in front of them without asking for anything.

Avoid generic praise like 'great post'. That's invisible. Provide a specific insight or ask a question that makes them want to answer. When they reply to your comment, they've opted into a conversation.

Pick one or two posts, not every post. A comment on a recent post about a problem you solve is better than a comment on a company anniversary. The goal is recognition, not a debate.

Do not pitch in the comments. If you solve the problem they wrote about, ask a question that lets them describe the problem in their own words. That gives you material for the next message.

1. **Audit their activity.** Go to their profile and click 'Activity'. Look for posts they wrote or comments they left on other threads in the last 30 days.
2. **Add a specific insight.** Leave a comment that references a specific point they made. Use a phrase like 'I agree with your point on X, but I wonder if Y affects the outcome.'
3. **Wait for the reply.** Do not send another request immediately. Wait for them to respond to your comment or like it.
4. **Reference the public chat.** Once they engage, send a message or a new request mentioning the specific thread where you both spoke.
5. **Keep a record.** Note the post URL and the date you commented. You will need that context if you try a request again later.

## Switching channels

LinkedIn is often the most crowded inbox. If you've tried the public strategy and still have no traction, move to a different channel. Reference your LinkedIn attempt without sounding like you're stalking them. You're just finding the best way to communicate.

This works best when you have a reason for the move. Instead of saying 'I tried to connect on LinkedIn', say 'I saw your thoughts on X on LinkedIn and wanted to send over a resource that expands on that.' Keep the same story across channels. If your LinkedIn note mentioned a post about hiring, your email should mention the same post.

Keep the first message short. You are not trying to close a deal in one email. You are trying to get a reply that tells you whether this person is worth more time.

If you cannot find an email address, use the company contact form or a public social profile. Do not guess addresses. A bounced email or a message to the wrong person wastes the opening.

| | Channel | Action | Goal |
| --- | --- | --- | --- |
| Email | Send a short, plain-text note | Reference a specific post they wrote on LinkedIn |
| Twitter/X | Reply to a thread | Move the conversation to a DM |
| Company website | Find a contact form | Ask for the right person to speak with regarding a specific problem |

## The low friction follow up

If you try one last time on LinkedIn, change your objective. Stop trying to force a connection and aim to be useful or curious. A low friction request is one where the prospect doesn't feel they're signing up for a sales pitch.

Use a soft close. Give them an easy way to say no or ignore you without feeling guilty. This makes them more likely to respond because you've removed the pressure.

Keep the note short. Open with why you are writing to them, not with your product. If you have a real reason, such as a post they wrote or a mutual contact, use it. If you do not, wait until you have one.

A follow up after a comment is different from a follow up after a request. Mention the thread you both spoke in, then ask one question. Do not send a calendar link in the first message.

- **you:** I saw your post about scaling remote teams. I have a question about how you handled the time zone overlap for your engineers.
- **them:** We actually just moved to a 4-hour overlap window. It was a pain to set up but it works.
- **you:** That makes sense. No need to connect if you're busy, but I'm curious if managing the documentation for those windows is still a struggle for your team?

```
I'll leave it here. If you ever need help with [Service], feel free to reach out.

Best,
[Your Name]
```

## When to withdraw and try again

Withdraw a request when it has sat for 14 to 30 days and the person has been active. Withdrawing frees the pending slot and removes the awkwardness of a request that will never be accepted. You can send a new request later with a different note.

Do not withdraw and resend the same day. That looks like a glitch. Wait a few weeks, engage with a post, and then send a request that mentions the post. If you have no new reason, leave them alone.

A withdrawn request is not a failure. It is a clean end to one attempt. The prospect may accept a request later when they have a problem you can solve. Leaving a stale request in place does not keep that door open.

Track what happens after you withdraw. If you have a CRM or a spreadsheet, note the date of the first request, the post you commented on and the date of the second request. If the same person ignores a second request after public engagement, stop. Some prospects are not ready, not interested, or not the right contact. Move to another person at the company.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept. That means you spend your requests on people who look like the buyers you already want.

The [Steal Customers](/features/steal-customers) agent watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, so your first message can reference a real conversation.

Kinlead withdraws stale pending invitations automatically and shows pending invitations and acceptance rate with warnings in Settings. You can set a send window in the lead's time zone so requests land during business hours.

## Related

- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)
- [Find leads](https://getkinlead.com/tools/find-leads.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**How long should I wait before withdrawing a pending request?**

Wait between 14 and 30 days. This gives the prospect enough time to see the request without you cluttering your pending list.

**Does ignoring a request mean they aren't interested in my product?**

Not necessarily. Some people ignore LinkedIn requests by default or simply don't check the platform daily. It often says more about their habits than your offer.

**Can I message someone without connecting first?**

Sometimes. LinkedIn lets you send a message without connecting in some cases, such as when you share a group or the person has open messaging. Those messages can land in a separate request folder and be missed.

**What should I say when I try again?**

Mention the post you commented on and ask one question. Do not repeat the first note or send a calendar link in the new request.

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