If you are deciding whether to add a message to a LinkedIn connection request, my default answer for scaled outbound is no. Send the blank request, let the profile create the first impression, and use the accepted connection to begin a real conversation.
That conclusion did not come from a generic best-practices list. It came from running and reviewing roughly 40,000 connection requests across client campaigns. Highly personalized notes, manually written notes, and templated notes all added work before the prospect had granted permission to talk. Blank requests consistently removed that premature pitch.
The short answer: for scaled cold LinkedIn outreach, test a connection request without a note as the control. In my operating data, acceptance performance improved by roughly 19 to 21 percent relative to note-based requests. Keep warm introductions, event follow-ups, and genuine shared-context invitations separate because a note can still be useful there.
What 40,000 LinkedIn connection requests showed
The comparison covered outbound campaigns rather than one pristine A/B test. That distinction matters. Sender profiles, audiences, markets, offers, and timing changed. The result should be read as a durable operating observation, not a promise that every campaign will gain the same percentage.
Across comparable cohorts, blank connection requests produced roughly a 19 to 21 percent relative lift in acceptance performance over requests that carried a note. I use a normalized index in the graphic because the underlying campaigns did not share one raw baseline. If note-based requests equal 100, blank requests landed around 119 to 121.
The result also runs against LinkedIn's own general guidance. LinkedIn says a short, thoughtful note can explain who you are and help build trust. That makes sense for networking with known context. My data covers scaled cold outbound, where even a personalized note can feel like a small pitch before the recipient has chosen to engage.
Why a blank LinkedIn connection request can win
It asks for one decision
A blank request asks only, "Do I recognize enough relevance here to connect?" A note adds another question: "Why is this person already explaining or selling something to me?" Removing that second decision can reduce friction.
It avoids the personalization uncanny valley
Manual personalization is expensive. Automated personalization often notices a post, job title, or company event and then forces it into a line that sounds engineered. The recipient does not need to know which system wrote it. They only need to feel that the note exists to earn the pitch.
It lets the profile carry the proof
A blank request is not a substitute for trust. It transfers the trust job to the sender profile. Your headline should explain the buyer and problem you work on. Your featured section should show proof. Your recent posts should make your point of view easy to verify. The LinkedIn search and profile guide explains how to build that public proof layer.
It preserves the real message for after acceptance
The connection note is a cramped place to explain a commercial idea. Once the prospect accepts, LinkedIn Messaging gives you room for a useful sequence and supports documents, images, and video. That is a better moment to use context, proof, or a visual asset.
How the Aimfox multi-account setup works
Aimfox documents a useful split between a search account and worker accounts. In a multi-account Sales Navigator campaign, one connected account with an active Sales Navigator subscription can find the targets. Aimfox then distributes those targets among the selected worker accounts.
This does not transfer a Sales Navigator subscription to the other profiles. It centralizes the search and target distribution. Every worker account still needs an Aimfox Outreach seat. If the campaign includes a connection note, Aimfox says every sending account also needs LinkedIn Premium. A blank request removes that note-specific Premium dependency.
Builds the campaign target set. The search profile may also be a worker, but it does not have to send.
Targets are shared across the selected worker accounts so the campaign does not depend on one sender.
Each worker needs an Outreach seat. Notes create an additional Premium requirement on every sending profile.
Use a useful follow-up sequence, stop when the prospect replies, and reconcile state with the rest of outbound.
What to send after a blank request is accepted
Blank does not mean generic forever. It means delaying the message until the prospect has accepted the connection. The post-acceptance sequence should earn a reply in steps.
- Open with relevance. Name the problem, operating condition, or reason the person fits the conversation. Do not praise a random post just to prove a system found it.
- Add a useful observation. Give the prospect a diagnosis, contrast, or practical idea that stands on its own.
- Show proof. Use a concise client result, screenshot, diagram, or short case study when it directly supports the claim.
- Ask for the smallest next step. A question is usually easier than a calendar link. Move to a call only when the conversation earns it.
LinkedIn Messaging can carry links, documents, images, and video. Use that flexibility to make the conversation clearer, not noisier. A one-page audit or a screenshot with a two-sentence explanation can be stronger than a long block of text. Aimfox also documents that follow-up messages can continue after a no-note connection request is accepted and that its sequence stops when a prospect replies.
Coordinate LinkedIn with cold email
A blank connection request still becomes annoying if cold email sends the same pitch ten minutes later. The LinkedIn to cold email handoff guide shows how to keep one identity, one event timeline, channel suppression, and reply ownership through OutboundSync.
The rule is simple: an acceptance should change what email does next. A LinkedIn reply should stop competing automation. A negative response or unsubscribe should apply the broadest appropriate suppression. Your buyer sees one company, so the channels need one memory.
Measure the sequence, not only the acceptance rate
A higher acceptance rate is useful only if the accepted connections are qualified and the follow-up produces conversations. Track the full path:
- requests sent and accepted by sender profile
- acceptance rate by target cohort
- DM delivery and reply rate after acceptance
- positive conversations, meetings, pipeline, and revenue
- restrictions, failed sends, and account health
Across our broader LinkedIn inbound and outbound work, the operating systems have contributed to roughly $4 million in client pipeline and revenue outcomes. That is an internal estimate across multiple funnels, not a claim that blank requests alone created the result. The causal chain includes targeting, sender profiles, content, messaging, follow-up, sales execution, and offer quality.
Know the platform boundary
LinkedIn's User Agreement prohibits bots or other unauthorized automated methods for accessing the service, adding contacts, or sending messages. Any third-party LinkedIn workflow should be evaluated against the current agreement, account risk, and applicable law. Keep volumes conservative, monitor account health, and never treat tooling as permission to ignore platform rules.
Frequently asked questions
Should I send a LinkedIn connection request without a note?
For scaled cold outbound, it is the control I recommend testing first. Across roughly 40,000 requests in my operating data, blank requests produced about 19 to 21 percent better acceptance performance than requests with notes. For warm or genuinely shared-context invitations, a concise note may still help.
Do blank LinkedIn connection requests get accepted more often?
They did in my campaign records, but the result is not a universal benchmark. Profile quality, audience, relevance, geography, timing, and sender health all affect acceptance.
Can Aimfox run a Sales Navigator campaign across multiple accounts?
Yes. Aimfox documents multi-account Sales Navigator campaigns where one connected search account with an active Sales Navigator subscription finds targets and Aimfox distributes them among worker accounts.
Does every Aimfox worker account need Sales Navigator?
No. The documented requirement is at least one connected Sales Navigator search profile for that campaign type. Every worker needs an Aimfox Outreach seat. If the campaign uses connection notes, Aimfox says every sending account also needs LinkedIn Premium.
What should I send after a blank request is accepted?
Start with a relevant observation, add a useful idea or proof asset, and ask a low-friction question. Do not turn the first DM into a compressed cold email.
Can LinkedIn DMs include links, images, and documents?
Yes. LinkedIn's help documentation lists documents, images, and MP4 video among the supported message attachments. Use them when the asset makes the message easier to understand.