Sequencing on LinkedIn with HeyReach

LinkedIn outreach works at scale only if you respect the platform’s constraints. Most operators who get their accounts restricted made the same mistake: they treated LinkedIn like email and ramped sending volume too fast. HeyReach is built around this reality — it’s the LinkedIn automation tool that makes throttling and multi-account rotation a first-class feature rather than an afterthought.

This playbook covers the full HeyReach setup: account warming, audience building from Sales Navigator, a three-touch sequence template, safe daily limits, and routing accepted connections to HubSpot for follow-up. It also covers what happens when LinkedIn restricts an account — because it will happen eventually, and the response matters.

Setup: Prerequisites

  • HeyReach account: Agency plan ($79/month per LinkedIn account, or $199/month for up to 5 accounts). The multi-account features that make safe scaling possible require at least the 3-account tier.
  • LinkedIn accounts: Minimum 2 accounts, ideally 3–5. These should be real LinkedIn profiles associated with real people at your company — not fake personas. LinkedIn’s detection systems are sophisticated and flag profiles that lack employment history, connections, and activity. Each account needs Sales Navigator ($99/month) for the audience building step.
  • HubSpot or Salesforce: HeyReach has a native HubSpot integration and a Salesforce integration via webhook. This playbook uses HubSpot.
  • Chrome extension: HeyReach requires its Chrome extension installed on the browsers where your LinkedIn sessions are active. Each LinkedIn account must be logged in on a separate Chrome profile.

Step 1: Account Warming

New HeyReach accounts (or LinkedIn accounts recently connected to HeyReach) must warm before running sequences. Warming in HeyReach means gradually increasing daily activity limits over 2–3 weeks while the accounts demonstrate normal LinkedIn behavior.

In HeyReach, go to Settings → Account Limits for each connected account. Set this ramp schedule:

  • Week 1: Connection requests: 10/day. Messages to connections: 20/day. Profile views: 30/day.
  • Week 2: Connection requests: 15/day. Messages: 30/day. Profile views: 50/day.
  • Week 3 and beyond: Connection requests: 20–25/day. Messages: 40/day. Profile views: 80/day.

The 20–25 connection request ceiling is not a HeyReach setting — it is the effective LinkedIn TOS safety limit. LinkedIn’s stated limit is 100 invitations per week (approximately 14/day), but in practice, accounts sending 20–25 per day with good acceptance rates rarely get restricted. Accounts sending 30+ per day with low acceptance rates get flagged quickly. The acceptance rate matters as much as the volume: if you are sending 25 connection requests and only 5% are accepted (normal for cold outreach to cold audiences), your account looks suspicious. If 30–40% are accepted, you can sustain higher volume safely.

During the warming period: Each LinkedIn account should also be doing genuine activity — commenting on posts, endorsing connections, and updating their profile. HeyReach cannot simulate this; the humans behind the accounts need to do it manually. 10 minutes of authentic LinkedIn activity per account per week is enough to maintain a natural activity pattern alongside HeyReach’s automated actions.

Step 2: Audience Building from Sales Navigator

In Sales Navigator, build a Lead search that matches your ICP. Filters that produce the highest connection acceptance rates:

  • Title keywords: Be specific. “VP of Sales” outperforms “Sales” as a title filter because you get fewer managers and more decision-makers. Combine multiple title variations with OR logic.
  • Company headcount: Set your target range. Matching this to your ICP avoids the common mistake of reaching enterprise contacts with an SMB pitch.
  • Geography: US-specific sequences typically outperform globally mixed lists. Create separate campaigns per region if you have multilingual outreach capacity.
  • Seniority: Director level and above accepts connection requests at 30–45%. Manager level: 20–30%. Individual contributor: 15–25%. Acceptance rate directly affects your account’s restriction risk, so targeting senior personas is both better targeting and safer automation.
  • Recent activity (“Posted on LinkedIn in the past 30 days”): This filter, available in Sales Navigator, dramatically improves reply rates. Accounts that have posted recently are actively monitoring LinkedIn and are more likely to see and respond to your sequence. This single filter can improve message reply rates by 40–80%.

Export the Sales Navigator search into HeyReach directly using HeyReach’s Sales Navigator integration. HeyReach will import the LinkedIn profile URLs and basic firmographic data. Target list size per campaign: 500–2,000 contacts. Split large lists across multiple campaigns to distribute activity across your account pool.

Step 3: Three-Touch Sequence Template

HeyReach sequences support connection requests, messages, InMails, and profile view triggers. This three-touch sequence runs over 7 days and is designed for a connection acceptance rate of 25–35%:

