Skip to main content

LinkedIn Message Requests: Why Cold DMs Get Buried

A cold message to someone you aren't connected to usually doesn't reach their inbox. LinkedIn message requests catch it first: a separate folder the recipient has to open, read and accept before the conversation becomes a normal thread. So your best opener can sit unread for weeks, while a two-line note from a first-degree connection gets answered the same afternoon.

That one routing decision explains why "message group members for free" tactics underperform. It is also why serious outreach runs connection-first.

How LinkedIn message requests work

LinkedIn lets you message some people without a connection. Fellow members of a shared group and attendees of the same event are the common cases. The platform treats these messages as unsolicited. It moves them out of the main conversation list and into a Message requests area.

From the recipient's side, three things matter:

  • The message isn't in the main list. On mobile the requests entry is a small link at the top of messaging. Most people never tap it.
  • They have to act. They can accept it, which turns it into a regular thread, or decline it.
  • You can't follow up. Until they accept, the thread is frozen on your first message.

Your opener has to do everything on its own, in a folder most buyers skip, with no second attempt.

Where each type of message actually lands

People often mix up the outreach routes, so here is what happens to each one:

What you send Where it lands Can you follow up before they reply?
Message to a 1st-degree connection Main inbox Yes, as many steps as your sequence needs
Note attached to a connection request Invitations (My Network), not the inbox No, it's a one-shot note
Message via a shared group or event Message requests folder No, not until they accept
InMail (paid credit or Open Profile) Main inbox, labelled as InMail Only by sending another InMail

Only one row gives you an inbox spot and room for a multi-step sequence: being connected.

Why this quietly breaks automated cold sequences

Picture a four-step drip campaign: opener, value follow-up, case for a call, polite breakup. Aim it at scraped group members and it shrinks to one step. The first message goes to requests. Steps two to four have nowhere to go. Your analytics report "sent", but the prospect may never see anything.

There is a second cost. Many messages to strangers that never get accepted or answered is exactly the pattern spam filters are built to catch. Each one spends account risk and brings back almost no conversations. That is a bad trade for a LinkedIn account you depend on.

Our view is blunt. Group and event messaging is fine for a handful of hand-written notes to people you genuinely share context with. It doesn't work as an automated channel.

Connection-first: the default we'd build around

A connection-first sequence fixes the routing. You send an invitation, with or without a short note. Then you wait. Once someone accepts, every message after that lands in their main inbox and your follow-ups can run.

The logic in a workflow looks like this:

  1. Visit the profile, then send the connection request.
  2. Wait a few days.
  3. If accepted: send the opener, then delayed follow-ups, and stop the moment they reply.
  4. If not accepted: wait a bit longer, then withdraw the pending request so stale invites don't pile up.

The constraint is invitation volume. Ampliflow caps connection requests at 25 per day per account on every paid plan. Over a five-day week that is about 125 invites, so your acceptance rate sets how many inbox-eligible conversations you get. Tighter targeting beats more volume here. A note that names a real shared context helps more than a clever hook.

Message caps then control your follow-ups to accepted connections: 25 a day on Standard, 50 on Pro, 80 on Team. If you have a large accepted network to work through, that difference matters more than the invite cap.

When InMail earns its cost

InMail skips both the invitation queue and the requests folder. It lands in the main inbox. That makes it the right tool for a narrow set of prospects: senior buyers who rarely accept invitations from strangers, and Open Profile members you can message directly.

The trade-off is cost and scarcity. InMail credits come with paid LinkedIn tiers, and each one you spend on a weak-fit prospect is gone. Our recommendation: keep InMail for a short list of high-value accounts you'd pursue by hand anyway, and run everything else connection-first. Don't make InMail your main cold channel unless your deal sizes justify the credit spend.

Building it in Ampliflow

Ampliflow's visual drag-and-drop builder handles the branching above directly. You set an If/Else on whether the invite was accepted, add delays between steps, and let auto-pause stop a sequence the moment someone replies. Replies from every connected account land in one unified inbox, so you can answer a prospect without hunting through threads.

Campaigns run in the cloud through the Unipile API. You connect your LinkedIn account once with the Chrome extension, then you can close your laptop (here's why that matters). Actions follow human-like daily limits with randomised timing jitter, only during your working hours. Real-time account safety scoring with anomaly detection flags unusual patterns before they become a restriction. A/B testing lets you compare connection notes and openers, and funnel analytics show where accepted connections drop off.

On price, cheaper options exist. Octopus CRM starts at $9.99/mo, Dux-Soup at $14.99/mo and Linked Helper at $15/mo. If all you need is a basic invite sender and you don't mind how it runs, those are reasonable picks. Ampliflow's case is architecture and safety, not the lowest sticker. Standard is $19/mo for founding members (regular $39/mo), Pro is $39/mo (regular $59/mo), and Team is $99/mo. Founding prices are locked for life for the first 100 paying customers. Every plan has a 7-day free trial. Full details are on the pricing page.

Frequently asked questions

Messages from people you share a group or event with, but aren't connected to, land in a separate Message requests folder rather than the main inbox. The recipient has to open that folder and accept before the thread becomes a normal conversation.
No. Until the recipient accepts, you can't keep adding messages to that thread. A multi-step cold sequence sent this way usually stops after the first message.
InMail lands in the recipient's main inbox, which helps with senior buyers who ignore invitations. It costs paid credits, though, so it suits a short list of priority accounts. Connection-first sequences are the better default for volume.
Ampliflow caps connection requests at 25 per day per LinkedIn account on every paid plan. Message limits are 25 on Standard, 50 on Pro and 80 on Team, with randomised timing inside your configured working hours.