The daily limit is only half of a safe pace
A LinkedIn account gets restricted for two broad reasons: it sends too much, or it sends what people do not want. HeyReach deals with the first: you set a daily limit on the sender, and the tool spreads the requests out.
The second half is not a setting. Requests to the wrong people, with a note that reads like a mailshot, collect ignored and declined invitations, and that pattern is what gets an account looked at. No limit fixes it. The list and the note do.
So this play works on the half the tool cannot. It takes out people who should never get a request: rows with no profile, people already connected to the sender, people already in your HeyReach inbox. It writes a note about the reader. And it loads in batches, so you see how the first group received it before the rest is queued.
One thing to know first: a HeyReach campaign cannot be created from outside HeyReach. You build it there, with its steps, sender and limits. The agent drafts the words and loads it.
What you get back
Your list split three ways: cleared to load, set aside for a missing profile URL, and removed, each removed row with its reason. The connection note and the follow-up messages as text, ready to paste into the campaign. A batch plan: people per load, and the working days each load takes at your limit. The first batch loaded into your paused campaign and read back.
Variations worth knowing
Candidates or client contacts. Both work. For candidates LinkedIn is the first channel and a personal email the second, never a work address. For client contacts the note points at their hiring, not at your agency.
Rows with no profile URL. They are not guessed. Add the LinkedIn profile URL to a list fills them, and they join a later batch.
No HeyReach. lemlist can have its LinkedIn steps, a profile visit, a request and a message, built through its connection in a paused campaign.
When the replies come. Sort campaign replies reads the HeyReach inbox and ranks them for you.
Where this goes wrong
The number in your prompt is not the number in HeyReach. The agent cannot read or change the sender's limit. It sizes batches from what you tell it. If the two differ, HeyReach wins.
Loading into a running campaign. Adding people to a live campaign starts outreach to them. The agent reads the status first and asks.
No sender id. The connection cannot list your sender accounts, so the already-connected check needs the sender's id from HeyReach. Without it that check is skipped, and the agent says so.
A note with a pitch in it. A request that sells gets ignored, and ignored requests are the risk. If the first batch was mostly ignored, fix the note or the list before you load more.