// HeyReach Sequence Configuration

Step 1: Connection Request (Day 0)
  Type: Connection Request with Note
  Note (300 character limit):
  "Hi {{first_name}} — your work at {{company}} on [specific topic relevant to ICP] caught my attention.
  I lead [your role] at [your company] and think there's overlap worth a quick conversation.
  Would love to connect."

  Character count: ~250-280 (leave buffer for variable substitution)
  A/B test: Run 50% with a note, 50% without.
  (Notes modestly improve acceptance for senior personas; blanket notes can hurt
  acceptance for junior personas who get high volumes of spammy connection requests.)

Step 2: Message 1 (Day 3, trigger: connection accepted)
  Type: Direct Message
  Message:
  "Thanks for connecting, {{first_name}}.

  One question: [single specific question about the problem you solve that they would
  have a genuine opinion on]. Seeing a lot of discussion on this in [their industry]
  and curious what your team's experience has been.

  Happy to share what we're seeing across [X] similar companies if useful."

  Tone: peer-to-peer, not vendor-to-buyer. No pitch. No demo ask.
  Length: 60-90 words.

Step 3: Message 2 (Day 7, trigger: no reply to message 1)
  Type: Direct Message
  Message:
  "Following up briefly, {{first_name}} — no worries if not relevant right now.

  If [specific pain point] is something you're actively working on, I have [specific
  resource — data point, framework, or case study] that might be worth 5 minutes.
  Happy to send it over.

  If not, no worries — I'll leave you alone."

  Length: 50-70 words.
  This is the final touch. Do not add a fourth message — it reads as desperation and
  damages your account's reputation with LinkedIn's engagement signals.

Personalization at scale. HeyReach supports custom variables beyond {{first_name}} and {{company}}. In your lead import from Sales Navigator, add a custom column for a manually-researched or AI-generated personalization token — a specific observation about each person’s recent post, a company announcement, or a role change. Even 10–15 words of genuine personalization in the connection note can lift acceptance rates from 25% to 40% for senior personas. Use Clay’s Claygent to auto-generate these personalization tokens before importing the list into HeyReach.

Step 4: Reply Routing to HubSpot

In HeyReach, go to Integrations → HubSpot. Authorize via OAuth. Configure these sync rules:

  • On connection accepted: Create or update HubSpot contact. Set property linkedin_connected: true and linkedin_connection_date: [timestamp]. Do not create a deal at this stage — connection is an early signal, not buying intent.
  • On message reply received: Create a HubSpot activity (“LinkedIn reply received”) on the contact record. Tag the reply text. Set contact stage to MQL if not already. Create a deal in the Inbound pipeline if one does not exist. Assign to the HeyReach account owner’s HubSpot user.
  • On positive intent keywords detected: HeyReach’s reply categorization can detect intent keywords (“interested,” “let’s talk,” “send me,” “book a call”). Configure HeyReach to send a Slack notification to #linkedin-replies when a reply contains positive intent keywords. These are your hottest leads — they need a human response within 1–2 hours.

Realistic Performance Numbers

With three accounts at 20 connection requests/day each: 60 requests/day, 300/week. At a 30% acceptance rate: 90 new connections per week. At a 15% message reply rate (message 1 + message 2 combined): 13–14 replies per week. At 30% reply-to-meeting conversion: 4–5 meetings per week from LinkedIn alone.

These numbers are lower than cold email at similar volume — LinkedIn’s constraints are real. What makes LinkedIn worth it: the quality of the conversations is materially higher. A LinkedIn message reply from a VP of Sales who accepted your connection is much warmer than a cold email reply. Conversion rates from LinkedIn meeting to opportunity are typically 20–40% higher than from cold email meeting to opportunity, which changes the channel ROI calculation even at lower volume.

LinkedIn Restriction Risk: The Honest Assessment

LinkedIn actively detects automation and will restrict accounts that trigger their detection signals. HeyReach is built to minimize these signals, but the risk is not zero. What triggers restrictions:

  • Volume spikes: Jumping from 5 to 25 connection requests overnight. HeyReach’s warmup ramp exists to prevent this — follow it.
  • Low acceptance rates combined with high volume: Sending 25 requests/day with 5% acceptance looks like spam behavior. Target audiences that will accept at 25%+.
  • Unusual activity hours: HeyReach’s scheduling should be set to business hours in the account holder’s timezone. Automated activity at 2 AM is a red flag.
  • Account age: LinkedIn accounts less than 12 months old are 3–5x more likely to be restricted for automation than established accounts. Do not run HeyReach on new LinkedIn profiles.
  • IP address changes: Logging into a LinkedIn account from multiple IP addresses in the same day (laptop in the office, HeyReach’s proxy, home WiFi) triggers security flags. HeyReach uses dedicated proxies — make sure your team is not also logging into HeyReach-managed accounts from their personal browsers.

