Use a connection request to give the recipient a reason to recognize you before the next message arrives. Accepted blank requests can still produce silence when the first message arrives.1 Make the follow-up easy to answer.
Choose the request type
Decide what the recipient can recognize about you. The request should fit the relationship you already have and the reason you are reaching out.
If you meet someone, add them to your network after the interaction.2 Send each identified person a connection note that refers to where you met.3 When more people join a meeting, give those additional attendees context for the connection.4 If you see a close connection to a prospect, send that person a message immediately.5
For broad prospecting, use the default blank request when you have no useful context to add.6 When you have a real reason to connect, write a short contextual note. A note helps you stand out immediately.7 Keep it specific enough for the recipient to place you, and leave generic wording out.
Write the note
Keep the note short enough to understand in one pass. It should create recognition and permission for the next exchange.
Use a short three-part message:8 shared context, a reason to connect, and an easy permission question. One sample establishes shared roles, mentions mutual connections, and asks whether the recipient is open to networking.9
Write like a human and avoid overly formal language in direct messages.10 A one-sentence direct message is a workable target; the cited example used one sentence.11 For InMail, stay under 150 words.12
End with an easy response. A kind connection message without an ask receives responses more often than expected.13 That leaves room to open a conversation without forcing a meeting request into the connection itself.
Move from connection to message
The connection request opens access to a later exchange. Keep the next message focused on why you connected and give the recipient a simple way to respond.
Sending messages is easier when you are already connected than when the outreach is completely cold.14 After acceptance, use the context from the note as the first line of the direct message, then ask one question that can be answered without research.
If the connection request does not work, send an InMail later in the campaign to seek an open or a response.15 A LinkedIn touch can prompt a prospect to reply by email.16 Track the response in whichever channel they choose and continue there.
Set a safe volume
Volume depends on account condition and invitation quality. Set a pace you can sustain while watching acceptance and pending requests.
LinkedIn's help pages describe restriction triggers, not a weekly connection-request number.17 For most established accounts, the working limit is reported at around 100 connection requests per week.18 Warmed accounts with strong acceptance rates and high Social Selling Index scores are widely reported to reach 150 to 200 per week, while new or low-acceptance accounts can be held to 20 to 30.
Older outreach playbooks quote higher limits because they were written before a change to the platform's limits.19 Historical guidance reports that LinkedIn previously allowed roughly 700 invitations per week and reduced that around 2021.20 Use the account's current response pattern to set your pace, and treat old volume promises as dated guidance.
Start below the reported range for your account type, then increase only when pending and ignored requests stay under control.
What not to do
- Do not send a generic connection note, because generic notes are declined.21
- Do not get clever in a mass connection request.22
- Do not send many invitations in a short period or let ignored, pending, or spam-marked invitations accumulate.23
- Do not copy advice promising hundreds of requests per day without checking its date.24