Features

Every surface a multi-account outreach team needs.

One operator console. Many sender inboxes. Eight product surfaces, no add-ons.

01 · Orchestration

Run every LinkedIn sender from one console.

Most outreach tools treat each LinkedIn account as a separate workspace. LinkedReach treats them as a pool. Push a sequence across all of them, balance load, and watch sender health from a single sender strip at the top of the dashboard.

  • Connect 1 to 500 LinkedIn accounts under one operator
  • Per-sender daily caps, warm-up state, and proxy health visible at a glance
  • Workspaces for client separation, with role-based permissions for your team
  • Auto-pause on warning signals — the affected account stops, the rest keep working
Sender pool · Northwave Agency
12 of 50 active
Sender 01 · alex.morrison
Day 47 · warmed · 18/25 today
Active
Sender 02 · sam.lin
Day 22 · warming · 11/15 today
Warming
Sender 03 · rita.chen
Day 6 · ramp 5→8 · 4/8 today
Ramp
Sender 04 · pat.gonzalez
Captcha detected · auto-paused
Paused
02 · Sequences

Branch on every reply state.

Build a sequence as a chain of steps — view profile, connect, message 1, wait 3 days, message 2, escalate to InMail. Branch on accepted, no-reply, or replied. Conditional waits respect your campaign's send window down to the timezone.

  • Connection requests, follow-up messages, and InMail in one flow
  • Time-based and behaviour-based branches
  • Per-campaign schedule windows (start hour, end hour, days, timezone)
  • Templates for common ICPs — or import your own playbook
Q2 RevOps Founders sequence
5 steps
01
View profile
Warm up the lead before the connection ping
Day 0
02
Connection request · AI opener
Generated against profile + recent posts
+1h
03
Message 1 (if accepted)
Soft-pitch the differentiator
+2 days
04
Message 2 (if no reply)
Different angle, shorter ask
+5 days
05
InMail escalation
Only fires if Sales Navigator is connected
+10 days
03 · AI personalisation

Openers that reference what the lead actually posted.

Personalisation isn't first-name token replacement. Each opener is generated against the lead's profile, recent posts, and your ICP brief — producing a sentence that reads like it took you ten minutes to write. Run a tone preview on every sequence before launch so nothing weird ships.

  • Per-lead personalisation grounded in profile data and the lead's recent activity
  • ICP brief stored at the campaign level — same model, your voice
  • Tone preview & safety filter before any message goes out
  • Fallback to your written template if personalisation can't beat a quality bar
Generated opener preview
Lead · Priya S.
CONTEXT
VP Demand Gen at Cinder. Posted last week about ABM tooling fatigue and "stitching together five different point solutions."
DRAFT MESSAGE
Hi Priya — saw your post on ABM stack stitching. We're building the orchestration layer specifically to kill that problem for outreach across multiple senders. Worth a 15-min look?
Reply rate
21%
Tone score
8.2
Length
42w
04 · Agent Mode

Replies and meeting bookings, autonomously.

Most tools stop at the opener. Agent Mode keeps going. When a lead replies, the agent reads the message, classifies intent, drafts a contextual response, and offers calendar slots when intent is positive. Run it in approve-each-reply mode for the first month, then graduate to fully autonomous.

  • Inbound reply classified into interested / not now / wrong person / negative
  • Drafted reply uses your tone, your ICP, and the conversation history
  • Calendar integration proposes real open slots and books on confirmation
  • Approve-each-reply mode for week one · full autonomy after you trust it
  • Every action logged with full audit trail
Agent Mode · Priya S.
Booked · 2m ago
INBOUND
Yeah, makes sense — happy to chat. Tuesday or Thursday work, mornings ideally.
Intent · Interested
Confidence 94% · warmth flag: hot
Auto-replied
AGENT REPLY (sent)
Tuesday morning works great. I have 9:30 or 10:30 ET open — either of those land for you?
Calendar hold · Tue 9:30 AM
Tentative until lead confirms
Booked
05 · Unified inbox

Every sender's replies in one feed.

Switching between fifty LinkedIn tabs is how operators burn out. The unified inbox surfaces every reply across every connected sender, attributed to the right account, sortable by intent, warmth, or campaign.

  • Reply-only view across the whole sender pool
  • Filter by sender, campaign, intent, or warmth flag
  • Quick-respond inline from any sender's identity
  • Conversation history threads automatically
  • Mark hot, snooze, archive, or hand off to a teammate
Unified inbox
38 unread
Priya S. · via sender 01
"Yes — happy to chat next Tuesday."
Hot
Marcus K. · via sender 04
"Send me a one-pager and I'll loop in finance."
Warm
Anna T. · via sender 02
"Not the right person — try Jordan in revops."
Referred
Jordan R. · via sender 03
"OOO until Monday."
OOO
06 · Lead qualification

ICP fit and warmth, scored on every reply.

Your closer doesn't want to read every "thanks but not now" reply. LinkedReach scores every replied lead on ICP fit, warmth, and intent — routes the qualified ones to the closer queue, archives the rest, and surfaces aggregate signal across the campaign.

  • 0–100 ICP fit score against your stored brief
  • Warmth flag (cold / warm / hot) based on reply tone and intent
  • Auto-routing to the right teammate's queue
  • Aggregate signal: which titles, industries, and company sizes convert
Qualification queue · this week
12 new hot
Replies
187
Qualified
42
Hot
12
Priya S. · ICP 92
VP Demand Gen · Cinder · 200–500 employees
Hot
Marcus K. · ICP 88
VP Sales · Mainline · 50–200
Warm
Sara D. · ICP 41
Account Exec · out of ICP · routed to archive
Filtered
07 · Safety

Built so you don't get banned.

Hard sending caps are not a feature you toggle — they're enforced at the worker level. Operators can't override them from the UI. Every action is randomised in timing, every account gets its own residential proxy, and any LinkedIn warning instantly pauses the affected account.

  • Hard cap of 25 connection requests & 100 messages per account, per day
  • Randomised 30–120 second gaps between actions
  • New accounts ramp from 5/day +3/week until fully warmed
  • Residential proxies bundled, sticky per sender
  • Warning or captcha → account auto-paused, operator notified
  • Per-campaign send-window enforcement (start hour, end hour, days, timezone)
Sender 01 · today
all green
Connection requests
18 of 25 daily cap · randomised gaps 47–112s
Within cap
Messages sent
62 of 100 daily cap
Within cap
Send window
Mon–Fri 09:00–17:00 ET · respected
Active
Proxy · residential US
Sticky session · 47 days clean
Healthy
08 · Integrations

Plug into the rest of your stack.

Native sync with the CRMs that matter. Webhook triggers for everything else. Zapier for the long tail. Lead activity, reply state, and meeting bookings flow into your pipeline without an admin running CSV exports every Friday.

  • Native HubSpot & Salesforce sync (bi-directional, contact + activity)
  • Webhooks for connection accepted, replied, qualified, meeting booked
  • Zapier and Make.com integrations for the long tail
  • REST API for everything in the UI
  • Calendar integrations: Google, Microsoft 365, Calendly
Connected integrations
4 active
HubSpot
Bi-directional · last sync 12s ago
Connected
Google Calendar
Agent Mode booking enabled
Connected
Webhooks · reply.qualified
POST to ops.cinder.io/leads
Active
Zapier
3 zaps running
Active

See it on your own senders.

14-day free trial. No credit card. Connect a LinkedIn account, build a sequence, send your first message in under ten minutes.

Start free trial View pricing