When an account gets restricted: LinkedIn will send an email to the account’s registered email address with instructions to verify the account. The typical restriction is temporary (24–72 hours) and resolved by completing LinkedIn’s identity verification flow. Do not attempt to automate around a restriction — it escalates to permanent suspension. Pause HeyReach for that account, complete the verification, and wait 7 days before resuming automation at reduced daily limits.

Build your multi-account strategy with restriction risk in mind: never rely on a single LinkedIn account for your entire outbound volume. With three accounts, losing one to a temporary restriction drops your capacity by 33%, not 100%. With five accounts, it drops by 20%.

Related reading: See the HeyReach vendor profile for a full breakdown of pricing, multi-account features, and a comparison against Dripify and LinkedIn’s own Sales Navigator messaging tools. For enriching your Sales Navigator audience before importing to HeyReach, see the Clay waterfall enrichment playbook. For routing LinkedIn replies alongside email replies into a unified outbound view, see the HeyReach vs. Expandi comparison.

Similar Posts

  • Routing Inbound Demo Requests with Default + Slack

    A step-by-step guide to building a responsive inbound routing system using Default’s form infrastructure, ICP scoring on firmographic and intent signals, Slack-based AE pod routing, and Linear for operational instrumentation. This playbook covers Default’s flow configuration, the scoring logic for ICP fit, the Slack channel naming convention that keeps routing noise manageable, and the round-robin fallback for unmatched leads. Includes an honest discussion of what happens to MQLs that convert but are not ICP-fit — the edge case most routing playbooks skip. Intended for RevOps engineers building or rebuilding inbound routing at Series A–C B2B SaaS companies.

  • Building a Forecast Confidence Layer on Top of HubSpot with Claude

    A practical guide to replacing gut-feel deal forecasting with an AI-powered confidence scoring layer built on Claude’s API and HubSpot’s engagement data. This playbook walks through the exact Claude prompt template, an n8n workflow that pulls deal and contact activity from HubSpot, scores each deal weekly, and writes scores back to a custom HubSpot property for dashboard visibility. Includes honest cost math: approximately $50 per month to score 1,000 deals weekly using Claude Haiku, and a discussion of what the model can and cannot infer from CRM engagement signals alone. For RevOps engineers and sales leaders who want forecasting that compounds with data rather than degrading to the loudest voice in the room.

  • Building a Waterfall Enrichment Workflow in Clay

    A step-by-step guide to chaining Apollo, ZoomInfo, People Data Labs, web search, and Claude inference in Clay to maximize contact enrichment coverage at minimum cost. This playbook covers the exact column setup, fallback trigger logic, per-row credit math, and the honest latency trade-offs at each provider layer. By the end, you will have a waterfall that fills email, mobile, job title, company headcount, and tech stack for 85-92% of a typical B2B contact list — without paying top-tier provider rates for every row. Intended for RevOps engineers and GTM operators who already have a Clay workspace and at least one enrichment provider connected.

  • Running a 30-Day Cold Outbound Campaign with Smartlead

    A day-by-day operational playbook for launching a cold outbound campaign with Smartlead — from domain warmup on day one through hitting full sending volume by day 21. Covers inbox provisioning, list build via Apollo and Clay, a four-email sequence designed over 14 days, deliverability monitoring with Glockapps, and reply handling that doesn’t let hot responses fall through cracks. Realistic numbers throughout: 50–150 emails per day per inbox, a 2–3% reply rate target, and the exact Smartlead settings that keep you out of spam folders. For GTM operators and RevOps engineers standing up a new outbound motion or rebuilding after a deliverability collapse.

  • Detecting Deanonymized Website Visitors with RB2B

    A step-by-step guide to installing RB2B’s deanonymization pixel, configuring Slack alerts for ICP-fit visitor identification, enriching identified visitors via Clay or Apollo, routing to your outbound team in HubSpot, and measuring the conversion rate from visitor identification to booked meeting. Includes publicly available conversion benchmarks (0.5–2.5% of identified visitors to meeting), an honest discussion of what RB2B can legally do in the EU vs. the US, and a frank verdict on whether RB2B is worth the $149/month for your specific use case. Links to the RB2B vendor profile and the RB2B vs. Warmly comparison for teams evaluating alternatives.

Leave a Reply

Your email address will not be published. Required fields are marked *