Can LinkedIn outreach tools message Group members without connecting?

LinkedIn's Group membership help says a member can send a message request to another member without connecting if the Group's settings allow direct communication. Its route is the Group member list, then Message beside one person's name. If the button is missing for the sender and recipient you intend to use, a vendor's campaign screen is not evidence that the Group request path is available.

The request arrives in a separate inbox where the recipient can accept or privately decline it. LinkedIn's Group Management help also says a Group admin cannot send one direct message to every member at once. The native action is an individual request, not a blanket right to broadcast to the membership list. A connected member can instead receive a normal message; an InMail is another path with different eligibility.

Sources: LinkedIn Groups membership FAQ, LinkedIn message request states, LinkedIn Group Management messaging

Expandi documents a Group campaign for messaging members without a connection request, but its help page limits the lead input to a Group URL or a Sales Navigator or Recruiter URL filtered to that Group. It warns against putting a CSV or an Event attendee list into this campaign. Expandi also says the sender must have belonged to the Group for at least four days. Those are Expandi's documented workflow conditions; they are not a universal LinkedIn waiting period.

Aimfox documents a different choice at campaign setup: connection request, Group message request, or InMail. Linked Helper describes collecting members from a Group and running a Group message sequence. The labels matter because a connection request followed by a message, a Group request, and an InMail can each look like ‘Group outreach’ in a product tour while reaching different people and creating different inbox states.

Before buying, ask the vendor to show the exact sender account, Group, imported list type, and first action. A sample campaign built from a convenient CSV does not prove the Group request will work with your prospect list. Nor does a successful Group member import prove that every imported person has a sendable request path.

Sources: Expandi Group Campaign help, Aimfox Group Members help, Linked Helper Group message sequence

LinkedIn moves an accepted message request into the main inbox. That tells the sender the recipient opened a conversation; it does not say the recipient wrote back. Linked Helper's Group sequence guide identifies a concrete failure mode: its reply detector can read LinkedIn's ‘message request accepted’ notice as a reply, even when the person has not answered. Its default follow-up behavior also waits for acceptance of the initial request.

A useful trial therefore needs four separate states: request attempted, visible in the recipient's request inbox, accepted, and answered in the recipient's own words. Check the tool's event log against the native sent record and the recipient's inbox, using a colleague who agrees to the test. Then accept the request without answering and see whether the campaign incorrectly marks a reply or stops a follow-up. Only after that should the colleague send an actual answer and verify the stop rule again.

Sources: LinkedIn message request states, Linked Helper Group message sequence

LinkedIn says it does not permit third-party software that scrapes, modifies, or automates activity on its site. A vendor's Group campaign documentation describes a product capability, not LinkedIn approval or an account-risk guarantee. If that exposure is unacceptable, use the native Message action for a small, relevant set of fellow members and record the conversation manually.

If the team still evaluates software, keep the test to a consented recipient and document the account role, Group setting, list source, first action, actual inbox result, and response state. A failed request should remain failed in the record rather than being retried through another action without a new decision. The tool is worth considering only if it preserves those distinctions and the team accepts the platform-policy tradeoff.

Sources: LinkedIn prohibited software guidance, LinkedIn Groups membership FAQ